I have multiple devices that use batteries.
Currently the only way to get a battery status (that I know of) is to look at the device page, and look in the battery column.
It would be ideal to have an automation that notifies when a device’s battery is below 10% (for example) so I’m not surprised when that device / relevant automations stop working.
Is such an ability possible? It seems like a simple, yet useful option.
Thanks.
There are several community apps that you can use. This one is available on the Hubitat Package manager and works pretty well. You can set alert levels and have it check daily.
To be fair though, the sellf reporting for many devices is hit or miss. Depends on the type of battery, the driver for the device, and several other things that makes the information "nice to know" but not reliable enough for anything if it is critical.
The other thing you can do also, is to start logging the battery change dates. I would search the forum for a few apps that can help, but you can also enter it in the device note block on the Device Info tab. For some devices, this may be the best way to predict when you need new batteries (like this one that is battery hungry)
This. 
Thank you. I installed that app, and it displayed a message saying the app is no longer being maintained. However, Battery Monitor looks like a good option. Thanks!
That looks like just what I need. I’ll give it a try. Thank you.
You should like this too:
Thank you, that looks interesting. I’ll take a look…
Perfect. That’s exactly what I was looking for! Appreciate it.
Quick follow up. When I use “Battery level on %device% is low”, I get “Battery level on null is low”. (No quotes).
Am I using that variable correctly?
Post your rule. Sounds like you haven’t selected any devices.
Isn’t it just because no device has yet triggered the rule?
Possibly. I ran the rule manually with a known low battery device. I’ll see what happens when the rule engine runs it.
I think %device% gets populated by the device that triggered it. As such, I do not think running manually populates the device. So, it will be null until an actual device triggers it.
One drawback to using RM - If multiple devices trigger it at the same time - you only get notifiation of one of those devices in the message. I use webcore when I need a list of things meeting conditions (Like this one for doors left open)
Thanks. That makes sense.
