Skip to content
Discussion options

You must be logged in to vote

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_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.
Then I tried resetting/removing…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by OzGav
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants