Mixed sync group: Sonos volume control not working or extremely delayed, while playback sync still works #5406
-
|
Hi all, I’m looking for help debugging a Music Assistant issue that started after a Music Assistant update. Setup:
What still works:
Problem:
Things I already tried:
None of this fixed the issue. Why I’m confused: Has anyone seen this with mixed Music Assistant sync groups involving Sonos + AirPlay/pCP players? Is there a known regression, setting, or workaround for Sonos volume/button handling in Music Assistant groups? Any suggestions for logs to check, settings to compare, or tests to isolate whether this is the Sonos provider, AirPlay bridge, or group handling would be appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
I have a pair of Sonos Era 100 and they work fine, grouping, ungrouping, volume controls, pause and resume are all super snappy. You seem to have tried everything I can think of. No one is reporting this but maybe some firmware update has created a problem. You can enable debug logging on SETTINGS >> SYSTEM>> PLAYERS and make the volume changes while looking at the log and see if you can see anything there, errors or obvious lagging? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for that nudge: We are getting closer. There is a significant amount of lag between the cmd_volume_set and the player reporting its updated volume level.
And to be honest, I think that was not the command it reacted to, but to one about 1 minute before that. I'm surprised that I didn't try this already, but the problem still occured when I only used a single Sonos Speaker.
That solved it. I don't know which one of these Plugins did the trick Anyways, in case anybody comes across this problem, I hope this helps. @OzGav thanks for this amazing piece of software and your input. |
Beta Was this translation helpful? Give feedback.
Thank you for that nudge: We are getting closer. There is a significant amount of lag between the cmd_volume_set and the player reporting its updated volume level.
2026-04-28 22:13:11.923 DEBUG (MainThread) [music_assistant.players] Handling command cmd_volume_set for player Sonos Move (by user sebastian) 2026-04-28 22:13:20.517 VERBOSE (MainThread) [music_assistant.players] Player state updated for Sonos Move: changed fields: volume_levelAnd to be honest, I think that was not the command it reacted to, but to one about 1 minute before that.
I'm surprised that I didn't try this already, but the problem still occured when I only used a single Sonos Speaker.
Then I tried resetting/removing…