This is not how I would do it as you break some of the blueprint. I will add it to the list to do.
Blacky 
1 Like
Hello there,
First of all, thanks a lot for your blueprint, it's really useful !
I have a "problem" : I have some zigbee temperature sensors exposing battery state as a sensor entity, containing "battery_state" in the entity name and the value is a text [Low, Medium, High, Unavailable]. Their state seems to not being caught by your blueprint, is it normal ? How to "fix" it please ? Don't hesitate to ask me more info if needed 
The blueprint will send a notification when the battery state is "Low" depending on you selected option. Message option 1 or 2 will do this. Make sure your entity that reports "Low" has a device class "battery". You can see this in developer tools.
Blacky
@Blacky thanks a lot for your help, I just added the device class to my devices and now it works great, it's perfect ! Have a great day 
This looks awesome and means it's time for me to understand blueprints and his to use this. 
I'm wondering what is the best way to track battery types as it's obviously a big ask for them to be detected automatically for such a large number of possible sensors. Rather than adding it to the name one by one, as in the FAQ example, is there a way to mark all sensors matching a particular name/id using search and replace for example (in some config file)?
I'm very new and so may not be using the right terminology here so by all means educate me.
I ask because I expect to have multiple sensors of the same underlying type and it works be good to be able to set the battery type (or where needed the class etc, add on the n previous query) all at once.
Alternatively I could maintain a lookup list but it would be nice to have this in HA.
you want this... Battery Sentinel: A Home Assistant App (Add-on) for Managing All Your Battery Devices
1 Like
The best way is to use labels. Let's say the batteries you would like to track are XYZ. In the entity list, search for them and apply a label to each battery you would like to monitor. Then, in Battery Sensors - Custom Group, select that label. In Easy Notify, under Sensor Selection, simply choose the custom group.
You will then be notified about any batteries that have that label applied. When you add a new battery, you will need to apply the same label to it, but this gives you full control and makes it very clear which batteries are being tracked.
Blacky
1 Like
Hi @Blacky, this is a great blueprint, many thanks for it!
One suggestion, if I could have, is to have on option to set Android notification icon and color separately for warning and okay message.
Thanks,
Peter
If a device becomes unavailable or reports an unknown state, I receive three separate notifications for the same device, as shown below:
Low Battery
Loft Water Leak Sensor Battery is unavailable!
Loft Water Leak Sensor Battery+ is unknown!
Loft Water Leak Sensor Battery low is unknown!
Garden Contact Sensor Zigbee (Aqara) Battery is unavailable!
Garden Contact Sensor Zigbee (Aqara) Battery+ is unknown!
Garden Contact Sensor Zigbee (Aqara) Battery low is unknown!
Ideally, I would like to receive only a single notification when a device is unavailable, rather than multiple battery-related alerts.
Btw, how do i update to the latest blueprint version?
Download it again. Using automation blueprints - Home Assistant
1 Like
Looks like you could be using battery notes. If so when you install this integration it creates the extra entities. You will need to add some code your your configuration.yaml file to hide the entities it creates so you only have one battery entity for that device. You have to look through the battery notes documentation for the how to.
This is not the blueprint you will have 3 entities of the same battery and this is why it showing you all 3 but if you look close you will see
- Battery
- Battery+
- Battery Low
Go into the device and you will see all 3 entities. If they are already hidden then all you need to do is go into Battery Settings and select Exclude Hidden Battery Sensors. This is why this option is there.
Blacky
1 Like
I think @Sir_Goodenough already answered this. But if your still confused just click the Import blueprint button again (like the first time you installed it) and it will be updated. All your existing automations will be okay.
Blacky
I use battery notes as well. Not easy to hide all the sensors it creates. It would be nice if this could be done on the blueprint, I. E. Battery+•.
Thx, and crystal clear!
I don't think you want to hide the batteries created by Battery Notes; instead, you should hide your existing battery entities. I believe Battery Notes needs to use the battery+ entities it creates, otherwise there isn't much point in using the app.
I had a quick look. You used to configure this in the configuration file, but it looks like the developer has now added an easier option to hide batteries from the main Battery Notes page using the settings (cog) icon. I don't use Battery Notes myself, so I can't confirm the exact steps, but the documentation is here: Configuration - Battery Notes for Home Assistant. Look for the Hide battery option and enable it. You may need to restart or reboot Home Assistant for the changes to take effect. As I don't use Battery Notes myself, you'll need to do a bit of troubleshooting to determine what works in your setup.
Then, in the blueprint under Battery Settings , enable Exclude Hidden Battery Sensors . This will automatically exclude any hidden battery entities from notifications.
Some devices expose both a Battery % entity and a Battery Low entity. The blueprint will detect both, so if you only want a single entity in your notification for each device, I recommend hiding the Battery Low entity.
Keep in mind that some devices only provide a Battery Low entity and do not have a Battery % entity. If you hide all Battery Low entities, those devices will be excluded completely. After hiding the entities you don't want, make sure Exclude Hidden Battery Sensors is enabled under Battery Settings .
This is why @Kayut sees three battery entities in his notifications:
- Battery % – Created by the device.
- Battery+ % – Created by Battery Notes.
- Battery Low – Created by the device.
Blacky
1 Like
I didn't notice the settings in battery notes. Thanks for pointing this out. I thought I had to go to each entity?
1 Like
@Blacky Thank you for this very useful blueprint. I wanted a way to call an immediate battery re-check straight from the low-battery notification instead of waiting for the next scheduled run, so I added it to a fork and wanted to share it here in case it’s useful to others / worth folding into the main blueprint: low-battery-notifications-and-actions.yaml · GitHub