I have recently been experiencing issues getting Roon to connect (or stay connected) to our Lumin P1 culminating today in a consistent message that " audio device refuses to switch input to Roon".
Lumin P1: hardware version 23.2 of 7 October 26. App version 12.5.3 also of 7 Oct 26
Roon Server: version 2.73 (build 1700) production, running on a Apple MacBook Air M5 OS 27.0.1
iOS version of Roon Controller: version 2.73 (build 1696) production (on iPad and iPhone, both running version 27.0.1)
OS version of Roon controller: version 2.73 (build 1700) production running on Mac mini M6 OS 27.0.1
Win 10 version of controller: version 2.73 (build 1700) production (64 bit)
Lumin P1 has mal-operated to point where its on remote controller will not get unit to respond, thus forcing a power off/on action. Lumin operates normally when running independently of Roon (using Lumin P1 remote controller and associated iOS controller on iPad and iPhone).
While I suspect the recent Lumin update is the culprit, we have all been experiencing connectivity issues recently with installation of iOS/OS 27!
FWIW: I experienced the same problem and Roon message in my setup (Lumin U1 Mini) twice in the last week since the last update. Never happened the years before. A restart of the Lumin solves the isse.
Thanks for your feedback - like you I have not had any issues with Roon Ready on the Lumin previously. Please note that since performance issues appeared I have turned power off/on to get Lumin to accept Roon connection, but even this failed in the end. I note Roon have released a new update this morning [version 2.74 (build 1712 production)] so this may resolve the issue faced.
Following installation of version 2.74 (build 1712 production) on Roon Server (MacBook Air M5), we are back to standard performance on Lumin with complete absence of issue - great!
I also noticed that dynamic range indication for current streaming track now exists (as already existed for own library tracks).
For the records: Today in the morning the Lumin suddenly disapeared in Roon in the middle of playing a track via Roon. The U1 Mini was then also not found in the Lumin app anymore. I needed to power down/on again to have the Lumin come back to the network.
@wklie Any idea what could cause this? Do I need to check the network cables or could a software issue cause this behaviour?
Just when I’ve prepared a new firmware for you to try, I’m glad Roon Server 2.74 update fixed this for you.
Please power cycle the whole network infrastructure starting from the router, WiFi mesh, access points, network switches, Roon Server, Lumin, NAS, phone tablets. On Roon Server OS, please disable firewall.
If this problem shows up again, please try a different network cable from Lumin to a different network switch.
Well following Lumin doing a controller application update (so Lumin P1 running version 23.2 of 7 October 2026, and Lumin controller on iPhone and iPad NOW running 12.5.4 of 20 October 26) I get the following:
If you operate the volume controller on either the iPad or iPhone quickly (say move the slider from 25 to 0 and back or used the +/- radio buttons rapidly, and then after a few seconds repeat the actions the Lumin completely locks up and will not respond from the Roon Controller, Lumin remote controller etc.; and the Roon Controller starts searching for the next track and after several iterations messages that there have been too many failures!
The only ‘temporary fix’ I have found is to turn the Lumin off at the wall, wait say 5-10 seconds and turn it back on. If then attempt to get the Lumin remote or app controller to select a track to play it take a few attempts before it works and from thereafter it is fine. Then firing up Roon on the iPad and selecting a track to play on the Lumin all works fine again … until you are too active on the volume control (slider or radio buttons) and then the above failure process occurs - yes failure mechanism is repeatable. (friends came around for a listen and I had to use the temporary fix method 6 to 8 times)!!.
It appears the ‘Roon Ready’ interface is overloading the Lumin buffer in some way and causing it to go gaga.
I note that all other devices are working normally with Roon and that around Sunday in NZ (so 25 or 26 Oct 26) the Roon controller software for iPad/iPhone updated to version 2.74 (build 1712 production) being the same as the Roon Server is using.
Issue occurs specifically when using iPhone/iPad Roon Controller. I have noticed that Roon updates are available to apply to non-mobile devices (in my case: Win 10 PC, OS MacBook Air, Mac Mini) generally well before same version is available on iPhone/iPad for Roon Controller app.
Some issues have occurred previously when iPhone/iPad Roon version is older than the Roon Server version as viewed on said iPhone/iPad form within the Roon Controller app.
I do not try and control the Lumin via its mobile app or physical remote when using Roon with the Lumin (which I try to be always, but not so much lately!).
Also I did note that controlling Roon from the same device as Roon Server (MacBook Air M5) appears rock solid … could it be that on said device both Roon Server and Controller are on the same version?
I see and have installed both OS 27.2 and Roon Version 2.74 (build 1716 production) on all non iPhone/iPad devices (these are on OS 27.2 and Roon Version 2.74 (build 1712 production).
Just add to above comments, today I rang Roon Controller on MacBook Air and moved the volume bar slowly to zero (from setting of 30 out of 100) and on moving back to increase the volume, the same fault occurred causing lost of control, no sound and Roon searching the next tracks iteratively till I switched power to Lumin off at the wall.
Turned power to Lumin on again and waited for it to initialize, enabled normal control of same track listing to Lumin.
This issue is occurring solely when interacting with the Lumin P1.
I note Lumin have released an update to their remote (now version 12.5.5 of 28 October 2026). With this version Roon Remote fails immediately (as described above) when attempting to control volume setting on Lumin from Roon Device Setup > Volume Control = Device volume. The only fix is to (as previously) disconnect from power supply, wait and reconnect. I appear not to be able to access release notes from Lumin on what changed in version 12.5.5.
I have now moved to Roon Device Setup > Volume Control = Fixed volume for the Lumin and this works fine (Roon doing stream upscaling and Lumin volume control management). In fact it may actually sound better, but with Roon volume control of Lumin now completely broken no A/B testing is currently possible.
As this new configuration allows the Leedh volume control to work as Lumin designed it, I suspect Lumin tweaks have caused Roon Ready connection relating to volume control to become unstable. Hopefully there is an answer and speedy remedy - that would be appreciated!
… further update, Lumin just released remote version 12.5.6 of 30 October 26, worked for about a minute on iPhone 12 Pro Max then failed as per above. Back to Roon Device Setup > Volume Control = Volume setting!
I think I might just have to stay this way until someone advises it is worth another attempt.