đŸȘ« Low Battery Notifications & Actions

@iona

So if your using battery notes then you will select Exclude Hidden Battery Sensors. That was one of the reasons it was added. Then in your configuration.yaml add

battery_notes:
  hide_battery: true

Then everything will work automatically.

Blacky :grinning:

@zBernie

First you create a button, click here

Once you have the button add it into the blueprint input Button Helper and enable the option Use The Button Helper Trigger.

Next you add that button to your chosen dashboard.

When you press it, it will run the automation.

Blacky :grinning:

I tried using the Easy Notify which resulted in an “unknown” dashboard notification. Any help would be appreciated. I really like the app!

image

@zBernie

See this FAQ click here

Take note of step 5.

Blacky :grinning:

I don’t seem to have a “Create” option or “Advanced” settings as described in the FAQ. Here’s a screenshot of what I’m seeing.

-Thanks

@zBernie

All you settings look good.

Your text helper is Low Battery Notifications. To find all your helpers you have created go to Settings > Devices & Services > Helpers (tab at the top). There you will see your Low Battery Notifications text helper. Click on it and then click the cog wheel. Now you see the options.

The thing to note is once you created this text helper it will be empty and there will be no text formatted in the correct way. In order to create some text you have to run the automation just once so it will populate the text helper. Then when you add it into the dashboard everything will work.

Blacky :grinning:

Thanks again!

1 Like

I don’t have the battery sensors hidden by choice for battery_notes configuration. I use both device and battery notes sensors together as sometimes there are inaccuracies/issues between the two. I guess I’d have to live with it or make changes, thanks nonetheless.

I just tried to implement this blueprint last night (Home Assistant OS, Core 2025.10.3, Supervisor 2025.10.0) and got the same error (UndefinedError: list object has no element 1) from the Markdown card.

Here’s my yaml following your response to thomas15.

alias: Implemented Low Battery Notifications & Actions
description: “”
use_blueprint:
path: Blackshome/low-battery-notifications-and-actions.yaml
input:
include_button: enable_button_trigger
button_entity: input_button.low_battery_button
dashboard_notification_text_helper: input_text.lowbatteryinputtext

@Previous

See FAQ on how to use this and take note to step 5.

click here

You also need to enable Use The Easy Notify - Dashboard Notification Option

Blacky :grinning:

Thank you for your kind assistance. I was able to resolve my issue by carefully looking again, I had manually created the input_text but didn’t set the size to 255 in advanced settings. I wasn’t yet ready to get notifications, but now that I can actually see data that’s the next step. Thank you!

1 Like

Thank you very much for this nice blueprint.

I have been searching this thread for a way to add the area my battery is in into the message that is sent to my device. But I have been unable to find much information about whether this is possible and if so how.

I can see that others have requested this feature, but I cannot find any information about whether this is possible or not.

Does anyone have any insight on this?

The reason why I ask is because I generally leave all my sensors with their default names and then just attach them to an area. So for instance The message I currently receive looks like this:

Xiaomi LYWSD03MMC-z Battery @ 17.0%
Xiaomi LYWSD03MMC-z Battery @ 11.5%
Xiaomi LYWSD03MMC-z Battery is unavailable!
Xiaomi LYWSD03MMC-z Battery is unavailable!

Which unfortunately does not tell me which area these sensors are actually in.

@tueboesen

This is currently under development and I am just trying to work out the best way it should be displayed in the blueprint and in the message. Here is a sneak peak.

But you should go through all your batteries and update the friendly name as it will look so much better and help identify them.

Blacky :grinning:

2 Likes

Hello @Blacky,

First thanks for you amazing Blueprints!
Mayby you can help to solve a small issue.
I got a strange “Batterie is Unavailable! " Without any Sensor Name on the dashboard. In addition I get no notification on my cellphone which tell me, no sensor is detected as Low Batt. If i am activating the OK confirmation, I get the notification with “YES! All batteries are okay :)””


and looks the “all_sensors” is also not Empty

Do you have an idea where is the bug on my system?

