Howto create battery alert without creating a template for every device

ProfKay · October 9, 2018, 4:24pm

Yes, or just comment them out

pdobrien3 · October 16, 2018, 4:08pm

So I finally had one of my batteries drop below the level I set. Everything worked perfectly. Notifications and all. I put new batteries in the device today though and the battery sensor has not updated so I keep getting the same notifications. I have a modified version as I don’t use MQTT to generate the sensors. Any ideas @NotoriousBDG?

Eeeeeediot · October 19, 2018, 10:09am

Does anyone have any idea how to do this?

joch · October 19, 2018, 11:22am

Would it be possible to post this non-MQTT version?

pdobrien3 · October 19, 2018, 11:55am

It is just the regular version minus the two mqtt automations. It works very well except for updating the battery sensors. I don’t think there is a trigger to update them outside of a Home assistant restart.

If I, or someone else, could figure that part out, it would be very beneficial for me.

walaj · October 19, 2018, 5:25pm

Im seeing potential errors from the package in my installation - errors originally raised at Error doing job: Task exception was never retrieved - TypeError

Any suggestions on where to start investigating?

pdobrien3 · October 19, 2018, 9:55pm

Ha ha ha…I get that error also. Had no idea where it was coming from. Get it at every start-up

kiwijunglist · October 20, 2018, 4:58am

hi @NotoriousBDG

Thanks for your battery sensor package, I 'm using the latest version from your github (v1.1.2)
Very easy to add to my home assistant and It’s working well.

Cheers
Kiwi

e_jp · October 28, 2018, 8:02pm

Hello,

Anyone have done some node-red conversion? I’m looking to create a telegram notification flow (as I can’t use the same bot twice in HA and node-red). I’m not sure to fully understand how the telegram automation, especially the action part of the rule:

action:
- condition: template
value_template: *low_battery_check
- service: notify.telegram
data_template:
title: “Low Battery Levels”
message: *message

especially the *low_battery_check and *message. So I don’t know yet how to recreate this is node-red.

elnaor · October 30, 2018, 9:18pm

@NotoriousBDG,

Hi, I finally installed mosquitto and re-installed your code. But it dont creating sesors for my xiaomi devices… I can see only my iphone battery in the group.
Any suggestions?

Thanks a lot!

Naor

Coolie1101 · October 31, 2018, 5:48am

Could it be possible using the “homeassistant.update_entity” service?
" Please note that you must be on v0.81.1 or later. v0.81.0 did not allow the use of a list for the service data for homeassistant.update_entity"

See post below.

champ26 · October 31, 2018, 4:36pm

i’m not a code ninja but am using this low battery tool.

so if we were to modify this low battery automation, would we leave the template sensors in place and just change our automation to use this homeassistant.update_entity service?

elnaor · November 2, 2018, 10:26am

My bad… MQTT discovery was not activated.

Works like a charm!

Dixey · November 10, 2018, 4:07pm

Things has been working swimmingly for months without a hiccup. Wonderful code work!
However, since the mqtt fiasco, things are back running but I’ve got some orphan battery sensors out there who’s names have changed and I cannot figure out how to get rid of them.
Question: Is there a place where I can just get rid of the past and rebuild it (just the battery sensors)?

dkmcgowan · November 11, 2018, 5:30am

I wanted to try this out, can the first post be updated with the latest package? I tried to scroll through the 400+ posts to find the latest package, but not sure I got it

Coolie1101 · November 11, 2018, 6:33am

github.com

notoriousbdg/Home-AssistantConfig/blob/master/packages/battery_alert.yaml

################################################################
## Battery Alert Package by NotoriousBDG
##
## Source: https://raw.githubusercontent.com/notoriousbdg/Home-AssistantConfig/master/packages/battery_alert.yaml
################################################################

################################################################
## Changelog
################################################################
##
## 1.0.0 (2018-02-14)
##   Added
##   - Added version number to enable better tracking
##
## 1.0.1 (2018-02-15)
##   Added
##   - Added battery_sensor_creation_disabled attibute to skip
##     creating a battery sensor even when an battery attribute
##     exists.
##

This file has been truncated. show original

PixelJonas · November 11, 2018, 8:21am

Hey I was just implementing your awesome script. I have the same thermostat like @Nightcat and encounter the same problem. Any way I can support?

RolfKoenders · November 11, 2018, 10:17am

First of all, Thanks! This is a great pacakge! The scripts works nicely for some of my battery levels like phones and so on. I also have a bunch of binary sensors which are xiaomi devices which are not showing up by default. (MQTT, and discovery is turned on).

I tried to add a battery_template like the following:

binary_sensor.door_window_sensor_158d000183ff71:
  friendly_name: Front door
  device_class: door
  battery_template: "{{ state_attr('binary_sensor.door_window_sensor_158d000183ff71', 'battery_level') | int }}"

but that doesn’t give me any result? Anyone knows how to get that to work? Thanks in advance.

Nightcat · November 11, 2018, 3:39pm

@Dixey
you need to clear the retained config messages from your mqtt broker.
Check in your states screen if the battery sensors show you the mqtt topic of their config message and then go ahead and send an empty retained message at that topic to clear them.

I hope this helps

Nightcat · November 11, 2018, 3:44pm

@PixelJonas
I dont think @NotoriousBDG has done anything about that bug yet, he hasnt updated the project in a while…
So far I still have the same bug, I will try and have a look into the code to see if I can find any solution…