I have 3 First Alert Z-Wave Smoke and CO detectors, configured as "Generic Z-Wave Plus Smoke/CO Detector". I have Rm rules that monitor the battery levels, to alert me if they go low. I had the triggers as battery level changed, but that triggered on the of the rules every time the device sent a battery level event, even though the level stayed at 79%. The battery updates are received about every 63 mins. I changed it to Decreases and it stopped sending the redundant messages. However, I would prefer to go back to Changed, so it can update some info on battery replacement. Of course I could add that as a second rule, but I think there might be an issue here with how the Changed triggering works.
It would be helpful to post screenshots of the rule.
Does the device report battery level as a percentage, or as a voltage (to several decimal places) that the driver converts to percent? Just a wild guess, although this explanation is inconsistent with changing it to decreases fixing it.
I was wondering if it was a device issue (battery roundoff) as you mentioned, or something else. I've used the Changed trigger elsewhere without issue. I figured though that this being an integer % (at least what I can see), it would be ok.
Here is the rule, with the Decreased trigger...
Along with the last few battery events for the device...
I am trying to figure out what your intent is with this rule. Why do you need a report when the battery is under 80%? What is the battery level where you need to change it?
What does the "Set PrvBatt-SDHall to SmokeCO2 Hall battery((79))" supposed to do?
Have you considered using Notifications for this rather than creating a rule in Rule Machine? I have battery status set up to be reported using notifications. I have it report once a day.
Thought I could go lower on these smoke detectors (my lock can go down to 10%), but one started chirping low battery at 77%. There is about 15-20 days between each % change, so it just gives me a heads up when one starts to get low. Preferred RM to have more control over the messaging. Example the lock drops in 10% increments, and I send myself an alert when it reach 20% and again at 10%. Found the batteries behave significantly different in different devices.
That was old code I hadn't deleted, yet. Used it to limit msgs to certain incremental changes, until I figured out exactly the the device battery behaved.
Oh ... so you don't turn into this guy ...
Yeah.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
