Hi,
i want to use this blueprint and did activated it. but i only get " Unavailable" statusses:
Battery level is unavailable!
Battery level is unavailable!
Kantoor Sensor Low battery level is unavailable!
Eetkamer Sensor Low battery level is unavailable!
Serre Sensor Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
You will find that you have these as the blueprint just reports what you have.
You could update the friendly names so they make more sense.
You have 2 x Battery level is unavailable! entities and 3 x Low battery level is unavailable! entities + another 3 entities. They are all unavailable.
Go to Settings > Device & Services > Entities tab at the top. and search for them. You could run a status filter. Once you find them consider updating the friendly name.
Blacky 
i started getting a bunch of ālow battery level is unavailableā from my z-wave devices. seems some update stopped polling this. for me it was ok to disable them (and restart home assistant) since the blueprint still notifies based on ābattery levelā.
1 Like
Same problem.
I am currently not seeing it. It all seams to be working.
Blacky
For the past few days, I have been getting this warning at the same time each day. All of my battery devices look fine. I am running Version 2.6 and never had this issue. Help, please 
You have 2 batteries entities that are unavailable. Both have the same name of Low battery level and the is unavailable comes from the blueprint.
Go into Device & services > entities tab at the top and search for Low battery level. You can also use the filter status of unavailable and you will see them both.
Blacky
1 Like
Much appreciated. So originally what I did is check every battery device and all were/are ok. I just did what you suggested and I have 2 entries for the same device. Why would this be? The device works perfectly and the battery is at 95%.
Hereās what HA says:
This entity is no longer being provided by the zwave_js integration. If the entity is no longer in use, delete it in settings.
1 Like
Iām not completely sure, but I believe this entity originally reported Low battery (as a binary state) rather than a percentage. The zwave_js integration later removed it in an update to better align with the Z-Wave specification, which defines battery status through percentage reporting and notifications instead of a fixed āLowā entity.
Your device reports battery as a percentage, which is much better than a simple Low indicator. For the blueprint, this works perfectly since you can decide the exact threshold at which it should be reported, rather than relying on a fixed ālowā state.
As HA mentioned, you can delete the entity. In some cases it can be removed directly, but if not, you can simply disable it. For those who want it gone completely, removing and re-adding the device will prevent the entity from being created again. Keep in mind that doing this will reset history and may create new entity IDs, which could affect existing automations.
Now itās up to you how you want to handle it. If you ask me, Iād try deleting the entity first. If that doesnāt work, Iād remove and re-add one device to see how it goes. If everything works well and Iām happy with the result, Iād then do the next one, and so on.
Blacky
Thank you for the help - this worked.
1 Like
Hi. Trying to set this up. Notifications are working fine but text helper just shows āunknownā and I get an error on the dashboard of āUndefinedError: list object has no element 1ā
Any thoughts?
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
Updated to 3.0 and getting a bunch of āLow battery level is unavailable!ā In addition to my actual alerts.
Now you will have to find them.
Go into Device & services > entities tab at the top and search for battery. You can also use the filter status of unavailable and you will see them all.
Blacky
1 Like
@Blacky merging this feature would be very useful.
also, are you up for adding a feature to Exclude Entities based on text patterns? I needed this so I created my own BP with this a while back but would love to switch to your BP since your v3 has some nice features. My code is on github if you want to see how I did itā¦ it was not as easy as I thought it would be but you are better at this stuff than I am so maybe easy for you.
@Blacky Thank you for the helpful blueprint. I organize most of my dashboards by room , so tend to keep generic entity friendly names. It would be helpful to have an option to add the room name to the friendly name in the notification, or let me know if Iām missing something.
I can see the notification_id being useful for the UI notifications and I have this on my list to do so this will be added.
Regarding Time trigger pattern: We have a time trigger already and I not sure if we need to check more than once a day 
Are people using this for checking house energy battery levels If so I then can see it being useful feature to have.
Thanks for the suggestion about excluding entities with a text pattern. I get where youāre coming from, but Iām not 100% sure this would be the best approach for this blueprint. Let me explainā¦ and I hope you can keep an open mind to something that may be different to what youāre used to, but could actually work better.
Home Assistant already has a native, user-friendly way to handle exactly what youāre describingā¦ labels or hidden entities. Hereās how:
- Go to Settings > Devices & services > Entities (tab at the top) and search for your text pattern.
- All matching entities will be shown. Enter Selection Mode (using the selection icon).
- Select the entities you want, making sure you donāt accidentally include ones that just happen to share the same text (this is the key advantage over blind text matching).
- In the top right, choose Add label or use the ā® menu to hide them in one step.
- In the blueprint, under Battery Settings, either select that label in Excluded Battery Sensors or enable Exclude Hidden Battery Sensors.
This gives you the same end result as a text-pattern filter, but with several advantages:
Built into Home Assistantā¦ no extra blueprint inputs or regex required.- Easier to manage long-termā¦ if you rename or add entities, just update the label once.
- Avoids accidentally excluding entities that only partially match.
- More user-friendlyā¦ no regex or text filters to learn.
- Transparentā¦ you can always see exactly which entities are excluded.
On the other hand, adding text-pattern exclusion has some clear disadvantages:
Accidental exclusionsā¦ a text filter could unintentionally catch unrelated entities. Labels force the user to be deliberate.- Complexity for most usersā¦ many people arenāt comfortable with regex/wildcards. Another input field adds confusion for those who wonāt use it.
- Support burdenā¦ with text patterns, a user might unknowingly exclude an entity and never get a low-battery notification. When the device eventually stops working, it looks like the blueprint failed, when in reality the exclusion was too broad. Labels avoid this because they are applied intentionally and visibly by the user.
Between entity exclusion, label exclusion, and now the option to exclude hidden entities, this blueprint already covers the common use cases in a clean way. Adding another exclusion input just for text pattern could make setup more complicated for everyone else. That said, I do have some other exclusion options on my list to consider for future improvements.
I never say never thoughā¦ maybe thereās a scenario Iāve overlookedā¦
Blacky
1 Like
@Blacky
I understand your thoughts on using Labels (I use labels often) I think using labels for this 1 purpose is 100x more admin work vs placing it in one blueprint. Especially for those of us that have hundreds or entities
real world exampleā¦
using your blueprint my report looks like thisā¦
KitchenTablet Battery level @ 1%
Aeon Labs Water Sensor Battery level @ 0.0%
Master Bathroom Shade Remote Battery Level @ 7.0%
Master Bedroom Shade Remote Battery Level @ 0.0%
Guest Room Shade Remote Battery Level @ 12.0%
Theater Bathroom Water Leak Detector Battery level @ 10.0%
Playroom Shade Remote Battery Level @ 12.0%
Aqara RTCGQ11LM Battery is unknown!
Battery Level - Theater Shade 2 is unavailable!
Battery is unavailable!
Battery Level - Theater Shade 1 is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
Low Battery Level is unavailable!
Low battery level is unavailable!
Low battery level is unavailable!
From an administrative / user standpoint, labels are a lot more work and more complexity to ārememberā they must do. Vs simply adding 1 line in the blueprint filter.
These are entities that are in a lot of devices and most people dont even know or will never need, see or touch (like Low Battery sensor).
With labels they need to āknowā to do it and add a label after every device they add.
with my method the user adds 1 simple text pattern to exclude ALL entities, forever. Takes 3 seconds to add, instead of 100x as much time and the need to look at and maybe modify every battery device when adding a new device.
In 3 seconds I add low_battery_level and all the āLow battery level is unavailable!ā messages are gone forever, and I never have to edit a single entity.
oh, and I also added some options to make it easier to read and see Entity ID (optional, can be disabled or only show ID and not Name) and what devices are actually unavailable, vs devices that have the sensor and do not report properly. Thus my report looks like thisā¦
1 Like
Would it be possible to add an option to exclude battery level is unavailable rather than me having to add them to an exclude label?