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
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.
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.
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!
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.
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.
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 :)ââ
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.
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 ?
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.
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.
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.
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.
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)
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.
Stay Charged, Stay Smart! Customize it your way and letâs automate your battery maintenance!
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 button in the top post
If you like my blueprints, and would like to show your support or just say thank you? Click Here