Thanks for your kind words.
This is all done in HA. In your battery entity look for sensor display precision. For me I dont have any decimal places. Above your post shows you how to get to this area in HA.
Blacky
Thanks for your kind words.
This is all done in HA. In your battery entity look for sensor display precision. For me I dont have any decimal places. Above your post shows you how to get to this area in HA.
Blacky
When updating to version 1.6 - If you are using the “Battery Sensors - Custom Group” option then you will need to select and adjust the new input for “Custom Group - Battery Low Warning Level”.
New Feature
Battery Sensors - Custom Group - The custom group has its own independent “Battery Low Warning Level” setting.
Use case: You may have a few batteries that require a different low battery warning level. Some devices may require you to replace / charge your batteries at a higher battery % so it can operate correctly. Some devices can still operate at less than 5% battery. Before you would have to have 2 automations to achieve this. This can now be set up in the one automation using the "“Battery Sensors - Custom Group” with its own independent “Custom Group - Battery Low Warning Level” setting.
Easy Notify - Sensor Selection - Easy notify now allows you to select a new option if you would like to use “Use All Battery Sensors Minus Excluded Battery Sensors + Custom Group”
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 it seems the import of this blueprint isnt working anymore?
the link: https://gist.github.com/Blackshome/4010fb83bb8c19b5fa1425526c6ff0e2
gives a 404:
@matrover @SKAL @Alwin_Hummels
Thanks for the heads up.
Everything is back up and running, please try again.
Thanks for your patience.
Blacky
Hi Blacky,
great blueprint you created. What would be very practical in the notifications is to specify the area of the device in the text. Maybe you can integrate this as an option in the blueprint.
Something like that:
{{ device_attr(device_id(trigger.entity_id), ‘name’) }} im Bereich ({{ area_name(trigger.entity_id) }})
And the last thing is the trigger options. It would be perfect if the automation were also triggered automatically when a device enters the status of too little charge, is not available or is low. A quick reaction is often necessary, especially with heating thermostats. Binary sensor that triggers if any battery level goes beyond a threshold (broken in 2022.09)
Best regards
Welcome to the community.
Thanks for your suggestion.
I am not following, What state is “too little charge”. Some batties report a “Low” state. The “Low” state = “on” in HA so that has been covered. What state do your “heating thermostats” report?
Blacky
@Blacky I always get excited when I see your avatar on a blueprint.
You sir, are a legend. Thank you very much for all your efforts in this community!
I just found your donation link, enjoy a brew on me.
Cheers!
Great blueprint as always. Could we possibly have NotificationChannel support for Android users? thanks
Any way to format the “{{all_sensors}}” payload to get a CR between each value?
It works with the standard HA app message
Great. Thank you, forgot that I could filter the data…
No problem, happy to help. More information on all that type of information can be found Here
Blacky
Have a brew on me too! The only thing I can think of is having a sensor we can check from elsewhere that is just true/false to indicate whether there is currently a battery with low charge. Then I can put something on the homepage to remind me if I haven’t looked at the notifications. Just an idea. Thanks for the blueprint!
Thank you for this Blueprint, Would be cool if we could get the batterys added to a To-Do list so we know to replace them or order more. Then when its done we can check it off the list.
Cheers. Also the ability to ignore “unavailable” ones in the check. I have a couple of sensors that drop out and back in from time to time as they’re on the edge of wifi range