Not sure when it started - I suspect with the latest update 2.4.1.154 but noticed that couple of my (for a very long time) stopped rules are now executing. Given that one was used to stop ecobee thermostat it could not be broken for too long.
Paused rules seem to be ok.
There was a fix for this (stopped rules running on their own again) in 2.4.1.152, but I think it might only apply to new 2.4.1 upgrades (from 2.4.0 or earlier) to this build (or later).
Assuming you went for one of the earlier 2.4.1 releases first, that was probably what caused this for you, so you'll need some workaround like re-stopping them or restoring your old database backup.
Thanks for the recommendation! Still looks broken though. I first paused, but then after reading your recommendation decided to resume and (re)stop. Now the app is stopped in the list of the rule machine apps, but marked paused in the log.
Hm, I guess the log entry really reflects the state during which the log entries got created and there is no log entry for stop. So, I guess all is ok, just weird looking 
Yes, if you're looking at Past Logs, the name will not necessarily be the current name. You'd need to look at the Apps list or the "inside" of the Rule itself.
After updating to 2.4.1.155 Iāve noticed a hole stack of rules that are no longer being triggered.
Anyone else having this issue?
Please provide a specific example. Screenshot of the rule, show its Event Subscriptions and logs.
Will do, this morning my HVAC system didnāt trigger and my doors didnāt unlock, Iāll dig through the logs now.
As far as I know, there is s bug in 2.4.1.155 wrt overlaps between Required Expression and Triggers using Mode or HSM Status. That's the only known RM issue, with a fix coming out soon in 2.4.1.156.
There are no other reports of unresolved RM issues, except for whatever you come up with.
Ok that makes sense, that was the exact circumstances for the missed triggers. Normal triggers seem to be working.
EDIT: confirmed, temp triggers worked fine, it was the mode change that didn't trigger my rules.
Something like this report: Release 2.4.1.155 - C8 - RM 5.1 - problem with required expression
Does that look similar??
Yeah, that's the bug. Fix coming shortly.
Excellent, thanks Bruce.
Those rules will need Update or Done after the platform update.
Fix for this released: Release 2.4.1 Available - #7 by bcopeland
No, nothing to do with that.
Is there an easy way to see which rules monitor for mode changes? It turns out I have a lot of rules watching for mode changes, and I want to make sure I dont miss any.
I'm also experiencing instances of Rules failing to trigger on switches and shades after upgrade to 2.4.0.151 and later. Hub is C8-Pro.
Tried "update rule" and "done" up to and including 2.4.1.156 without success.
All actions execute from rule, but logs not registering triggers. Roll back to 2.4.0.148 solves the issue.
Other than the platform version update, no changes have been made to my system.
.156 solves it for me so far.
Download the Hubitat app
