Thanks for the quick response @daniel.winks! The latest version has fixed the leadership inconsistencies.
1 Like
I noticed some rather high CPU usage on my Hubitat and tracked it down to a "Zone Group Topology update storm" of sorts. Basically there's no need to subscribe to ZGT on every device, as it's "household"-wide on Sonos. This update should clear that up. I tested this for the last week on my end, it definitely cuts CPU usage a bit and I didn't notice any issues with group membership updates being processed by a single device maintaining the subscription rather than all of them.
I also didn't notice my SAC devices getting into a "ZGT storm" again, but then again, I've only seen that once (that I noticed). It was definitely noticeable when it happened, since there were a ton of re-subscribes on ZGT and 2 of the players were using about 100x normal amounts of CPU.
4 Likes
Found another issue this morning... somehow I got a string type passed in for 'clipDuration' when it expects an integer. This patch fixes that. No other changes.
5 Likes
Hi all, is there a dummy guide to this? I am stuck at even getting the favourites loaded. "Get Favorites" button does not seem to create any new items I can see.
Enable a "favorites child device" (and playlist, if you want that too) on one of your Sonos. There's an update that runs nightly to update the favorites, and "getFavorites" updates it immediately. The child device created should show all your Sonos favorites and provide the favorite number that's needed to start a favorite from a rule. It works across the whole "household", so you only need to enable this on a single speaker.
The commands don't have any way in Hubitat to be conditional. It's all or nothing for command and capabilities on a driver, so I can't do anything like "only show get favorite if there's a favorite child device created". So there's the same commands on all speakers, regardless of whether or not they have a child favorite created. Hubitat limitation.
Thank you. I managed to load favourites successfully from Sonos. LoadAppendandPlay does not seem to work even though I have the #number. I will fiddle with it some more.
First of all, MANY THANKS for putting in the time for this functionality!
I'm using 0.11.7 and trying to set the volume to 0 on all of my Sonos speakers as part of night time daily housekeeping.
While the "system" shows that a volume for a Sonos Advanced controlled speaker can be set to a range of: "0..100" (i.e., no volume), the 'system" only allows for it to be set to a minimum level of '1'.
I'm not sure if this is a bug in your app or the general Hubitat "system"....
Thanks!
Peter
Just to update, I did a complete uninstall and reinstall of the driver to get it working. Should have tried the usual "solution" earlier.
Just a thought, but why not just use mute?
I've been using Sonos Advanced Controller for a long time - love it. And I greatly appreciate all the work in constantly updating/improving.
I have a simple routine I've setup that plays a Sonos favorite on all my speakers (all rooms). Over the years, it has generally worked, but I would give it about an 80% reliability rating. Sometimes I have to run the routine multiple times for it to actually start playing the favorite. When it fails, typically just nothing happens. On occasion, it will start playing the favorite but only on a subset of rooms. I haven't been able to narrow down the issue(s). I've even tried inserting delays between commands thinking perhaps the Sonos API just couldn't keep up (not sure if that's even a valid theory). When I look at my Sonos Controller app after running the routine (and it fails) I sometimes see that the rooms have all been grouped and the proper favorite is selected, but it just didn't start playing. In other cases, I see either nothing selected (i.e. no favorite) or I see that the rooms haven't been grouped. The results seem to be random.
I was hoping to have someone take a quick look at my routine (below) and tell me if I'm doing anything wrong/superfluous to achieve the desired result. For context, I use a virtual dimmer and, through an Alexa voice command, I set that virtual dimmer to a value equal to the Sonos favorite number. Turning on that virtual dimmer is the trigger for this automation. I've checked many times, and that part of the routine always executes perfectly - the virtual dimmer is always set to the correct favorite number. It's the Sonos actions...grouping/select favorite/play...that seems to be the problem.
Thanks in advance for any advice/error corrections...here it is...
I created a Virtual switch(VS) for mine to run and what I found was the VS turns on to run the action, then stays on. So I set it up to automatically turn it off after turning it on.
Hi, All. I'm back to messing with this again, and while I can play an MP3, I can't play a track. My music system uses Spotify through Sonos. What is the particular syntax to use? It has to be something that simple.
Thank you.
Apologies if this question has been asked and answered, I searched but couldn’f find anything.
I was hoping this app would help me group Sonos Gen 1 (a Connect) and a Gen 2 (a Beam) devices, but if I select the Beam as a controller, no Gen 1 devices are then available to group. If I select a Gen 1 device, all the other Gen 1 devices are available, but not the Beam.
I am well aware of the incompatibility between the devices when it comes to the Sonos Apps, so I assume that incompatibility isn’t something this app solves?
Again, apologies if this is an old question.
Hi, I am running the latest version of SAC. The App could discover all of my Sonos speakers, however, I do not see any details such as album art, song titles, artist, etc. I see other folks could see all the details of the track or album art. What am I doing wrong here? Can someone give me guidance?
Thanks.
Here’s an example. This was before the author added support for grouped speaker control.
It’s done using a speaker custom command, like so:
