Grouped Sonos speakers stop playing after track change (ref#EHW6DW)

[Paul_Hodge]

What’s happening?

· Other – My issue isn’t listed above

Describe the issue

Grouped Sonos speakers stop playing after track change

If I group Sonos speakers together using Sonos (either the app or holding the play/pause button on a speaker to group it), then the grouped speaker (not the one Roon has a zone) will stop playing back after a track finishes or when skipping to another track.

This is the same issue as the following posts but there was no resolution in either of the posts. I’m using the Sonos Sync as I have a wide mix of different sonos devices (Play:1, Play:5, One, Roam and ERA100) and the native Roon group functionality is unreliable, but Sonos Group function works fine. I want to be able to skip tracks in Roon without the Sonos app ungrouping itself. I have largely copy and pasted the closed case from @seadowg as it was unresolved.

Roon ungrouping Sonos speakers

Roon Core Machine NUC 10 i5 using ROC Networking Gear & Setup Details XFinity WiFi Connected Audio Devices Sonos Bridge and 8 differing Sonos speakers of various generations, use the Sonos S1 app accordingly Number of Tracks in Library 39,386 tracks Description of Issue I have two rooms grouped together regularly under Sonos. When playing Roon through the bedroom+bathroom speakers of Sonos, it will ungroup the bathroom speakers at the beginning of each new track. How to stop thi…

Grouped Sonos speakers stop playing after track change (ref#UO6CK1)

What’s happening? · Other How can we help? · None of the above Other options · Other Describe the issue If I group Sonos speakers together using Sonos (either the app or holding the play/pause button on a speaker to group it), then the grouped speaker (not the one Roon has a zone) will stop playing back after a track finishes or when skipping to another track. Usually this works fine, but once it gets in this state I can't work out how to fix it. The last time, grouping and ungrouping the sp…

Describe your network setup

Unifi wireless network

[vadim]

Hello @Paul_Hodge,

Thank you for taking the time to describe the issue in detail.

Regarding the two threads you linked — those cases remained unresolved simply because the original posters never followed up with the information we requested. Since no diagnostics or timestamps were provided, we weren’t able to investigate further, which is why no resolution was posted.

To move forward with your case, could you please:

Reproduce the issue once more

Group your Sonos speakers using the Sonos app (not Roon), start playback from Roon, and let the grouped speaker drop out after a track change.

Please note the exact local time when the grouped speaker stops playing.

Once you share that timestamp, we’ll pull diagnostics from your Core, review what the RAAT and Sonos integrations are doing at that moment, and discuss the findings with our Product team to determine whether this behavior is:

• a bug we need to address, or
• a feature request / limitation of how Sonos grouping interacts with Roon.

We appreciate your help — with the timestamp, we can finally investigate this properly.

[Paul_Hodge]

Hi there Vadim,

Have reproduced the issue. Here are the details…

• 9:05:45 local time sydney (started playing on office speaker in roon after having grouped office and bathroom in sonos)
• When Roon started playing, the group in Sonos was broken straight away
• Recreated the group in Sonus while the song was playing. Group was maintained during the song
• Skipped the track at 9:09:00 am Sydney and it has broken the Sonos group

[vadim]

Hello @Paul_Hodge,

We took another close look at the diagnostic data from your account, specifically around the time you mentioned — 12/10 at 09:09:00.

Here’s what we can confirm from the logs:

1. The track was still playing normally at 09:08:56

12/10 09:08:56 [PLAYING @ 3:08/3:28] Silent Night...

No buffering issues, no stream starvation, no transport-layer errors on the Roon side.

2. At 09:09:00, Roon receives a “Next” command

12/10 09:09:00 Trace: [zone Office] Next

This command did not come from Roon.
It was triggered by the Sonos device or the Sonos group itself. Roon simply responded to the request it received.

3. Immediately afterward, the Sonos group restructures itself

Multiple zone update and unlink check events follow, showing that Sonos changed group membership on its own. Roon is only reporting the updates it receives from the Sonos API.

Summary

There are no playback errors, no network issues, and no streaming failures on the Roon side at the moment of the interruption.
The behavior you observed — track skipping + group breaking — is being initiated on the Sonos side, not by Roon.

We would recommend contacting Sonos support with these timestamps, as their device is instructing Roon to skip tracks and is reconfiguring the group unexpectedly.

If anything changes or you have additional details, feel free to update us — we’re here to help.

[Paul_Hodge]

Vadim,

The only think that I did on the Sonos side was
a) Establish the group initially at the 9:05 marker
b) Recreate the group after it was initially broken after the track started playing

Starting the track and skipping the track was all invoked from Roon. This seems to be different to what your logs are reporting.

Multiple people are having this issue, so it’s not just isolated to my system or environment.

[Paul_Hodge]

So for those that have had this problem, here’s what it was for me (could be other variances). I had my Sonos system set to “update automatically”, however when Sonos looked at the logs, there were some nodes with pending updates. According to Sonos, having nodes with inconsistent update levels can cause this issue. Forced an update to get all of my nodes up to the same level and the issue went away.

[benjamin]

Hey @Paul_Hodge,

Thanks for following up and confirming that updating your sonos devices solved your issue - happy listening!