Yup happy with it. Functioning well. Added a button on dash to input_button.low_battery_button which does spot checks for me. Much appreciated.
1 Like
Another great blueprint, could we get a option for Notification channels on Android please? thanks
Thanks for your suggestion, I will add it to the list. My notifications are quite basic but you can add this in your custom actions if you like.
Blacky 
1 Like
Just set this up - works flawless!
One tricky thing though (and mentioning it for others): seems that when selecting the excluded group or custom group, âlabelsâ cannot be used either, only the entities themselves directly. The documentation is mentioning only not to use âareasâ or âdevicesâ for the selection.
Could be a nice addition to allow (entity) selection via labels - it is much easier to select and tag a couple entities with a label, instead of editing the automation and adding each one individually. Also, this label can be reused in other places, therefore no need to keep the selection in sync in multiple places.
Thanks for your kind words.
Thanks for reaching out and for the heads up 
. I will need to go through my blueprints and update the descriptions but it does say that " NOTE - You can only use entities. Areas and devices are not supported". âLabelsâ was added to blueprints HA 2024.4. I normally wait about 3+ months so everyone has time to update before I break a BP for those who havenât updated yet. Agree I will need to look into âLabelsâ further and see how they can be used.
I will put this on my list to do 
Blacky
Stay Charged, Stay Smart! Letâs automate and take charge of your battery maintenance! 
Maintenance 
-
Update the description in âExcluded Battery Sensorsâ and âBattery Sensors - Custom Groupâ to include the new option to select âlabelsâ. The updated description should read:
NOTE: Only entities can be used. Areas, devices, and labels are not supported.
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 
@Blacky Thanks for this amazing blueprint! Is there a way to target a notify group instead of a hard-coded list of devices?
Hi Jules, and welcome to the community.
I decided not to go with groups because I just wanted to go into the automation and see who is being notified. I find this easier to manage.
For me to understand more⊠why would you like to use groups and not just quickly set up your automatons selecting devices?
Blacky
Blacky
@Blacky Thank you for your response 
I am trying to organize notifications by ârolesâ, so that anyone interested in the household can âjoinâ a group. For instance, low batteries is the âmaintenanceâ group ^^ I find it neat that way, but can live without!
1 Like
Hi! Firstly - wow this blueprint is awesome!
Iâm having a minor issue where itâs reporting some phantom devices (presumably something I used once upon a time and didnât delete when I pulled it out of the system) but Iâm not gettting âBattery is unavailable!â messages for two devices without a device name (to go look into)âŠ
Iâve attached a screenshow - @Blacky or anyone got any ideas where I can find out what these devices are? Thank you!!
And thank you again @Blacky for sharing such an awesome template!
Thanks and I still have more to come.
Yep, go into settings > device & services > Entities tab at top > in the search type âBatteryâ and you should see all your batteries pop up. The BP reports the friendly name but look for the ones with the red warning. You should see 3 of them. Then you will have to act on what you would like to do with them, delete, replace battery, reconnect, etc.
Blacky
Stay Charged, Stay Smart! Letâs automate and take charge of your battery maintenance!
New Feature 
-
Collapsible Sections - Added collapsible sections to the blueprint. This enhancement improves the blueprint user interface by making it cleaner and more organized, allowing sections to be collapsed.
This feature was introduced in Home Assistant 2024.6, so you must have this version or later for the blueprint to work.
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
1 Like
I donât quite get whatâs the point of the Cancel Action Button. I would expect it to remove the notification. On my Android device I can press the button, but nothing happens. I would also like to not have the Cancel Button as swiping the notification already removes it. Maybe make it optional?
Also may I suggest to add an option to add the current time as due date to the to do entry?
The automation is waiting to see what you would like to do (listening). If you push the cancel button then it knows what you would like.
If you choose the âAdd To-Do List Action Buttons + Confirmation Messageâ Then when you push the cancel button you will receive a confirmation message.
Normally when you choose this option 9 times out of 10 you will push the âAdd To To-Do List!â. Again when selecting âAdd To-Do List Action Buttons + Confirmation Messageâ and you push the âAdd To To-Do List!â button you will receive a confirmation message. If you click on the confirmation message it will take you directly to your chosen To-Do list. You then can click on the task and add your due date.
Blacky
That didnât work for me. I pressed Cancel several times and nothing happened. In the end I just swiped the notification away.
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
alias: Batterielevel
description: ĂberprĂŒft regelmĂ€Ăig den Batterielevel und erzeugt Tasks zum wechseln
use_blueprint:
path: Blackshome/low-battery-notifications-and-actions.yaml
input:
to_do_list: todo.allgemein
include_time: time_enabled
time: "16:00:00"
weekday_options:
- mon
- tue
- wed
- thu
- fri
- sat
- sun
include_easy_notify: enable_easy_notify
notify_device:
- 676fd4d19422dee4caea8c99b8c4c592
notify_title: Batterielevel niedrig
notify_okay_message: Alle Batterien in Ordnung!
notify_action_buttons: enable_to_do_list_button
to_do_task_title: đ Batterie ersetzen
action_button_to_do: Task erstellen
action_button_cancel: Abbruch
action_button_confirmation_title: Batterieaufgabe erzeugt
action_button_confirmation_message: Batterien mit niedrigem Stand wurden als Task erstellt.
cancel_action_button_confirmation_message: Alles in Ordnung!
include_persistent_notification: disabled_persistent_notification
exclude_sensors:
entity_id:
- sensor.pixelchen_battery_level
- sensor.sixpack_battery_level
include_custom_actions: disabled_custom_actions
notify_message: sensors
Thanks for your help!
Hey there, very nice work!
Currently I have the problem â that it does not find any untis with battery at all.
And that where I have 15+ devices which I find under âSettingsâ > devices & services > entities > search type Battery.
But mostly all are incoming via MQTT / Zigbee2Mqtt.
Did I miss something? 
Hi Nick, and welcome to the community.
Could you go into developer tools > states and search for one of your batteries entities and see if in the attributes that they have a âdevice_class: batteryâ
Could you also 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