[SOLVED] - [2.4.3.123] Rule with conditional trigger not triggering despite condition being True

I've not used conditional triggers much before so if I've done something completely stupid let me know...

My manual locks are monitored in Hubitat by microswitches (connected to contacts) but despite their status being clearly visible on multiple wall mounted dashboards I still managed to leave home with a door unlocked recently. To prevent that happening again I created a rule to notify us if the alarm completes its setting process while a door remains unlocked. Rather than have it trigger every time the alarm sets, then check the door status, I tried to use a conditional trigger. My issue is that the rule does not trigger despite the condition for the trigger (a door being unlocked) being true. The rule is below:

As you can see above the conditional trigger evaluates True so I expect it to trigger. The simple conditional for the Front Door being unlocked also evaluates True. If I go into the rule and click 'Done' I see two entries - 'Initialized' as I'd expect but 'Updated: Required expression now false' which is unexpected, as it is True:

I can just remove the conditional trigger and let it trigger and check the conditions every time the alarm turns on but was interested if I've done something wrong...

Was there a (no-kidding) Required Expression in this rule at some point? If so, have all hints of it been completely removed?

1 Like

I'd just tried that before your post and it seems to have resolved it. Kudos for blindly knowing what the issue was!

I went back into the rule, turned on 'required expression', clicked 'delete expression' then clicked 'done' again. Now I just get 'initialised' in the log. I left the front door open and set the system and it worked as expected.

I think when I started setting it up I got a bit tangled up in the UI. I must have gone into required expression and exited. I did delete it but something must've remained.

1 Like

Awesome. I don't recall details, but I know I've run into similar such weirdness before when messing with or removing Reqd Expressions. I'm sure it was somehow my fault, but diagnosing it wasn't exactly straightforward. But all's well that ends well!

2 Likes