Unexpected behaviour of required expression versus trigger

What platform version is your hub on?

Wait, false mistake. Your Required Expression is false, so the rule should only have the stHandler Event Subscription until the RE becomes true. I just tested that and it works as expected, adding the Trigger Event Subscription when the RE becomes true.

So, back to this report. You said "the problem didn't go away". What does that mean? Please test this rule again. I think it's fixed, and so far this is the only 'evidence' of that not being the case.

Done.

2.4.1.118

Wow, impressive - thanks!

If you rule doesn't work as expected, I will need to see logs supporting that.

Okay, makes sense.

All right, I tried that myself, and I can see the two handlers when I make Environment_need_lights false. So far, so good.

The morning after I updated to the beta version (that is, yesterday Monday Feb 10, as I updated the Hubitat to the beta version on Sunday Feb 9), the kitchen lights turned on when Environment_need_lights became false, as had been (incorrectly) happening all along -- hence, at least as of yesterday morning, the problem still existed. At that point (again, Monday morning) is when I tried re-updating the rule, and reported that the event handlers didn't change (which we now realize was a red herring).

Actually, I believe that this morning, the lights did not come on (i.e., correct behaviour, or at least, lack of incorrect behaviour). So it very possibly is fixed -- if so, presumably updating the rule (after switching to the beta version) would be what finally did it. Let me see if I can run a more detailed test, and I'll check the logs (I'll make that first that the rule is has logging on)...

1 Like

Yeah, this Update in the rule was needed to fix the Event Subscriptions (which clearly had been wrong before). I probably failed to mention that need in this case. I had surgery last week, and my brain is slow to wake up fully, especially about subtlety in RM. When I saw your post that it was still broken, I was fairly dismayed, because I was certain that bug had been fixed -- but then in fog, say what? Sorry. but this should be good now.

2 Likes

I do believe it is fixed! I futzed with the variables manually, and:

That's excellent news: the beta indeed contains the needed fix! But it looks as though you were right a few days ago when you suggested that re-installing the rule would be necessary.

Thanks for all your patience following up on this! I'm really glad that I can now carry on with my rule-creation plan that uses variables as required conditions.

(I just read your subsequent note - I wish you a speedy full recovery both from the surgery and from the anaesthetic!)

4 Likes