I have a simple trigger rule that evaluates the attribute from a Dome On/Off switch and sends notification. The attribute is "voltage" as the switch has power monitoring capabilities. Displaying the voltage attribute on the dashboard works great and the value seems correct. When the device refreshes, the notification consistently triggers even though the power has not dropped below 100.0. The logging shows that it triggered but I cannot figure out why. I have included screen shots below.
Hmmm, this doesn't look right, does it?
I'll poke around a bit and see if I can reproduce this somehow. Able to reproduce the bug. Tracking it down.
Update: The bug has been found. No comparisons of a custom attribute value were being done for Trigger Events. That fix will be in the next release. Comparisons are done correctly for Conditional Actions, so you have a work-around that way.
Thanks so much for your help. I was convinced that it was something that I was doing wrong... I'm new to the HE platform. Your rule engine is very impressive !! I have really been enjoying its capabilities.