· None of the above quite fits
· None of these quite match
· Sonos Play Pause Issue with Roon
· WiFi and Wired. I use Switch between the Roon server and wifi. I use Wifi mesh from Asus. Recently changed the mesh from Synology. The issue was also present with Synology (prior to that TP link). Seems this is a persistent issue between Sonos and Roon.
Hey @Moh,
Thanks for writing in and for your report! We were able to review a fresh Roon Server diagnostic report and saw the following:
Roon isn’t the one pausing. Across the twelve days of logs, Roon sent exactly one pause command (Sept 7th at 14:50 local), and that one worked perfectly. Every other interruption came from the speaker’s side, the Sonos reported itself as paused or stopped while Roon still believed it was playing, and Roon did what it’s designed to do in that situation: assume you paused at the speaker and release the zone.
What that looks like in the Office (ERA 300): this is the one that actually kills playback:
The Living Room (Beam) shows a different, milder problem: four times on Sept 7th between 14:09 and 14:26, the Beam reported “stopped” at the very end of a track instead of rolling into the next one Roon had already queued up. Roon recovers by restarting the next track, so you’d hear a gap or a stutter rather than a full stop.
What we were able to rule out: the server itself was completely healthy at every one of these moments (no memory pressure, no stalls), your Sonos IP addresses were stable throughout September, and there isn’t a single failed command, timeout, or error against either speaker anywhere in twelve days of logs. Roon asked the speakers to play, they said yes, and then they told Roon they’d stopped.
Roon’s log records that the speaker reported a pause, not why, so we can’t close this from the logs alone, but there’s one strong clue. On Sept 16th at 19:22, Roon tried to renew its event subscriptions with the ERA 300 and all three came back rejected, meaning the speaker had already silently dropped Roon from its notification list. Speakers dropping subscriptions and delivering duplicate or out-of-order status events is a very typical signature of a network where some devices sit on a wired segment and others on wireless, which would explain why this has followed you across three different mesh vendors. It’s not really about the mesh brand.
A few things that would help:
One thing that would help us a lot: next time it happens, note the time. With that we can match it to the exact event in a fresh log set and see whether the speaker gave any reason.
Also, a quick question, is the Beam connected to a TV? A TV waking up or switching inputs can pull the Beam away from Roon, and that would explain the Living Room behavior separately from the Office.
Hi Benjamin,
Many thanks for detailed analysis.
To answer your question on Beam, yes it’s connected to TV. I play spotify from the spotify app and never have problem of play pause from any of my sonos devices.
My main concern is with Office (ERA300). It will help us to narrow down the problem and resolution.
None of my SONOS are connected with network cable, all are wify.
When I play song from Roon on Office. I see that behavior of skipping to next song without pausing.
At 10:23 CET I ran the test (3 times). However, this time, instead of skipping the song, it says ROON lost control of the audio device. Kindly check the log.
Hi @Moh,
Thank you! We were able to locate the incident in logs.
The office Sonos Zone prematurely ended a natural track mid-stream at that time. The fact that the Era300 alone manifests this behavior is significant, since that unit doesn’t rely on SonosNet like most Sonos Zones.
If any unit is wired, the rest of your fleet is running on that dedicated mesh while the Era 300 sits on your ordinary household Wi-Fi by itself. That difference alone would account for one zone dropping while the others stay put.
As a next test, can you please try hardwiring any other Sonos unit in this setup via ethernet? This will give us a useful data point and an immediate next step.
As a side note, the team has a significant volume of work proceeding behind the scenes to improve the Sonos/Roon compatibility and make the connection and device announcements more resilient.
Thanks for your patients.
Hi @Moh,
Circling back on this, have you had a chance to try hardwiring another Sonos unit over ethernet so we can compare it with the Era 300 on Wi-Fi? That extra data point should help us narrow down whether the zone drop is tied to the network layout we discussed. Please let us know what you see, and we can take it from there.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
Hello,
Thank you for your note. I just completed the test.
Test 1: Around 20:48 CET - Tested with wired Sonos (Play 1) in Living Room group. Most of the time it showed connection lost.
Test 2: Around 20:50 CET - Tested with Office Era 300 Wireless (no ethernet port). It showed connection lost error.
Please check the log and suggest me what I need to do with my network for Sonos to work properly with Roon.
Hi @Moh,
We looked over the diagnostics from your setup, and the repeated dropouts across multiple devices, including the Cast zones, point to a broader routing issue rather than a Sonos zone issure.
Could you let us know the exact model of your router and switch, how they are connected, and how Roon Server is connected? We also need to know whether your router is running the latest firmware and whether you are using a managed switch. If you try bypassing the switch and connect both Roon Server and the audio endpoint directly to the primary router, please let us know whether the issue still appears.
Thanks, and we’ll use that information to narrow this down.
Hello,
I am using
my router is configured to have it’s ownd DHCP network and I am using ISP router as internet connection (Double NAT - because of this my Roon ARC does not work. Anyway it’s another issue for another day).
Do you think I should change my router / switch?
Hello @Moh
Thank you for the router and switch details. We would not change either one right now. Nothing so far shows them failing, and a new one is not guaranteed to change this. Your test with the wired Play:1 also showed the same lost-connection error as the Era 300 on Wi-Fi, which suggests this is not only a Wi-Fi problem.
The double NAT affects Roon ARC, but it should not affect playback to your Sonos speakers, as long as the Roon Server, the Sonos speakers, and the device you control Roon from are all on your ASUS network. Please let us know if any of them are on the ISP router’s network instead.
Roon has a few known issues with how it hands off between tracks on Sonos speakers, and some fixes went out in recent weeks. We do not have a timeframe for the rest. To see where your setup stands, please do two things:
With that, we will pull fresh logs and look at that exact moment.
Hi,
I updated the server version.
At 1434 CET, I initiated the test.
First I did with a SONOS Roam. When I pressed pause button, it showed the same error of sonos losing control.
I then switched to the system called Office (Era300 + Sub Mini). And faced the same issue. You can check the timestamp at 1435.
Thank you for helping.
Is there something new here? I’m a very longstanding Sonos user and, for 2+ years, a Roon user. In my experience Sonos Streaming has always worked fine so long as transport control (play/pause/next/etc) is initiated from Roon, but has always screwed up when attempting transport control from the Sonos side (via speaker buttons, voice control or the Sonos app). The misbehaviour and messaging matches @Moh’s descriptions.
Volume can be adjusted from Roon and Sonos.
A potential workaround is to switch to AirPlay2 streaming to Sonos, which does apparently support bi-directional transport controls, but in my experience it’s not as reliable for playback as Sonos Streaming.
Hello @Moh,
Thank you for running the test and noting the times, that made it easy to find.
Here is what the logs show for your test on 11 October:
This is how Roon’s Sonos integration currently works: when playback is paused from the Sonos side, the speaker ends Roon’s stream, and Roon shows that it lost control of the zone. It can’t be resumed from the speaker or the Sonos app afterwards, only by pressing Play in Roon. As @Giles_W mentioned, controlling playback from Roon (the Roon)
Could you confirm that in this test you pressed pause on the speaker or in the Sonos app? If you pressed pause in the Roon app instead, please let us know, as that would be a different case.
Also, did you see any of the original issue (playback stopping or skipping on its own, without anyone pressing a button) since updating to the latest Roon version? If so, please note the time and the speaker again, and we’ll check it.
Hi,
Yes, I confirm that I pressed buttons on the device to pause. One good thing I noticed that the issue related skipping the track and playing the next one while pressing pause is gone. I will monitor for sometime and notify.
I understand that current design about the play pause from sonos. It will be extremely helpful to have that capability. Other apps like Spotify is able to do it, so I think it should’t be an issue for Roon and Sonos to collaborate and fix it (or rather release this enhancement).
Thank you for your support so far.
