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 WiFi channels but to no avail.

All speakers show as on-line in the app and the advanced web app and when a speaker is removed/added from ST or Sonos it is (after a shortish period) automatically rediscovered in ST. All routines (and command requests from the web app) appear to execute correctly from a user pov (not looked into logs). Speakers are stuck on last recorded status prior to the ISP change and all fail to respond to ST requests.

Everything else on my network works as it should with ST, including Hue and other LAN devices, and everything is on fixed IP’s. All other apps/hardware interacts perfectly with Sonos (Sonos itself, Phonos, Ikea…). Apart from ISP user/password nothing has changed.

Any ideas anyone, I really rely on my various Sonos integrations :frowning:

3 Likes

Do you assign static IPs to your ST hub and to the Sonos speakers? Try that and reboot everything including Router.

I’m having the same issue. Yesterday Sonos seemed to stop working. I did all the normal trouble shooting, rebooting devices, router APs etc. If I reboot the ST Hubv3 the speakers will work for about 15 minutes, then stop. When I look at the Sonos devices in the ST app and check the driver, I see the driver version updated to version 2025-6-02T20:50:12.11244068. Checking the GitHub for the Smartthings Edge drivers I see there were changes made to the Sonos drive 2-4 days ago. I now see there is a new firmware rolling out: Aeotec Smart Home Hub/2018/2015 Model Hub Firmware Release Notes - 0.57.13

I don’t have this version, my version is 56.11.

I’m thinking I got the new driver, and not the new firmware so things are broken. I hope I get the new firmware and things go back to normal.

1 Like

Hi @jkp,

I’ve static IP’s assigned to everything permanently on my network, wired or otherwise. This includes the hub and all speakers.

I have discreet modem, firewall/dhcp, WiFi and a managed network switch. Rebooting individually or en masse has not worked. I also tried moving the ST hub between switch, firewall/dhcp and wired to a WiFi hub… no joy there either.

I am out of ideas, really beginning to think it is an issue within ST or somehow associated with internet outage/ISP change. Especially as a speaker deleted from ST was discovered by ST as if new - but still without status/control.

My LAN side has been working well and consistently. All was fine across a previous ISP change, again user/password only, back in February this year. In Feb only a +/-30 minute outage though, otherwise no different from my PoV as this time :thinking:

(just retried a few targeted reboots, including a speaker - no change…)

@RandomName Good spot that, I have the same driver version too:

Hopefully this is the cause as I am also on the older firmware.

Tagging @nayelyz as this is possibly an ST compatibility issue?

1 Like

You mentioned rebooting… Try powering down the V2 hub for a few minutes. Remember to remove any batteries.

Tried that too - a couple of times :-1:

Hey all. Just wanted to let you all know we are looking into this and I’ll let you know if there are any updates.

For now, we suspect the issue isn’t in production and is only in the beta driver channel, so if you are in the beta channel and are looking to resolve this ASAP you can try switching to the production driver. If this for some reason doesn’t help or you are seeing it in production please let me know.

If you are willing to reproduce the control issue, push hub logs via the option in the advanced users interface, and DM me your hub serial or ID I’d be happy to investigate your specific instance as well to help speed up the resolution.

2 Likes

@Michael_ST I’m not using the beta driver, at least I don’t think I am when I check the driver it doesn’t show the beta channel like TheHundredthIdiot’s screenshot. I’d be more then happy to send any logs to you, not sure if I can DM since I registered just for this issue and I’m a new user. Let me know how you want to proceed.

Hi @Michael_ST thanks for your response. To confirm that, for me, switching to the production driver:

seems to have resolved the issue. My ISP change by chance must have coincided, + or -, with the driver update :roll_eyes:

I am out of time today but tomorrow I’ll see if I can switch back and get some logs/further diagnostics for you :+1:

1 Like

Memory leak?

There were actually a couple issues we worked on with the Sonos driver in the beta channel and TheHundredthIdiot and RandomName perfectly split between two of them, which actually helped figure out the issues :grinning_face_with_smiling_eyes:.

We’ve got some fixes lined up to resolve the issues in the beta channel and production will continue to function as expected and is unaffected.

4 Likes

I removed the Beta Edge channel from my hub but my Sonos driver is not being updated. It remains at version 2025-06-02. How can I revert to the working driver on then main channel?

@pomartel Go to the production channel (via Hub - > Drivers) and install the Sonos driver listed there. It should automatically replace the beta version :+1:

@TheHundredthIdiot Thank you for your answer! The thing is I removed the Beta channel but I’m not enrolled in the main channel. I can’t find a working link (and I’ve searched) to enroll back in the main SmartThings channel.

Production Channel

2 Likes

@pomartel I always understood that all hubs are automatically subscribed to the production/default channel. So you cannot join it like the Beta channel but you can access it to manage drivers. Just like any other channel.

Someone else here may be able to offer more insight though… ah, as posted above while I was typing :roll_eyes:

@TheHundredthIdiot Thanks for kindly taking the time to help me with that! Re-enrolling the Production Channel with the link provided by @bthrock did the trick. My Sonos speakers automations are working again! :sweat_smile:

3 Likes

@pomartel I have the beta driver, but it doesn’t show me joined to the Beta Channel. Did you just re-enroll in Prod and were able to change the driver?

@RandomName Removing the beta channel and adding back the prod did the trick for me. I also read somewhere in the forum that you should try to remove the Sonos driver. It will inform you that it cannot be deleted since it is being used by a device. But this should (maybe?) trigger an update.