Hi @Brian_Taylor and @Nezmo !
I’ve deployed an update to fix the State Stays trigger issue you reported. To complete the fix for your affected rules, you’ll need to trigger one event from each impacted device. This one-time step will initialize the new state-change tracking system.
The update introduces internal state-change tracking while maintaining compatibility with the existing system. For most users, this transition is automatic. However, in your specific case (where the reported state timestamp differs from the state-change timestamp), this one-time initialization is necessary.
Once initialized, the system will reliably track all state changes going forward. Please let me know if you have any questions or need further assistance.