thanks a lot

@DjOlf

So when it says Batterie is Unavailable! the name of the battery is Batterie and the blueprint adds is Unavailable!. So you need to search for Batterie in settings > device & services > entities tab at the top and then search Batterie. You can also use the filter to see the Unavailable.

For the 2 displaying different I would need to see your YAML of you settings. If you like 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.

Also I have a new release ready and waiting. I am just holding for Home Assistant to release version 2025.11.2 as I would like to update my HA and test it before I release it. In the new release you will be able to include your entity ID so you can find it easy.

Blacky :grinning:

Thanks for your really fast answer.
First point:


I found probably which device is causing the issue but is device Name is not “Batterie” but “WandTablet”. Why it is showing this name?
I tried to deactivate the device but it is still staying with this red status “not provided”. Does it make sens to exclude those sensors from your template check ?

For the second point:

alias: "Low Battery Notifications & Actions_TEST VERSION "
description: ""
use_blueprint:
  path: Blackshome/low-battery-notifications-and-actions.yaml
  input:
    time: "20:00:00"
    include_easy_notify: enable_easy_notify
    notify_device:
      - 638effebbe3004c81aad35ad7aceabab
    notify_message: sensors
    notify_data:
      - high_priority
    battery_level: 10
    dashboard_notification_text_helper: input_text.battery_text_helper
    include_dashboard_notification: enable_dashboard_okay_notification
    include_time: time_enabled
    exclude_hidden_entities: hidden_enabled
    custom_actions:
      - if:
          - condition: template
            value_template: "{{ all_sensors == '' }}"
        then:
          - action: input_select.select_option
            metadata: {}
            data:
              option: High
            target:
              entity_id: input_select.general_battery_state
        else:
          - action: input_select.select_option
            metadata: {}
            data:
              option: Low
            target:
              entity_id: input_select.general_battery_state
    include_custom_actions: enable_custom_actions

Thanks for your help

@DjOlf

Yes it is as shown in your screen shot Batterie.

That is the name of your device and the Batterie is the entity of that device. Where is your “WandTablet”? turn it on or charge it up.

If it is a Tablet then yes, normally you exclude those batteries. Same for your phone, watch etc.

Thanks that helps.

  1. In your device notification in the message selection you have chosen option 2. See the description of that input. Option 2 will not show Unavailable + Unknown sensors.
  2. In your dashboard notification in the message selection you have chosen option 1. See the description of that input. Option 1 will show Unavailable + Unknown sensors.

Blacky :grinning:

OK understood,
Point 1:
first the friendly name( Batterie) provided from this intergration is dumb

I manually changed it now. I cannot delete it or turn it on actually because of an another issue with the Tablet. I have to work on this another day. I changed the status to off ( only to test ) and now it is not here anymore.

point 2:

thanks for you explanation and it make sense. but it is still showing the condition as you explained on your post here as not true. ( there is no sensor reported on the dashboard)

do you have here any idea?

thanks for you help an your really good blueprint.

Answering to myself.
It is running properly.
The test here is not performed during running the template process, that why it cannot be true because all_ sensors is probably not existing or something like that.

@Blacky thanks for everything. I am now less dumb :slight_smile:

New Update 3.3

Stay Charged, Stay Smart! Customize it your way and let’s automate your battery maintenance! :battery::zap:

:new: Battery Sensors - Report Fields

You can now choose which fields are included when your battery sensors are shown in the low battery notification. The new option is in the Battery Settings section.

You can choose multiple options, but you must select at least one. Previously Friendly Name was hard coded. Available options now are:

  • Friendly Name
  • Floor
  • Area
  • Device
  • Entity ID

The fields will be reported in this format

Friendly Name {Floor} (Area) [Device] – Entity ID

Any field you don’t select (or that isn’t available for the sensor) is simply left out.


If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

If you like my blueprints, and would like to show your support or just say thank you? Click Here :smiling_face_with_three_hearts:

Enjoy

Blacky :grinning:

2 Likes