Hey @Brian_Taylor – thanks for the follow-up. I just received a report from @Nezmo who seems to be experiencing something similar.
I’m trying to figure out why this was only impacting you (or perhaps your devices / drivers) back in September and why it just starting impacting Nezmo just this weekend. It’s not clear if it’s a change that is unique to these particular drivers, a platform level SmartThings change, or why those timestamps for the state are updating now.
Normally when a device reports its state, if it reports the same state again, SmartThings keeps the existing timestamp recorded for the state (even though it might internally record an ‘event’).
It seems like in both of your cases, the state is showing a newer timestamp at a later point when the State Stays part of the rule checks to verify that the current state matches the originally snapshotted state from when the event first came in.
What make / model switches (Brian), motion sensors (Nezmo), or other impacted State Stays devices are each of you using? And are you using an official SmartThings driver or a community driver?