[2.4.1.156] Events triggering <> backwards [C8]

[user2292]

I have 2 rules triggered by a custom attribute (sun azimuth) and they are triggering opposite the designated comparison. I altered one to check and the result is repeatable.

[danabw]

Variable trigger issue may be the root issue?

[2.4.1.155 - 2.4.1.156] RM 5.1 variable trigger issues

@bravenel After updating to this release I'm finding that setting a varialbe trigger with stay is no longer working. Example showing that there was no "stay" when triggered. [image] [image] Also of note, this example isn't working either, something seems to be wonky with variable triggers. In this example test variable set as "stop" shouldn't trigger, but it does [image] [image] Rolling back to 2.4.1.155 didn't fix above issues , however 2.4.1.154 restores expected results

[user2292]

This has been working flawlessly for 2 years until the last update though.

[danabw]

I'm saying both of the rules use variable triggers, so maybe they share a root cause related to using variable triggers that surfaced in .155/.156? What release are you on?

[user2292]

2.4.1.156

[user2292]

Update: I changed the trigger directly to the custom attribute and it works correctly that way.

[danabw]

That does seem to point a finger...@bravenel will know best, of course.

[bravenel]

I will look into this.

[bravenel]

This bug found and fixed. Next release....

[bravenel]

Fix for this released 2.4.1.157