Could you please confirm whether you already sent the hub logs?
And if you saved the driver logs, could you please send them as well so we can analyze them together?
Ok, here’s another fun thing to try.
Open the Sonos app, select a speaker. Open the SmartThings app and select the same speaker (device).
Play some content.
Using ONLY the Sonos app to adjust the volume, the volume does change and the level changes instantly in the SmartThings app. You can do this over & over, either sliding or stepping in the Sonos app. This seemed to work without issue - I was even able to use the Harmony remote to change the Sonos volume and all apps acted as expected.
Now try controlling the volume using the SmartThings app, either stepping or sliding. The Sonos app will not react to the changes from SmartThings without a significant delay. If you’re sliding, only one delay occurs. A step adds a delay for every press.
Any volume changes you’re trying to make in the SmartThings app are getting queued into that delay, so if you attempt a few changes, get ready for a volume smorgasbord with each change taking the same amount of delay time.
So it appears that SmartThings is reacting instantly, properly and as expected to changes made in the Sonos app. But changes made in the SmartThings app are encountering (introducing?) the delay.
1 Like
I’ve got the same with mine, been about a month now, at last found somebody else with the same issues, has anybody got anywhere with this yet
Cheers Dave
I’ve just sent you my dump logs off the hub, you still have access to my hub from a while back, I have the beta firmware on hub but this problem has been here for a month or so
That tracks. I think it started about a month ago.
Hi @uncledaveghr
To help the team identify the issue, could you please share the following details with us?
- Timestamp: the exact date, time, and time zone when the delay occurs.
- Step-by-step description: what exactly happens during the delay (for example, which device triggers the alert and which automation or routine is involved).
I too have noticed delayed notifications with my Sonos speakers. It seems to have started when the new driver version 2025-12-08T22:56:34.184279263 installed.
Another tidbit to add:
As part of monthly maintenance here, I shut down & restart my network and all devices, hubs, etc. I usually encounter minor problems getting some devices or routines back to running as expected, but this time around SmartThings & Sonos communication didn’t come back at all. After an hour or so of fiddling around, I decided to just UNLINK & RELINK Sonos. This hasn’t been a problem in the past and always resulted in eliminating the SmartThings/Sonos delay, at least for a while.
This time, however, I could not get Sonos to respond to the link request at all. Tried it a couple of times, but all I got was a spinning process indicator with no progress. I finally resorted to trying to link the S1 version instead. The link happened almost instantly, and all speakers & routines were eventually restored, but the delay problem remained with no improvement.
Also: one of my routines checks the MUTE status of a Sonos device and alters it if necessary. This routine works instantly with no delays. The only time I’m seeing delays are when trying to adjust the Sonos volume level or trying to play a notification.
If anyone is following this thread, the delay problem seems to have been corrected today. No idea what changed, let’s see how long it lasts!
2 Likes
I have been following this thread as I control Sonos quite a lot through ST.
Oddly enough I noticed this issue for the first time at about midnight this morning (UK).
Actions and announcements delaying (and queuing) for 20/25 seconds before announcing and, after a further delay/period of silence (5/10 seconds), returning to playing source…
I was just about to replicate and produce a diagnostic (9 hours later) as it was still apparent but rebooted my hub first… it seems to have resolved with the reboot 
Monitoring…
Interesting. I didn’t reboot/reset my hub and there’s been to power outages here. Regular scheduled hub & network resets hadn’t corrected the issue in the past. Even the unlinking/relinking of ST & Sonos services (which DID correct the issue for a short time) didn’t fix it on the last attempt.
In my circumstance, this problem just seems to have gone away. Like I said, we’ll see…
Still a problem for me. Seemed to be OK yesterday but back to large delays again today 
Well it didn’t fully resolve with a hub (v2) reboot as mentioned/hoped for previously.
This has definitely become a thing for me now too, having been unaffected it suddenly manifested some time overnight on the 16/17th Jan. GMT (UK) and has remained since:
- Delay to announcing anything
- Delay to actioning a request (in addition to announcement delay)
- Announcement getting ‘lost’
No changes, that I am aware of, to my network but there was a Sonos firmware update earlier in the week. Other things, Sonos itself, Ikea etc. remain properly functional…
Bit pressed for time currently but will try a full network reboot (router, switch, wifi ect.) at some point and see if that has any impact. If not, @Itati , is there anything I can provide to aid investigation?
I’ve just encountered this - the problem starting in the last week. V2 hub and Era100.
It’s not just notifications and not something with the app - as it affects routines trying to play etc, as well as app actions like start/stop/volume. Sonos app and Alexa controls aren’t affected.
The delay is close to 30 seconds - so although what triggers it may not be clear the result seems very consistent among users.
I see there’s mention of a recent 0.59.9 f/w release in case that relates.
I was able to resolve (for the time being) by a power cycle of the hub.
1 Like
I got a temporary reprieve doing a reboot of the hub…Sonos was very responsive for multiple commands via ST app (routines, direct control from device tile)… This was 2 days ago. Today, it’s back to the 30 second delay. Here’s a snip from the hub log for the sonos driver while trying to do a mute command from the Smartthings app (I’ve obfuscated the device id to all xxx’s). You can see the 30 second delay at the token expired message. Happy to upload any more info or hub logs etc if helpful to debug
Select a driver. 13
connecting… connected
2026-01-18T17:03:42.876724366Z TRACE Sonos Received event with handler capability
2026-01-18T17:03:42.884069537Z INFO Sonos <Device: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (Sonos Connect)> received command: {“args”:{},“capability”:“audioMute”,“command”:“mute”,“component”:“main”,“named_args”:{},“positional_args”:{}}
2026-01-18T17:03:42.885624689Z TRACE Sonos Found CapabilityCommandDispatcher handler in Sonos
2026-01-18T17:04:12.916052819Z WARN Sonos notice: wait_for_oauth_token → token expired
2026-01-18T17:04:12.917514258Z DEBUG Sonos Sonos Connect all connections running? {coordinator=true, mine=true}
2026-01-18T17:04:12.918286936Z DEBUG Sonos Sending command over websocket channel for device Sonos Connect
2026-01-18T17:04:12.921183759Z DEBUG Sonos Sonos Connect device thread event handled
2026-01-18T17:04:12.926919875Z TRACE Sonos Sending message over websocket for target sonos_xxxxxxxxxxxxxxxxxxxxxx.zwlxxxxxxxxxxxx/rincon_94xxxxxxxxxxxxx
2026-01-18T17:04:13.008021281Z TRACE Sonos Received WebSocket message, fanning out to listeners
2026-01-18T17:04:13.010082436Z DEBUG Sonos SonosConnection for device Sonos Connect handling websocket message
2026-01-18T17:04:13.012178692Z DEBUG Sonos OnMessage for Sonos Connect
2026-01-18T17:04:13.015083893Z DEBUG Sonos Message for Sonos Connect has data
2026-01-18T17:04:13.025562422Z TRACE Sonos Received WebSocket message, fanning out to listeners
2026-01-18T17:04:13.027720125Z DEBUG Sonos SonosConnection for device Sonos Connect handling websocket message
2026-01-18T17:04:13.029760103Z DEBUG Sonos OnMessage for Sonos Connect
2026-01-18T17:04:13.033505099Z DEBUG Sonos Message for Sonos Connect has data
2026-01-18T17:04:13.036473375Z TRACE Sonos PlayerVolume type message for Sonos Connect
2026-01-18T17:04:13.038707032Z INFO Sonos <Device: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (Sonos Connect)> emitting event: {“attribute_id”:“volume”,“capability_id”:“audioVolume”,“component_id”:“main”,“state”:{“value”:54}}
2026-01-18T17:04:13.053702318Z INFO Sonos <Device: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (Sonos Connect)> emitting event: {“attribute_id”:“mute”,“capability_id”:“audioMute”,“component_id”:“main”,“state”:{“value”:“muted”}}
2026-01-18T17:04:13.076089881Z TRACE Sonos Received WebSocket message, fanning out to listeners
2026-01-18T17:04:13.076889447Z DEBUG Sonos SonosConnection for device Sonos Connect handling websocket message
2026-01-18T17:04:13.077554947Z DEBUG Sonos OnMessage for Sonos Connect
2026-01-18T17:04:13.078209774Z DEBUG Sonos Message for Sonos Connect has data
2026-01-18T17:04:13.079424214Z TRACE Sonos GroupVolume type message for Sonos Connect
2026-01-18T17:04:13.082545232Z INFO Sonos <Device: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (Sonos Connect)> emitting event: {“attribute_id”:“groupVolume”,“capability_id”:“mediaGroup”,“component_id”:“main”,“state”:{“value”:54}}
2026-01-18T17:04:13.093858136Z INFO Sonos <Device: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (Sonos Connect)> emitting event: {“attribute_id”:“groupMute”,“capability_id”:“mediaGroup”,“component_id”:“main”,“state”:{“value”:“muted”}}
1 Like
The benefit of the power cycle lasted for around 24hrs or so before the 30 sec delay returned. A hub restart from the advanced web cleared it again but a daily restart isn’t practical.
The issue has been reported for a while now and seems to be increasing so no idea why it hasn’t been fixed.
1 Like
Add me to this sad list.
I also have the 30-second dalay but it worked great on the evening on January 14 while there was a SmartThings update going on. Sadly, it’s back to the 30-second delay again.
Yes, rebooting the SmartThings hub fixes everything for a certain period of time, but not permanently.
If anyone gets a fix to this, PLEASE post it!
I am affected by this also. Seems to be related to the 0.59 firmware update. The workaround I found was to login to the advanced portal via my.smartthings.com, pick one of your SONOS speakers and change the driver to JBL, wait a few seconds and then change it back to SONOS. No idea why it works, but it seems to last until the next day. Hopefully a proper fix soon, the delay is almost exactly 30 seconds.
4 days, no delays here. Still keeping my fingers crossed. 
Tried the driver replace route, it worked for me too but only lasted a few hours… Hopefully there is some resolution around the token expiry issue mentioned previously 