I tried searching on this topic and didn't come up with any recent postings. If I missed one, please point me to it...
I have a simple automation that plays a Sonos favorite in all rooms of my home, initiated via voice through Alexa. The automation clears out any groupings, selects the favorite, groups all the speakers together (using a speaker grouping I setup in the integration), sets the volume, transition fade, etc. and plays. Up until a Sonos system update I installed two days ago, this worked pretty much flawlessly. However, since that Sonos update, the speakers are not grouping. The favorite will start playing on the originating speaker/room, but none of the other speakers are getting grouped. It doesn't seem like a coincidence that the recent Sonos system update introduced the new "preset" feature which pretty much does the same thing...select a Sonos favorite, select rooms, select volume and save as a preset. Did Sonos change anything about how speakers are grouped, which the Sonos Advanced Controller hasn't caught up to yet?
I installed the latest HPM Sonos Advanced Controller update hoping that may address the issue, but testing so far yields the same result - speakers still aren't grouping. Also, thinking perhaps my pre-established speaker grouping ("Whole house") may be the issue, I attempted to go into Sonos Advanced Controller to establish a new speaker grouping to use instead, and I'm getting an error every time I attempt to create a new group..."Select a coordinator before saving the group." I've obviously done that so, something is off with that function.
Curious if anyone else is experiencing this, if this is a known issue and/or if there's a work-around.
UPDATE: I was having no success in creating a new speaker group in the Sonos Advanced Controller interface. However, on a whim, I toggled the switch at the bottom of the screen to "Use old UI" and tried again. While I received the same error ("Select a coordinator before saving the group"), the save actually did create the new speaker group. I then modified my automation to use that pre-defined speaker group and it's working again. So, either my old speaker group somehow got corrupted or otherwise invalidated, or the back-end workings of defining a speaker group have changed. In any event, this seems to have resolved the issue. That doesn't account for the error when attempting to save a speaker group, and the fact that it sort of works when you use the old UI. It seems this should be looked at.