· The Nucleus boots up and I can connect to it in the Roon app without issue, but I have a question about configuration/storage/attached devices
Describe the issue
Hello, For some time now when I switch from my Lumin T2 to reading and I want to read a song from my nucleus roon, this one is impossible I stay on the T2. If I reboot the Nucleus, playback is possible. If I switch to T2 it works, if I go back to Nucleus it doesn't work anymore. I must reboot Nucleus. This manipulation was never a problem before... My hardware configuration has not changed. Could you please help me. Thank you in advance Philippe
Please power cycle your whole network of devices starting from the router, WiFi mesh, access points, network switches, Lumin, Nucleus, tablets and phones.
1. The internal drive has damaged areas. Four files cannot be read at all: two from Jamiroquai’s A Funk Odyssey, one from Susheela Raman’s Salt Rain, one from Autour de Minuit. The operating system reports it as an uncorrectable read error on the drive.
This is not what you wrote to us about. Roon just skips those tracks and everything else on the drive plays normally. But the damage will spread.
2. Roon keeps losing its connection to the Lumin T2. When Roon starts playing to it, it first asks the Lumin to switch its input. That request failed twenty times with an internal error, because at that moment there was no working connection to the device. Eleven more times Roon asked the Lumin to prepare for playback and gave up after fifteen seconds with no answer.
The timing matches your report. On 28 August the error appeared at 10:21, you restarted the Nucleus at 10:25, and playback worked from 10:30. The same pattern appears on 18 July.
What to do:
Copy your music off the internal drive now, while it can still be read. Note any files that refuse to copy.
Once copied, have the drive replaced. It is a standard 2.5 inch drive, and your library and playlists are stored elsewhere so nothing is lost.
Next time playback stops, note the exact time and do not restart the Nucleus straight away. Leave it for a few minutes, then tell us the time. Restarting erases the record we need.
Please tell us whether the Lumin T2 is connected by Ethernet or wirelessly, and whether it has a fixed address on your network.
Hello,
Nucleus reboot time: 9:40 AM (Paris) on September 3, 2026.
Web radio playback on the T2, switch to Roon, web radio playback, switch to T2 web radio playback, switch to Nucleus, web radio playback.
I have the same problem regardless of the source: web radio, Qobuz, or CD file.
Thanks for the precise timestamps, that made this easy to pin down. We went through the logs around your 9:40 AM reboot and the failure is clearly visible. All times below are Paris local.
What the logs show
09:41 — Nucleus reboots, Roon Server starts. The T2 is discovered at 09:41:37 on 192.168.0.33.
09:47 — you start web radio on the “Nucleus + Lumin” zone. One second into the stream the T2 drops its RAAT control connection, and Roon’s five reconnection attempts are all refused. At 09:47:46 the T2 reappears — on a different RAAT port, which means the Roon Ready service on the T2 restarted itself.
09:47 – 09:48:17 — playback runs normally.
09:48 — the T2 reports back to Roon: Lost — reason: source_deselected. This is the moment the T2 was handed over to its own source.
09:48 — coming back to Roon, Roon asks the T2 to set up the stream and the T2 never answers. Roon waits 15 seconds and gives up at 09:48:33.
09:48:38 onward — every further play attempt on that zone hits an internal error in Roon Server, and the T2 does not appear in the log again for the remaining nine hours.
Two problems, compounding
On the T2 side: its Roon Ready service restarts, and after it deselects Roon as its source it stops responding to Roon’s setup requests entirely. The changing RAAT port is the giveaway. We see the identical pattern in your logs from 27 and 29 August, so this is not a one-off.
On our side: once that happens, Roon Server is left holding a dead connection to the T2 and the zone can never be re-selected — which is exactly why a reboot is the only thing that brings it back. We’re writing that up for the team, since I believe Roon should recover on its own here.
Best next steps
Check the T2’s firmware. The logs report firmware 23.1a with RAAT 1.1.47, which is a few generations behind. Please confirm the version shown in the Lumin app and install any update offered.
Try a lighter recovery next time it happens, before rebooting: go to Settings → Audio and disable, then re-enable the T2. If that alone restores playback, that tells us a lot about where the state is stuck. If it doesn’t, try restarting just Roon Server from the Nucleus web interface (http://<nucleus-ip>) rather than a full reboot.
Change the order of operations as a test. Press stop in Roon first, wait a few seconds, then switch the T2 to its own source, and reverse that when coming back. Does the problem still occur?
How are you switching the T2’s source, the Lumin app, the front panel, the remote, or does it switch automatically when another app starts streaming to it? That detail matters for reproducing this.
Please also open a ticket with Lumin support and give them 09:47–09:49 on 3 September, Paris time. Ask them for the device-side log for that window, their log will show why the Roon Ready service restarted and why it stopped answering afterward.
Send fresh timestamps after the next occurrence and tell us the time it failed, so we can confirm whether the firmware update changed the behaviour.