Thank you @c_h_1, there was still some apparently connectivity related issues that was blocking the request for a diagnositc report. Those have since been cleared.
That said, There’s a real, ongoing network-stability problem independent of the Sonos issue.
Across the week we found repeated “incomplete receive” broker connection failures, spread fairly evenly across almost every day, not just clustered around reported skip times. Two control points are responsible for essentially all of them:
192.168.68.105 the iPhone
192.168.68.115 a second control point identified as LMAC-7FYVQ5N-AP, which separately shows its own repeated [raatserver] lost client connection. Retrying(0) → 5-attempt-then-give-up cycles
Both are consistent with WiFi/mesh roaming instability (dropped associations, band-steering, AP handoff) rather than anything Roon Server is doing wrong.
Are you running Tailscale on the ROCK and iOS remote? If so, try disabling it on both for a test period.
Also, If possible, get the Sonos stereo pair onto Ethernet (the zone group state confirms it’s currently WiFi-only, EthLink=“0”).
The issue still occurs - UTC times - 00:12:40 - 7th Tuesday July 2026.
I’ll try ethernet when I get a chance.
Also out of interest, you mention the controllers. However I thought the music comes from the Server, so if I switch my controller off, music still plays. In which case how does the controller effect things?
Finally to add, you mention wifi/mesh issues. It works perfectly on my WiiM Pro Plus. And also if playback on my laptop, or my phone.
First off,I hear you, and the frustration is fair. A ticket open since April with the music still cutting out isn’t the experience we want you to have. So let me give you something concrete.
Going through this week’s logs, we’ve isolated what looks to be the actual cause of the early cutoffs, and it’s more specific than our earlier thinking:
The stops are happening on the Living Room (Sonos pair) zone during the handoff to the next track. Near the end of a track, Roon and the Sonos exchange the “next track” info for a gapless transition, and on this zone, that handoff is closing the current stream a few seconds early. The Sonos then reports the track as finished, so Roon advances, which is the cutoff and short gap you’re hearing.
Two things worth being clear about, because they revise what we’d said earlier:
It's not driven by your network. We can see it firing during completely normal, uninterrupted playback. There is some connection noise in the logs, but it's coming from other endpoints and isn't what's causing the cutoffs. I don't want you chasing WiFi fixes that won't move the needle.
One optional thing: because the Sonos pair is currently on WiFi, moving it to Ethernet can reduce how often this triggers while the dev fix is in progress. To be clear, it's not a fix and it won't be on you to solve, but if it's easy to try, it may make things more bearable in the meantime.
It's not tied to clearing the queue, and it's not your source (local, Tidal, and Qobuz all hit it). It's specific to the Sonos handoff path, which is why your WiiM zone is unaffected.
I've put these findings and reproduction details on the dev ticket so it's pointed at a clearer cause now.
On the app crashes you mentioned, that’s a separate issue and I don’t want it lost in this thread. It would be good to review a set of manual iOS Roon remote logs, please use the directions found here and send over a set of iOS logs to our File Uploader.
I know that’s a lot of patience to ask for, and I appreciate you sticking with it and doing the legwork on timestamps; it’s genuinely what let us get to the bottom of this. I’ll keep you posted here as the fix progresses.
