# Sonos alerts sometimes trigger wrong resume state **URL:** \ **Category:** SmartApps & Automations\ **Tags:** sonos\ **Created:** [November 22, 2018, 4:24pm UTC](https://community.smartthings.com/t/sonos-alerts-sometimes-trigger-wrong-resume-state/143220 "2018-11-22T16:24:40Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![fsckit](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/fsckit/32/94458_2.png) [@fsckit](https://community.smartthings.com/u/fsckit)\ **Post date:** [November 22, 2018, 4:24pm UTC](https://community.smartthings.com/t/sonos-alerts-sometimes-trigger-wrong-resume-state/143220/1 "2018-11-22T16:24:40Z")
I have a SmartThings v2 home security kit. I’ve set door open detectors to play a tone on my Sonos devices in various parts of my home (Play 3, sound bar with play1 surrounds, and two Sonos Ones). Tones play appropriately in all of the places I expect them to. The automations are set to resume playing the previous audio after the door chime sounds. However on the Sonos One on one floor and the Sonos One grouped with the Play3 on another floor when nothing is actively playing on them, sometimes after the tone plays the automation will trigger the sonos to start the last thing we had playing. This happens maybe 1 time in 10. It does not happen on the sound bar as far as I can tell so it makes me think it’s a race condition specific to the Sonos Ones. This basically means that sometimes we’ll come home to find that music has been playing all day which is annoying. Has anyone experienced this? Any ideas on how to fix it or at least gather enough info for whoever I should be filing a bug report with? Thanks! ---
**Author:** ![Dechlan\_jacobs](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/dechlan_jacobs/32/96123_2.png) [@Dechlan\_jacobs](https://community.smartthings.com/u/Dechlan_jacobs)\ **Post date:** [January 19, 2019, 4:14am UTC](https://community.smartthings.com/t/sonos-alerts-sometimes-trigger-wrong-resume-state/143220/2 "2019-01-19T04:14:17Z")
Ever find a solution to this? ---
**Author:** ![fsckit](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/fsckit/32/94458_2.png) [@fsckit](https://community.smartthings.com/u/fsckit)\ **Post date:** [April 5, 2019, 2:47pm UTC](https://community.smartthings.com/t/sonos-alerts-sometimes-trigger-wrong-resume-state/143220/3 "2019-04-05T14:47:03Z")
Sadly I have not. I still suspect it to be a race condition on the Sonos side with the resume play logic getting confused about whether something was playing. But I’ve found nothing in the activity logs that would point a finger at the cause. ---
**Author:** ![fsckit](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/fsckit/32/94458_2.png) [@fsckit](https://community.smartthings.com/u/fsckit)\ **Post date:** [July 15, 2019, 3:02pm UTC](https://community.smartthings.com/t/sonos-alerts-sometimes-trigger-wrong-resume-state/143220/4 "2019-07-15T15:02:21Z")
It would appear that a recent Sonos update has addressed this. Since either 10.2 or 10.3 I no longer experience this behavior.