The log showing it being triggered(this was the ONLY entry in the log for that rule--events and actions are being logged, so I SHOULD have seen that IF statement and the rest of the rule being executed):
But, then, I had another rule that acted similarly. I saw the event that should have kicked it off, but it didn't seem to run until it was directly run.
The rule above was a 5.x rule, This time, it's a 4.x rule.
It's like some of the event handlers aren't actually kicking the associated rule(s) off-impacting certain event types and both current & legacy rules.
Note: I did a test last night and the "Attic South Light" event DID kick it off. But the Ring Alarm one didn't work twice now & the other issue was related to an HSM status >change<.
Running rules directly works and it seems that the explicit triggers are working. So far, the two failures were on "changed" triggers.
All of your Event Subscriptions look correct. Events will be logged, even when a trigger does not fire. I just created a rule with multiple *changed* triggers, and it works as expected.
You need to provide more/better logging. Those logs have to definitively show an event that didn't trigger. You can isolate logs to show the device or variable in question, as well as the rule.
So far, I've had 3 situations that I know of where I see that "event triggered" message--and nothing else for the rule. It just doesn't run at all. One log entry, nothing more
Please tell me what log events show when a rule is NOT triggered?
Other than seeing NO log entries (which is exactly what I said and showed: NO log entries showing the rule running), how do I demonstrate conclusive proof that it didn't trigger?
As I said, I see the "event" and then NOTHING AT ALL happened. The rule did not run. None of the rule's actions happened. NOTHING beyond that "event" was in the log.
I'm at a loss as to what you're wanting to see--when there's NOTHING in the logs.
(as a side note: I've spent the last week moving rules from RM4 to RM5 and am continuing to do more still)
And those happen when an event hits any of the rule's Event Subscriptions. If you think it's not working, as I said above, you will have to show both the log for the device/variable issuing an event, and the rule either responding to it or not. You've done neither.
