As @Sir_Goodenough suggested. Please update your HA if you can and you will be good to go.
Blacky 
1 Like
Indeed I can confirm it solved the issue 
1 Like
is there any way to have it add them individually instead of one big message? I want to mark them off one by one as I replace them.
Currently it just reports them all. You can however edit the to-do item and remove the ones you have actioned.
Blacky
Hi @Blacky, amazing blueprint, thank you!
Iâve been getting an interesting alert each time the blueprint runs lately, where {{sensors}} is blank, i.e., " {{sensors_names}} all have a low battery level and it is time to replace them" is just returning âall have a low battery level and it is time to replace themâ, so some sensor seems to be getting picked up by the blueprint but isnât getting included in the {{sensors_names}} variable. Iâve tried replacing {{sensor_names}} with {{all_sensors}} to see what happens and I get âBattery is unavailable! all have a low battery level and it is time to replace themâ, so it seems to be something being detected as unavailable but the entity is not getting printed.
Looks like your using custom actions. If so then have you included the quotes at the start and end? As shown below⊠looks like you are but just checking
"{{sensors}} all have a low battery level and it is time to replace them"
Next when you use {{all_sensors}} your unavailable returned âbatteryâ sensor. You have a sensor called battery in your HA and if you search for it you will find it. Next after that you have no names for the low so it look like you donât have any. I think your custom action is not set up correctly. Have a look at point 6 or 7 in this FAQ, click here. This will be it and if you would like to test it adjust your Battery Low Warning Level to 100% then run the automation. You will see all your batteries and they will be above you original setting. You will have no batteries below your original setting so there is nothing to print.
If you are still having problems could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on â</>â and paste code in there.
Blacky
Hi @Blacky thanks for the note. The âBattery is unavailable!â was a red herring for me as I didnât think it actually was saying literally â[the battery with the name âBatteryâ] is unavailable!â. Low and behold one of my Sonos Move devices somehow created an entity only with the name âBatteryâ and not the name of the device (and I have since moved that Sonos device out of the house so itâs unavailable and therefore being reported correctly as being unavailable). User error there but that was a confusing message lol
What is interesting however is that the automation looks like it will trigger if a battery is unavailabel but the template names that donât include unavailable names (like {{sensors}}) or {{sensors names}}) will just be blank in that case. I guess the expectation is that one would use both {{sensors}} and {{unavailable_sensors}} in the same message to avoid confusion
Yeah I seen it a few times through this forum. I can be tricky but now you sorted that one out.
Maybe I didnât explain myself correctly.
It is working but you have no sensors to report a low battery % so it not printing them because there are none to print. This is because your custom action is not correct.
In the link to the FAQ I provided above if you look at point 6 or 7 shows you how to set it up.
This is what is happening.
- The automation is triggered, that works because you get the notification.
- Because there are no sensors below your % you have just given it one option and that is to print the notification message. The FAQ shows you what to do but your could just use the easy notification and it will do it for you.
If you provide me your YAML I can fix it then it will make sense.
Could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on â</>â and paste code in there.
Blacky
@Blacky No worries, my apologies I actually didnât catch that in your prior message correctly. It makes complete sense that you need the if/then to not call the custom action. Thanks for (re)-pointing that out for me and again thanks for your great work on the automations and your fast responses.
I was trying to figure out the most efficient way to do this and I was kind of stuck in helper Center groups and adding all my batteries. When someone recommended this blueprint, I was so pleased. This is awesome and my addiction for Hass is getting out of control my wife says LOL
Thanks for your kind words, you might want to check out my other blueprints. All links to them are at the first post.
Enjoy and have fun!
Blacky
Iâm so appreciative of your work and generosity, is there somewhere I can make a small donation to you?
Just imported and set-up. Havenât had a chance to run it yet; however, Spook is throwing an error.
Yes Spook will do this and we are aware of it.
What Spook is doing is looking for the TODO integration. The TODO integration is a Home Assistant integration supported and designed by HA.
In the blueprint when it sends a notification you can have an option to add your low batteries to a TODO task this way you can follow up replacing the batteries and crossing it off your TODO task.
To remove this warning from Spook all you need to do is install the integration or you can just ignore the warning.
To add the TODO integration go to Settings > Device & Services > click add integration and search for Local To-Do and follow the steps.
Blacky
Stay Charged, Stay Smart! Customize it your way and letâs automate your battery maintenance! 
Maintenance 
- From time to time, Home Assistant updates their YAML standards and coding practices. To align with their roadmap, weâve updated the code accordingly. We will continue to apply these updates across all our blueprints as they are revised.
If you like this blueprint? Consider hitting the 
button in the top post 
If you like my blueprints, and would like to show your support or just say thank you? Click Here 
Enjoy
Blacky 
saw this discussion in a other topic aswell. This was fixed with a template.
https://community.home-assistant.io/t/advanced-heating-control/469873/1836
Thanks for the info.
Blacky
The blueprint is wonderful and powerful; I am quite new to HA and this is the first blueprint that I can import. All is ok and the blueprint works (>Automation>RUN Automation>notification is ok). Then I created a Low Battery Button (as per the FAQ) and created a Button card including the entity Low Battery Button. When I click on it nothing happens⊠where am I wrong⊠