All my SONOS devices appearing OFFLINE to ST … I’ve tried power off /on both my Hubs and SONOS devices to nil effect .
I notice the Driver has changed to 2025-06-09T19:06;57.951558407
I lost all my ZIGBEE devices last night at 8PM but by morning most have re-paired .. a few needed re -pairing .
So I suspect some update has been performed … Anyone else affected ???
@glowworm There is/was an issue with the beta driver which is not present in production. See:
Sonos also had an update and my suspicion is that Sonos makes no effort to comply with ST.
1 Like
I’ve not updated SONOS and I’m on V1 … strange the new ST hub Driver bears the date of the 9th June 2025 ??? and ST are rolling out 57.14 Firmware … which I now have.
@glowworm That driver (2025-06-09) is the beta driver (see above). Production driver is dated 2025-04-07 and, for me, it is working without issue - although I am totally upto date on Sonos v2.
Looks like you may need to switch drivers, again see above referenced thread, or at least give it a go and see if it addresses your issue. If it does it may be worth flagging with development 
Yep … I’ve just reverted to 2025-04-07T19:30:36.011152122 and Bingo may SONOS devices are back online …Other than the one I manually removed to test fixing it :frowning 
SO ST DID COCK IT UP ???
1 Like
Yeah but on Beta and not in production so forgivable… 
Probably worth adding a comment to the other thread noting your issue and that you are on v1 of Sonos…
1 Like
This latest glitch is the result of some structural refactoring in the beta driver, and as @TheHundredthIdiot notes, is easily solved by moving to the production driver.
Just to draw a distinction, unlike the ‘new’ Sonos app, SmartThings—as well as Hubitat, Home Assistant, and more—use a locally-based WebSocket solution, and none of Sonos’ many issues and updates over the past year have had any impact on WebSocket or even older UPnP implementations. They have remained untouched and rock-solid throughout.
While there is no reason to expect that any of this will change in the near future, given Sonos’ recent history, I make no predictions. 
2 Likes
@bthrock do you think it’s possible the work being done on the driver will stop it crashing when speakers are grouped/ungrouped? Would be nice if it did.
This isn’t something I was aware of and haven’t experienced it myself, although to be fair all my Sonos automations/controls are handled separately from SmartThings because the ST driver is just too basic for my purposes. If other users are aware of these crashes, perhaps they can jump in here.
With that said, nothing in the recent changes to the driver code suggests it’s a fix for what you describe, but I am anything but an expert on Edge drivers.
1 Like
@glowworm Thanks for the report on this.
We were able to reproduce this and get a fix up. As has been indicated, this was on the Beta version of the driver, so some breakage is to be expected. Some of the recent refactors to the driver introduced more stringent error checking on some of the responses that speakers would send back to the hub when we send a command. Some of these checks were relying on data that looks different if a speaker is connected via the S1 Controller app as opposed to the Sonos/S2 app.
I wasn’t able to catch this as early because I don’t actually have any speakers that can be onboarded to the S1 app, all of my test devices are too “new”. But after your report, our QA team was able to reproduce this with some speakers they have in their QA lab. I was able to borrow an S1 compatible speaker from a friend over the weekend, and we should have a fix on Alpha later today, Beta some time later this week 
do you think it’s possible the work being done on the driver will stop it crashing when speakers are grouped/ungrouped? Would be nice if it did.
This is something that happens rarely on the production driver, but it was something we were able to track down, and initial review of crash reports from Alpha/Beta Driver Channel populations shows that this has stabilized significantly.
3 Likes
Thanks for your prompt action Doug… I didn’t realise I was still running on BETA … dates back to the problems we all encountered when EDGE drivers were implemented. Cheers Keith
1 Like
Dang- my Sonos announcements had stopped working so about 2-3 weeks ago I realized I was on the beta drivers channel and there had been an update dated about the time they stopped.
I unenrolled from the beta drivers channel and all of my speakers/notifications worked again after that when the speakers switched to the main channel drivers.
And then about a week ago they stopped working again, and I just checked the drivers and the main drivers have now been updated to 2025-06-27T15:20:51.
Was it expected that the main channel drivers would get updated with the broken beta drivers? I would have expected the update to be held until the beta was fixed? Anyone using beta and things working and now I need to re-enroll in beta? Frustrating!
I discovered a new option in the latest version of Android Smartthings that I when I turned it on notifications started working again … My old phone Android 10 wouldn’t take the new SMARTTHINGS so I had to buy a new ANDROID 13 phone 
Found your other post, Routine notifications via SONOS Stopped Working - #4 by glowworm, but do you have any more details on what/where the setting was that started your voice notifications working on Sonos again, with the latest 2025-06-27 stable drivers?
Is it the “Appliance notifications” (Receive notifications for appliance activities, detected events, and more." toggle within the “Notifications” menu? Just tried turning that on and we’ll see if my rules which create spoken text notifications will start working again. If that works, I’ll have to change the setting for all of my speakers?
Yes .. that’s it “APPLIANCE NOTIFICATION” on each speaker… just tested mine are still working.. so try it
I made the change yesterday to turn on appliance notifications for all of my speakers, and they still don’t seem to be playing notifications. When I “edit” and then test routine actions, where there is one phone notification action and one speaker notification, I’ll receive the notification on my phone but nothing plays on the speakers. So it doesn’t appear to have fixed my situation. I guess I’ll try switching back to the beta device driver channel.
Related?
I was wondering which version of SONOS … As stated earlier I’ve kept running SONOS V1 … checking my Hub SONOS Driver it’s now 2025-07-09T15:54:29…So I’ll check again tonight 
… All my notifications are set to after SUNSET