Over the last month I have been trying to troubleshoot delayed Sonos notifications. When an alert is triggered, like “The garage door is open” the Sonos notification is about a minute behind the sensor being in the open state. This is for all notifications. I have restarted my router, my eero WiFi network, the hub, my Sonos speakers and nothing seems to work.
I have looked across the for forums but I haven’t seen any cause or fix. Any ideas what could be causing this?
Hi,
quick question, did you happen to make any recent changes to your environment that could have caused interference (new devices, network changes, physical relocation, etc.)?
If not, we may need your help gathering some additional information so we can investigate further.
Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
Thanks @Itati. I have not reached out to support but I’ll pull the logs today. I have not made any changes to my network setup and I have not added any new devices.
I have also checked that the ST app is tracking the trigger. The triggers show in the app, is the SONOS notification that is delayed, by 30 seconds or more.
@Itati Just to confirm; I have dumped the hub logs and ensured that I have enabled access to my account.
One example is my Door to Garage was opened and closed twice at 7:27p PT yesterday (Sun, Dec 7) and the SONOS notification was delayed 30 seconds to 45 seconds. After both open triggers.
Hi @JBR
Could you please let me know if you sent the hub logs right after the routine ran, or if you waited until the next day?
Sometimes the logs don’t last more than 12 hours, so I want to make sure we received them in time.
Ah, good point. No, I did not pull them immediately.
I did unplug all my networking equipment: Xfinity router, all three eero APs and my ST hub which seems to have fixed the problem. I’ll keep an eye on it and pull logs as soon as it happens again. This is the second instance in the last six weeks. The unplug method only works for about a week until the delays shows up again.
Hello! I have the same problem. My Sonos IKEA symfonisk bookshelf Speakers are delaying notifications and music commands, ie start a favorite, change volume etc. As a temporary workarroung, I go to the Smartthings App, change the Speakers driver to something else, ie Boss or JBL and then back to Sonos Driver. My Speakers are working fine for a day or so an then again they star delaying. Have you find any solution?
Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
I’m experiencing the same issues. All my OS’s and apps are up to date. I have deleted and reinstalled SmartThings & Sonos. I have unlinked and relinked SmartThings & Sonos. (This is a pain in the ass, because although the Sonos devices reinstall with the same names, routines that use them need to be edited in order to restore them.)
Interestingly, following the relink, routines work as expected with very little Sonos delay. However, after a day or so, the lag creeps back in. I’m experiencing notification & control delays of about 30 seconds.
There are no delays with any other linked services.
I would like to add some more detailed findings from my side, in case they help with debugging.
My Sonos device (IKEA Symfonisk bookshelf speakers, named “Speakers”) works perfectly in the Sonos app at all times (wired via Ethernet), so the issue does not appear to be related to network stability or the speakers themselves.
Using smartthings edge:drivers:logcat, I exported and reviewed the logs. From the log output, it appeared that the Sonos integration was encountering authentication / session-related issues (OAuth token or key expiration / invalidation). After disconnecting and reconnecting the Sonos service in SmartThings, the system immediately returned to normal operation: commands were executed instantly and without delays.
However, after approximately 24–48 hours, the same behavior consistently reappears:
noticeable delays when sending play / pause or preset commands
commands eventually execute, but with significant latency
no errors in the Sonos app, which continues to work flawlessly
I tested the newer Beta Sonos driver (released Dec 1, 2025) as well. The behavior is very similar: after reconnecting or switching to the beta driver, everything works correctly for a short period, but after a day or two the delays return.
At this point, usage is minimal (only basic play/stop commands, no TTS, no heavy automations), yet the degradation still occurs over time. This suggests the issue may be related to long-lived sessions, token refresh, or stale subscriptions on the SmartThings side rather than command volume.
Thanks for your post and for further investigation. I’ve got to believe the problem is on the Sonos end, as no other linked services are exhibiting delays.
For more clarification, here’s one scenario I’ve got that’s negatively affected:
I’m using a Harmony remote & hub with SmartThings integration. When I switch A/V activities, I like to make sure the Sonos volume isn’t excessive. There’s no way to set the volume directly within the Harmony app, so I’ve set up VIRTUAL SWITCHES in SmartThings that get trigged when an activity is selected in Harmony. Routines in SmartThings detect the virtual switch state & will adjust the Sonos starting volume accordingly. The virtual switches are reacting instantly, as expected, but the delay to adjust/control the Sonos devices can be as much as 30 seconds.
Routines aside, trying to control the Sonos volume directly via the device icon in SmartThings also encounters delays. Conversely, when adjusting volume in the Sonos app, those adjustments aren’t mirrored in the SmartThings app without the delay.