Just FYI, during beta (and even fairly recently) there was an issue with the Sonos speakers occasionally failing to respond to any commands from the API (rules, routines, or even the CLI) despite those commands appearing in the CLI logs. When that happened, the speakers would also stop reporting events (track changes, group changes, album art, etc.)
There is a particular engineer, a Sonos user, who I know experienced this himself. (He is still responsible for the majority of fixes/revisions to the current driver.) I thought he had largely resolved the issue with some of the more recent commits, but this morning it happened to me again. In this case, a “refresh” command brought everything back online, with a flurry of past events suddenly reporting. Now, whether this is the same as what the others experiencing, of course I can’t say, but it does sound like it might be related.
My system stopped reporting events again approximately one hour ago according to my tracking. “Refresh” didn’t accomplish anything this time. As you can see the command was received, but no data was reported back.
DEBUG entries are relatively new, suggesting someone is actively looking at this.
Refresh Log
2023-07-13T20:43:01.581303666+00:00 TRACE Sonos Received event with handler capability
2023-07-13T20:43:01.606633328+00:00 INFO Sonos <Device: 72415b90-9153-4350-b4ad-281a51ac4813 (Sonos Office)> received command: {"capability":"refresh","component":"main","args":{},"positional_args":{},"command":"refresh"}
2023-07-13T20:43:01.609774465+00:00 TRACE Sonos Found CapabilityCommandDispatcher handler in Sonos
2023-07-13T20:43:01.613067443+00:00 TRACE Sonos Refreshing Sonos Office
2023-07-13T20:43:01.615882826+00:00 INFO Sonos [DEBUG->INFO] Sonos Office all connections running? table: 0x1eb0a38
2023-07-13T20:43:01.617848551+00:00 INFO Sonos [DEBUG->INFO] Refresh subscriptions on Sonos Office
2023-07-13T20:43:01.630807277+00:00 DEBUG Sonos Sonos Office device thread event handled
Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
I’ve had the issue with the connection to Sonos being lost a couple of days after migration.
ST no longer controls the Sonos so a click in the app just has a spinning animation for a few seconds, the status of the Sonos in the app doesn’t update although it shows as online, but the Sonos app still has full control.
I resolved - for now - by an unplug of the ST hub.
I can understand a meandering discussion being detached from the Update on Groovy Platform Migrations thread but this new thread is somewhat buried for something that hadn’t been fixed at release - I rely on ST control of Sonos so it’s very annoying after years of being trouble free.
I have also had Sonos devices simply becoming unresponsive, usually after actioning a ‘thing’ - say play favourite - and then no status reported back with device becoming unresponsive. Fix is to reboot ST (v2) hub and/or my Sonos gateway device (a boost).
However this behaviour predates the recent updates to hub and driver but does continue to manifest.
Possibly of interest, it is always stereo pairs that demonstrate this issue
My Sonos integration is fully broken at the moment. Nothing works.
An added bonus, in the early hours of the morning SmartThings Sonos devices suddenly started playing (not the actual Sonos devices) so it was like a massive delay/lag from real activity Friday night. And, while those ST devices are now showing ‘stopped/paused’ the API is apparently reporting them as still playing. So, for example, SharpTools thinks they’re playing.
I know I shouldn’t be surprised but really, how did this make it to production?
Yes, this behavior is similar to what I described in the post above (quoted here)
It’s like everything gets backed up in the system, then a door opens, and that all comes rushing out at once.
For what it’s worth, I’ve had automations tracking what SmartThings reports from this driver vs. what Sonos’s UPnP interface reports, and in recent weeks I genuinely believed this issue had largely if not completely been resolved. I also have my suspicions about whether this is actually a driver issue or some kind of problem in the hub firmware or SmartThings backend.
Fortunately, for me anyway, I rely on webCoRE and node.js for 99%t of my Sonos automations.
@nayelyz Access granted for 1 month, additional info:
V2 Hub, Android, UK with all software, ST and Sonos, up to date.
Sonos is on it’s own network with a Sonos Boost as the wired access point to my main network where the ST hub resides.
I have only noticed the issue with the Bedroom Sonos which is my only stereo pair. However it may have been occuring on other speakers and I havn’t noticed - Bedroom and Kitchen get the most use through ST.
I have experienced no dropouts from Sonos itself or from an IKEA hub used to enable paired, old style, Symfonisk remotes for each Sonos instance which, for the room in question, continued to function.
Thankyou, if I can be of any further help please just ask
Il throw my Sonos S1 speakers into the not correct in various ways hat
Even trying to on board the speakers was hit and miss
Scan nearby found only 2 speakers, subsequent scan nearbys found more but again not all, took about 4 scan nearbys to find all speakers
On boarding via Sonos manufacture link did seem better but again not all found in a single on boarding.
Favorites is greyed out on all speakers.
Currently playing audio from Tunin does not display on any speaker.
Notifications do not work (S1) which these days means that will probably never happen for whatever resson.
Speaker tile occasionally shows speaker off line but if you chsnge room and then go back to same room it shows on line
Volume of speaker and group volume appears to function ok even if the device appears to be not playing due to lack of album art or scrolling track info
At the moment i am not willing to hard reboot, electronics do not like power being cut and restored and with the V2 hubs not easily replaced a rebuild of everything is not what i want to be doing in my life if i had to source another v2 so i will wait on a reboot until we get the software option returned
@nayelyz access is always granted if you need to take a look at the hub logs, email on here is the same
Yeah my Sonos S1 integration is also pretty dead since 12th of July (six speakers in various groups). I was wondering why all my voice notifications stopped working and my remote controls hooked up via Sharptools and ST app also stopped working, but didn’t have time to look into it since now. I can still see the Sonos tiles in the ST app, but they are unresponsive and some started displaying offline when I tried to push them a bit. I did try power hub on and off, as well as the Sonos speakers (all Wifi connected).
Now I need to find the mental strength to deep dive into this rabbit hole again as the whole Sharptools integration I did with mapping up a lot of buttons on several remotes and commands was quite complex and a real time sink.
Below is a list of known devices which will be affected by the migration away from Groovy DTHs to Lua Edge drivers**.** Some devices may lose partial functionality or full functionality within the SmartThings app. These devices may continue to work outside of the SmartThings app.
Sonos
Older models of Sonos speakers
These devices may not continue to support the playing of audio notifications in the SmartThings app.
A bit of progress, now at least I got my Sonos S1 working in the SmartThings App again. I tried many things (reboots, removing, driver fiddling, sonos app network configuration etc.) and don’t know if it was just a confidence, but what seemed to do something was:
My Sonos S1 setup was running purely on Wifi. When you initially setup a Sonos S1 system you do need to be connected with ethernet (LAN cable), but once connected it’s not needed anymore. My Sonos had been running without ethernet for ages. I then connected one speaker to ethernet which was then suddenly responsive in the SmartThings App.
I then in the Sonos App grouped all of my speakers (ethernet and wifi) and played some random playlist, hoping they would somehow connect better. Before that I spend a 30min trying to remove a couple of Sonos wifi speakers and re-add them, but to no avail.
After the grouping I could find the wifi connected speakers I experimentally removed (by searching for brand Sonos in the ST app), and the wifi Sonos speakers I didn’t remove was again “online” and responsive in the SmartThings App.
Might just have been a coincidence and could be that some other stuff I did fixed this with some delay, but for anyone else troubleshooting it could be worth a shot.
Now I need to have a look at my routines and Sharptools integration… Looking into the migration guide it seems like I won’t be able to get Sonos S1 and voice notifications working again with current drivers (Did Sonos sponsor this in order for me to finally use my 30pct discount to “upgrade to Sonos S2” ? )
Update: Once I ungrouped them very weird things happened… like it slowly feel apart again… with speakers becoming unresponsive and marked as offline
Be careful if power cycling S1 Play5s, they have a known weak point in the electronics, i think its a certain capacitor, it will blow, especially as the play 5s get older, they are fixable with a better capacitor but it does take a decent Sonos specialist to do the job
Meh, it is annoying not having that but we have Amazon Echos around the place which are easy enough to get to do the same job or if you really get bored it is possible tp select an alarm sound from spotify, add it in your library and then use that in an automation
Thanks for the tip Mike I have actually been power cycling those super power hungry 1st gen Sonos devices (with automation of course). I’m in Copenhagen where energy prizes are a bit looney tunes, specially lately with everything being “war” taxed here
Amazon Echo is not really supported in Denmark. Currently I’m toying with some different options
Try get voice notifications work with my two Google Home Mini speakers (supported in Denmark!). I can see there’s something about you can do that with virtual switches. With this option I still fear that just getting basic music functionality working with Sonos S1 again, is deep in the backlog of the dev team (and might remain there)
Look for some other homebrew edge driver for Sonos S1
Getting rid of all my Sonos S1, not really going for Sonos S2 but finding an alternative (So I’m not stuck again on some Sonos S2 ship when a new S3 sets sails )
Migrate to Home Assistant, more chaos but less $ agenda driven
Maybe tryout the new Google script editor for google home automation, if it’s worth migrating to. It seems only to be cloud though where I did like SmartThings going for running more locally
Fork the edge driver code and do a proper Sonos S1 edge driver myself in spite!
Wait a month or so, and see if Sonos S1 integration have improved before going for one of the above, but probably fixing voice notifications somehow for safety reasons. Which I hope that whom ever is product owner of SmartThings realize, that when you break voice integration and other stuff, you potentially make our homes less safe and such, if your users are relying on this functionality
)