Fixed. Can now compare variables, Thanks
2 Likes
Another interesting one:
I created a rule with several variables to act as presets with which to compare outside temperatures (see screenshots below) and started building conditions. I got to a point where I could no longer select variables when building a condition. I wanted, for example, to compare the humidity with the outsideHumidity preset. When I get to the point where I check the "relative to a variable" box and try to choose a variable, nothing comes up. I am using the Accessibility/screen reader mode, so I thought I'd turn it off and try in case it is a bug specific to that, but unfortunately no variables showed up.
Thanks,
Zuhair.
I will investigate...
2 Likes
Another possible bug in RM5, I setup a couple of new rules using hub variables that had the same name as the old global variables.
Anyway, the new RM5 rules worked great so I deleted the RM4 rules and the old global variables…. And then my 2 new RM5 rules both stopped working.
When I went into them, the IF statements referencing the new hub variables were broken with blank spaces instead of variables comparisons.
This problem arose do to the released version being too restrictive about the type of variable that could be used in the comparison. For instance, humidity is an integer attribute, so Rule 5.0 was limiting the choices to Number variables. But you have Decimal variables, so those were not offered as choices. The next release will relax this so that either Number or Decimal variables can be used for comparisons.
4 Likes
I think as a consequence of the update, everyone might need to go back and check any rules that used a real comparison. I just noticed this morning that one of my cost displays looked funny so I went back and looked at the rule and in two places where a compared a decimal variable to a constant the line had been deleted. In every rule, I had five, that did the same thing and both lines were deleted in each rule. I have others that do comparisons of two decimal variables that seem to be OK. I still only have a few RM5.0 rules, and my RM4.0 rules seem uneffected.
The first was IF FractPart <0, and the second was If FractPart < 10
Hello, I moved the following rule from RM 4.0 to RM 5.0 and it doesn't function as it did previously:
What happens is the notification and TTS never trigger now when the sensor reports that it's wet.
When the Sensor is Wet and I click "Run Actions", then the TTS and Push Notifications trigger, but even then it reports the device name as "null", and the status of the sensor as "0".
I noticed that my rules with repeating actions seem to be the only ones with issues in RM 5.0.
Another one that doesn't work quite properly from RM 4.0 to 5.0:
In RM 4.0, when the windows open, it send a notification to our phones, but then stops sending the notifications when the windows are both closed.
In RM 5.0, the trigger conditions start the notifications, but when the windows are closed, it never stops the repeating action until I click "Update Rule".
I noticed that my rules with repeating actions seem to be the only ones with issues in RM 5.0.
This is the expected behavior when you “Run Actions” because, in that instance, the rule is not triggered by a device event.
1 Like
Turn on logging for Events, Triggers and Actions. We need to see the logs for the sequence of events that represents a failure.
@bravenel
Turned on logging and noticed that when my RM 4.0 rule is active,
-the logs show the Water Sensor change from dry to wet
-The RM 4.0 Rule Shows up and reports logging on the app
-My Speakers show up because they're in the rule
When I pause the RM 4.0 rule and reinstate the rule in RM 5.0, that has the exact format:
-the logs only show the Water Sensor change from dry to wet...that's all that shows.
This may be completely unrelated, but another thing I noticed is that in RM 4.0, when I created/selected the trigger events, the same trigger events were available for selection when I created the action. In RM 5.0, I notice that after I create/select the trigger events and then go to create the actions to run, I have to manually select/create the conditions under which the rule should run. Is that change by design?
Yes, this is a change in Rule 5.0.
Please post a screenshot of the Event Subscriptions section of the Rule 5.0 App Status page (gear icon).
Logging for Events, Triggers and Actions is on for the RM 5.0 rule, but nothing shows in the Event tab. Is there a different setting that I missed turning on?
Logs page, not Events for the app.
Do you have the logging turned on the for rule? Events, Triggers, Actions?
Also, please post a screenshot of the Event Subscriptions portion of the rule's App Status page (gear icon).
Logging is turned on:
Event Subscriptions:
Thank you for the assist! Learning a lot about the logging.
OK, sorry for the hassle. There was a bug found earlier today that is messing up the water sensor subscription. There will be a hot fix release coming out for it. If you can roll back to 2.2.8.152, it does not have the bug.
Hot fix release 2.2.8.156 is out, and fixes this problem.
2 Likes
@bravenel updated to the latest hotfix, recreated both rules, and they are working properly now!
Thanks for the assist!
-Travis
