Last driver update set my Sonos offline again…
Last driver update set my Sonos offline again… when might we expect a fix for this?
Yup, mine have been “partially” offline since the 2023-3-14 update. Some controls are working; some are not. It’s very odd.
There is some ongoing activity on this driver in GitHub with regard to “device initialization,” but whether that’s related or not to this particular issue, I couldn’t say. There are still unresolved backend issues as well.
Hi @troy_owens Does the issue happen after rebooting the hub?
Hi @bthrock,
Can you share more information with us about these problems?
1 Like
The issue with the speakers occasionally not responding to controls in the app isn’t new by any means (one of the SmartThings engineers working on the driver has said he’s experienced this himself) but this was the first time I noted that only some controls were non-responsive. For example, at the time I posted I could pause/play the speakers through the app, but adjustments to the volume control were ignored. I had never seen that particular behavior before, but that doesn’t mean it hadn’t happened before and I just didn’t catch the distinction.
This morning, my speakers were not responsive again. In this particular instance, the play favorite command was being ignored. I didn’t test any other commands, just went to the Sonos app and got things working from there.
As for the “backend” issues, I was specifically told that the inability to play favorites my names in routines with this driver “is actually a platform bug upstream of the edge driver.” Probably “backend” was probably the wrong term , and in any event it was an offhand comment unrelated to the issue that Troy was raising and I should have omitted it.
It’s totally random with no interaction
1 Like
Lol, that describes it perfectly in a lot fewer words!
1 Like
One thing I’ve noticed is that when commands don’t seem to be responding, if I go into the Sonos app and do something to interact with a player/speaker, the ST app will then start responding.
Sounds like some CLI driver logging might be in order here to help figure out what is going on.
1 Like
Ok, so I did a little 
When the device seems non-responsive in the app, I see that the hub receives the command from the cloud and I notice that there is no event emitted from the device after the command is “supposedly” sent.
2023-03-21T22:56:08.644862181+00:00 INFO Sonos <Device: b99ebbfd-fc49-4294-8cff-83bd20bdf42e (Kitchen)> received command: {"args":{"volume":36},"capability":"audioVolume","command":"setVolume","component":"main","positional_args":[36]}
2023-03-21T22:56:08.648384848+00:00 DEBUG Sonos Kitchen device thread event handled
Then, once I poke the device in any way from the Sonos app, the ST app becomes responsive again and when commands are sent, the device emits an event.
2023-03-21T22:57:06.474444168+00:00 INFO Sonos <Device: b99ebbfd-fc49-4294-8cff-83bd20bdf42e (Kitchen)> received command: {"args":{"volume":40},"capability":"audioVolume","command":"setVolume","component":"main","positional_args":[40]}
2023-03-21T22:57:06.484092022+00:00 DEBUG Sonos Kitchen device thread event handled
2023-03-21T22:57:06.548056355+00:00 INFO Sonos <Device: b99ebbfd-fc49-4294-8cff-83bd20bdf42e (Kitchen)> emitting event: {"attribute_id":"volume","capability_id":"audioVolume","component_id":"main","state":{"value":40}}
2023-03-21T22:57:06.626091043+00:00 INFO Sonos <Device: b99ebbfd-fc49-4294-8cff-83bd20bdf42e (Kitchen)> emitting event: {"attribute_id":"mute","capability_id":"audioMute","component_id":"main","state":{"value":"unmuted"}}
It almost behaves like a stale open connection between the hub and the Sonos device that “refreshes” or “wakes up” when the Sonos device emits events based on commands from the Sonos app. I haven’t looked at the driver code, but I would have presumed that the communication between the hub and the Sonos device would be stateless, but who knows. Or it could be that the driver is periodically losing some bit of info about the Sonos device that it needs to transmit properly and when it receives an event, the information is now available.
All in all though, seems to me that this shouldn’t be that hard an issue to track down.
1 Like
Yes, I’ve seen the same behavior .
Interesting, I haven’t tested that combo. I did try some UPnP commands from my node.js, but while the devices responded appropriately, those commands didn’t “wake” the connection between the hub and the device.
That’s a great description. 
I’ve recently noticed that a sonos commands via routines (not moved to Edge according to the IDE), don’t appear to be executing. For instance, I’ve got the routine configured to set the volume low when it is first turned on (as using sonos beam for streaming and a TV cause very different volume levels to be set as the initial volume). This approach had been working effectively before, but not in the last week or so, this no longer appears to be working. Is this related to the other issues noted here?
Although I wouldn’t trust the IDE for much of anything these days, unless you downloaded the Edge driver manually, it’s reasonable to assume you’re still on the DTH. Still, you can easily check by looking for the “driver” option in the device presentation if you want to be sure.
Unless your devices were somehow migrated, it seems unlikely that your issue is related, as the problems noted above been ongoing for much longer, but honestly I don’t think anyone here not employed by SmartThings can answer that definitively.
Both the sonos and ecobee have C2C integrations- and in my case, they both appear to have been moved, but neither show “driver” should driver show up for C2C integrations that are running under edge?
cloud to cloud intergrations do not use Edge drivers and Driver would not appear under the 3 dots (More options) for them
1 Like
so at this point, the place holder indicator is the best indicator that these have been moved to the new architecture?
instead of IDE, this may be a better choice to find info:
yes, Placeholder can indicate: (1) it is using an Edge Driver or (2) it is a cloud to cloud integration using the new architecture
An update to the Sonos driver posted yesterday eliminates the onboarding issue wherein every “scan for nearby devices” would repeatedly onboard the secondary speaker(s) in a bonded set.
As for the issue with speakers going offline due to a stale connection or some other cause, the PR that was merged does not address this issue. At present, there are no pending requests or open discussions that I am aware of that address this issue specifically.
The favorites issue (allowing routines & rules to use names instead of IDs to play favorites), is currently marked as “won’t fix,” but I hope this can still be addressed down the road, along with the ability to set audio notification volume.