Rule Machine trigging when I don't think it should

I have a custom rule called "Alarm Away - Checks". The only purpose of this is, when I set HSM to "Armed Away", it checks all door/window sensors and if any are open, it broadcasts over my sonos & sends my phone a message.
Thing is - it ALWAYS triggers. I have checked every contact sensor on this list, and they all say closed. I have checked events & logs for every contact sensor on this list, and none have any logs of triggering this app. Yet sitting at my desk right now, if I enable "Alarm Away", I get a message saying "Fleethouse is still open, don't leave without closing". Yet each of these contacts is closed, and battery levels on the battery-powered sensors are fine. What is going on here?

I agree with @Tree.Log as the rule is working as defined. That unused condition is what needs to added in order for the rule to work. You could actually use it in one of three places: (1) Required Expressions, (2) Conditional Triggers, or as a (3) simple conditional action. The implications are slightly different depending on where you place the condition, but the action would still be the same (only notifying when the condition is true).

3 Likes

Well, there ya have it. Thanks for fixing my stupidity so quickly, both of you! Working well now!

3 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.