Triggered Rule not working as expected, have I misunderstood it?

I am starting to set up my Heating control on HE. I'm trying to just use RM rather than learn Groovy and emulate the complicated Lua system I had on my Vera.

I've got a basic system working but have come across a simple issue that must be me misunderstanding something. Below is my RM2.5 Rule for daytime heating. I have several similar rules for different times of the day, which work fine, but on this one, the false conditions never run. Regardless of the state of the "Heating Daytime Active" virtual switch, the rule always runs the True commands. Am I misunderstanding how this should work?

Why does heating active disable the rule? Maybe I'm just misunderstanding your labelling, but if I'm not, then when the heating becomes active, the rule is disabled, so it can no longer evaluate when the condition becomes false.

To put a point on it: is the rule disabled when this runs with the rule false as you show? If so, then @SmartHomePrimer just showed the flaw in your logic.

The "disable when off" option is selected, so it runs when Heating Active is on and is disabled when it's off. That part of it works fine, it's the Heating Daytime Active switch which seems to be ignored.

Can you try a different time, and have the Logs running. It should log something at the time...

The rule is not disabled, it definitely runs because I've tested it with different values for the set temperature and that changes accordingly. The problem is it always runs the "true" portion even when the Heating Daytime Active switch is Off.

OK, go back into the rule, into the Define Rule section, and make sure it is correct. That will probably mean selecting the single condition.

I've just tried that but with the same result so I've selected another random switch that is also currently off (kitchen light) and it still runs the true portion of the logic.

That's weird. Can you show a screenshot of the app detail page. May take more than one to get the whole thing.

Also, could you remove the restriction, and see if it does the same thing or not?

I am able to reproduce this failing. Will dig into it and find out why. Do your other triggered rules work for false? Are they different in some significant way?

I think this is my first RM2.5 rule with a trigger and a condition. The other heating rules are straightforward time triggers.

Found the bug. Definitely introduced in 2.5. This will be fixed in our upcoming release (soon).

1 Like

Thanks for looking into it so quickly for me.

New release out with this fixed.

1 Like

You will need to open the rule and hit Done, after you've done the update. That will refresh its scheduled events.

Updated, reloaded the rule and all good! Thanks again.