Have SMARTTHINGS cocked up SONOS again?

[glowworm (Keith)]

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 ???

[TheHundredthIdiot]

@glowworm There is/was an issue with the beta driver which is not present in production. See:

Sonos status reporting and control issues (loss of)

Hi, after some curative ideas. Everything ST and Sonos on up to date app and firmware versions except my ST (v2) hub which is still awaiting latest firmware update… The issue: Yesterday I switched my ISP and was without internet for 5/6 hours from about 01:00 (UK). The ISP change was only a reprovision to another provider so other than a username/password change on my equipment there was absolutely no hardware or configuration changes. Before the switch all was working properly but when everything came back on-line with the new provider my Sonos speakers are no longer updating status and can not be controlled by ST. I have tried all the usual fixes, rebooting everything, removing/adding and resetting selected speakers from both ST and Sonos. Nothing seems to work. I even tried changing…

[danfelix (Dan)]

Sonos also had an update and my suspicion is that Sonos makes no effort to comply with ST.

[glowworm (Keith)]

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.

[TheHundredthIdiot]

@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

[glowworm (Keith)]

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 ???

[TheHundredthIdiot]

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…

[bthrock (Bob)]

@danfelix

Sonos also had an update and my suspicion is that Sonos makes no effort to comply with ST.

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.

[granite]

@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.

[bthrock (Bob)]

@granite

do you think it’s possible the work being done on the driver will stop it crashing when speakers are grouped/ungrouped?

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.