Variable changed issue on 2.3.6.135

[darren]

I have a number of rule machine rules attached to variable changes.

I've noticed the trigger variable 'changed' has stopped working when the value of the variable is changed to 0.

I've worked around this by adding a second trigger of if variable = 0 which has got me around the problem but I'm sharing my findings.

[bravenel]

@darren

I've noticed the trigger variable 'changed' has stopped working when the value of the variable is changed to 0.

I will look into this.

[bravenel]

Not seeing this behavior.

You might try hitting Update in one of those rules, and seeing if it works after that.

[steve.maddigan]

I noticed this as well. I upgraded last night and a couple inovelli indicator rules were not getting reset after being cleared. Today I had another rule get stuck. I realized that the common denominator was hub meshed variables and when they return to their default state. I will not have time to debug further until the weekend so reverted this aft and I am back to all operational.

[darren]

@bravenel I have included a grab of the activity from my Hub. I reverted the rule to it's previous state (prior to the update) which eliminates the concern I read somewhere that the rule needed update clicking to work.

Hopefully this is clear.

[steve.maddigan]

I switched back to

var.Bright.day is a HubMesh variable from my C5 to my C7

I can confirm that when var.Bright.day = true, my rule triggers, when it = false, nothing.

This rule is on my C7

[bravenel]

I'm still not seeing this. But, I will look into it further. Changes were made to how *changed* works in this release, and it's supposed to update the rule automatically to the new method. So it could be there is a problem with that updating mechanism. Again, hitting Update in the rule should fix it, although at least in theory that shouldn't be necessary. What I would like to know is if doing that fixes it for you or not. Rolling back works too, but doesn't provide any useful information.

[bravenel]

I think I've found the problem with this, and will get a fix into the next release. It's just not handling *changed* correctly for variables.

[steve.maddigan]

Thank you sir. I was just about to update again and really dive in to debug, but now I will wait for the next release.
I appreciate your update.

[darren]

Great news, thanks. Hopefully, if anyone else trips over this, the notes will help them work around.

For integer variables, add a condition of variable = 0 to the changed trigger in an or relationship.