· Hi, I am using Roon Nucleus to control Sonos endpoints, mostly streaming music from Qobuz. Everything was running smoothly since November, but in the past three week I have had lots of issues. The music stops playing, speakers drop or will not play, "Roon loses control", etc. I have restarted my router (1gb fiber service), tried resetting the app and Nucleus, powering on and off speakers, but can't get to a stable place. Can you run diagnostics so I can figure out my issues? Thanks, Mark
Could you please reproduce the issue one more time and note the exact time it occurs?
After that, please collect the logs following these instructions. Note that we need the “Logs” folder located inside the “RoonServer” folder, not the one in the “Roon” folder.
Once you have them, please upload the files to our Logs uploader so we can investigate further.
Hi, I uploaded the requested files, 19 of 20 uploaded fine. One is failing after multiple attempts. The one that will not upload is probably the one you need, but please let me know if you have what you need. The issue occurred at 8:15am and 8:24am. Mark
Thanks for the update and timestamp! You are correct in that we’d need the latest ‘RoonServer log’ in order to see the time you provided.
That said, we saw a handful of unnatural stoppages from the other logs you’ve sent over that helped paint a pretty clear picture around the issue.
We’re seeing this error that fires almost immediately after playback starts:
CorruptMediaException: Got CorruptFile while creating decoder (2)
Roon fetches the Qobuz stream successfully, starts sending audio to your Sonos group (Move 2 + Garage + Kitchen), but then the audio decoder fails almost instantly and kills the stream. It then auto-advances to the next track and that one plays fine, which is an important clue.
It also looks like your Master Bath Sonos speaker is causing a large amount of “Connection refused” errors in multile logs, firing several times per second, all day long. This is hammering the Roon Server process, consuming memory, and likely causing cascading failures across all your zones.
As a first step in troubleshooting, Power cycle the Master Bath speaker completely, unplug it from the wall for 30 seconds, not just a soft restart.
Afterwards, assign static DHCP reservations for every Sonos device in your router’s admin panel. Log into your router, find each Sonos device by MAC address, and pin its IP permanently. This alone will solve a large portion of your instability.
See if the above helps, I’ll be curious to see if you run into any continued Qobuz-specific issues.
Hi Benjamin, thanks for the detailed and helpful reply! I did reset the one problematic speaker and that brought stability back to my listening world! I have set the IP addresses for my 10 Sonos devices as recommended and will see if that provides a long-term solution. Thanks again! Mark
Since a few days have passed, I wanted to check in and see how things have been performing for you so far. We’re here to help in case you’re still running into playback issues.
Hi, thought I had replied to this, but don’t see my message. The issue started again. I sent log files immediately after the episode. I disconnected the speaker that was previously causing an issue (Sonos MB) and that helped. Do I have a bad speaker or bad location, or does it seem to be something else? Mark
What is strange is that we are not seeing any sign of the Nucleus on our end in the diagnostics. I wonder if there is something going wrong at a network or OS level.
We have seen users have a better experience in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS.
I would also suggest performing a Backup of your current database (just as an extra precaution) and then try to perform an Operating System reinstall from the Nucleus Web UI.
The above may or may not help with the stoppages, but it should allow us to better inspect the error logging for clues.
The last response is confusing to me and feels like we are changing topics. Initially, we identified a problem with one speaker, the Sonos in the Master Bath. Based on the most recently sent logs, is that speaker still causing problems or not? I did assign static DHCP for every Sonos speaker, as suggested. Did that make a difference is the results you see in the logs? Let’s resolve this issue before we go down other paths. By the way, I did reinstall the Nucleus OS and everything seems to running clean for now.
The last log set we can see from a manual upload is from April 14, and we are not able to locate any others from you. The Nucleus also appears to be blocked from diagnostics for some reason, if you can please try the OS reinstall when you have a moment.
Hopefully, that will help and allow us to check the system-level logs for clues. I suspect that there may be several issues at play, as I also saw the Sonos buffers stuck, and several connection refused errors in the April 14th log set you sent.
Just checking in on this. Were you able to try the OS reinstall on the Nucleus so we can get access to the system-level diagnostics, and have you had a chance to send any newer logs since the April 14 upload? Thanks, and let us know what you’re seeing.
Hi, I did the Nucleus OS reinstall, and made one other network change–added ethernet backhaul on a node in my mesh system. So far, running clean. Will run logs and submit when I have another issue. Mark
Hi, the music was cutting out this afternoon. I just uploaded log files ([redacted] RoonServer_log.01.txt.zip). Please let me know what you can see in the files. Thanks, Mark
Thanks for the update, sorry to hear you’re still having issues!
We were able to review the log you’ve sent over, and see a very consistent pattern throughout the entire day — roughly every 5–15 minutes the zone transitions:
Playing → Disconnected → WaitForStatus → Playing
What’s causing it? A few clues in the logs:
"Stale AV status event ignored" warnings appear right around the disconnections. This is a Sonos-specific symptom where the Sonos speaker's AVTransport status event arrives out of order or is delayed, causing Roon to lose sync with the player's state.
The Kitchen speakers are on Wi-Fi (WirelessMode=1, ConnectionType=5 = SonosNet/wireless), while Pool and Garage appear to be on wired connections (ConnectionType=2). The Kitchen unit is the group coordinator, meaning if Kitchen has any wireless instability, the whole group drops.
No Qobuz streaming errors: the Qobuz API calls all returned HTTP 200, and file downloads completed cleanly. The problem is entirely on the Roon→Sonos delivery side, not the streaming source.
What to try next:
Check the Kitchen speaker's Wi-Fi connection: it's the group coordinator and is wireless. Even brief Wi-Fi hiccups will drop the whole group. Try moving it closer to an access point, or switching it to a wired connection if possible.
In Roon Settings → Audio, check if there's a "Resync Delay" option for the Sonos zone and bump it up slightly.
In the Sonos app, check if the Kitchen unit's firmware is current
Note that the Study speaker shows an older firmware version (86.7-77050) worth updating that too, though it wasn't in the playing group.
We’ll be on standby for your reply, thank you @mn.marke!
Thanks for uploading the logs. Here’s what we found:
The afternoon cutout is not in this file. The log you uploaded (RoonServer_log.01.txt) covers May 30 from 7:55 AM to 3:18 PM local time — the incident you described happened after that. Could you also upload RoonServer_log.txt? That file should contain the afternoon events we actually need to investigate.
What we did find in the uploaded log:
Qobuz CDN bandwidth drops. Three times during the morning session, the download speed from Qobuz's streaming servers fell below the minimum required for your stream quality:
8:11 AM: 656 kbps actual vs. 964 kbps needed
8:39 AM: 1,117 kbps actual vs. 1,151 kbps needed
9:01 AM: 640 kbps actual vs. 1,017 kbps needed
These would cause brief audio cutouts. This is on Qobuz's delivery side (Akamai CDN), not your local network. There's not much you can do to prevent them other than switching the DNS settings, which can help absorb short dips.
Sonos Move 2 (IP 192.168.68.66) generating instability. This speaker joined the network at 7:56 AM and triggered a zone rebuild that interrupted playback at 7:58 AM. After that it continued generating "unlink" warnings every ~5 minutes for the rest of the log — a sign it's periodically dropping out of its Sonos group. Since it's a portable/battery speaker, this could be due to marginal Wi-Fi placement or the speaker power-cycling. Please double-check that its static DHCP reservation is still correctly assigned to this device's MAC address in your router.
Please upload RoonServer_log.txt and we can look at what specifically happened that afternoon.
