Howto create battery alert without creating a template for every device

emontes · June 27, 2018, 11:49pm

Interesting, I see exactly the same issue even though I added them to customise and then cleared the topics (sending an empty payload) but they keep being created.
If I click on one of them, even the battery_sensor_creation_disabled is showing as true
I am puzzled by that now.

NotoriousBDG · June 28, 2018, 12:41am

battery_sensor_creation_disabled needs to be set on your Pressure Upstairs entity, not Pressure Upstairs Battery entity.

emontes · June 28, 2018, 8:43am

Thanks.
I’ve tried every single entity ID and can’t make it work.
Everything with humidity/pressure I just added it customise , cleared the topics and it’s still showing up.
Pretty sure I am doing something wrong but can’t find what.

NotoriousBDG · June 28, 2018, 3:10pm

Can you go to the States panel (http://hassio.local:8123/dev-state), search for Pressure Upstairs in the attributes column, then post a screenshot? It should look something like the screenshot below.

emontes · June 28, 2018, 3:33pm

Sure thing, here you go:

NotoriousBDG · June 28, 2018, 5:35pm

Add this to your customize section, restart Home Assistant, clear the retained topics, then restart Home Assistant one more time.

homeassistant:
  customize:
    sensor.pressure_158d0001a21e25:
      battery_sensor_creation_disabled: true

emontes · June 28, 2018, 5:54pm

NotoriousBDG:

Add this to your customize section, restart Home Assistant, clear the retained topics, then restart Home Assistant one more time.
homeassistant:
  customize:
    sensor.pressure_158d0001a21e25:
      battery_sensor_creation_disabled: true

Just tried that and they are still showing up, unbelievable
For the sake of it, I had all that on my custom.yaml (tried everything):

sensor.humidity_158d0001a21e25:
battery_sensor_creation_disabled: true
sensor.humidity_158d000171dfdc:
battery_sensor_creation_disabled: true
sensor.pressure_158d000171dfdc:
battery_sensor_creation_disabled: true
sensor.pressure_158d0001a21e25:
battery_sensor_creation_disabled: true

sensor.humidity_downstairs_battery:
battery_sensor_creation_disabled: true
sensor.humidity_upstairs_battery:
battery_sensor_creation_disabled: true
sensor.pressure_downstairs_battery:
battery_sensor_creation_disabled: true
sensor.pressure_upstairs_battery:
battery_sensor_creation_disabled: true

sensor.pressure_158d0001a21e25_battery:
battery_sensor_creation_disabled: true
sensor.humidity_158d0001a21e25_battery:
battery_sensor_creation_disabled: true
sensor.pressure_158d000171dfdc_battery:
battery_sensor_creation_disabled: true
sensor.humidity_158d000171dfdc_battery:
battery_sensor_creation_disabled: true

NotoriousBDG · June 28, 2018, 7:13pm

Hrm, that’s odd. Can you confirm that your customize section is indented like the example I showed? Are you running the latest version from GitHub?

emontes · June 28, 2018, 7:50pm

Yes, I am using 1.0.10 and the indentation is the same. I use a custom.yaml file but I know it is being read as I have other configurations there.
Very weird, indeed.

sensor.humidity_158d0001a21e25:
 battery_sensor_creation_disabled: true
sensor.humidity_158d000171dfdc:
 battery_sensor_creation_disabled: true
sensor.pressure_158d000171dfdc:
 battery_sensor_creation_disabled: true
sensor.pressure_158d0001a21e25:
 battery_sensor_creation_disabled: true

NotoriousBDG · June 28, 2018, 10:03pm

Can you check the attributes of sensor.pressure_158d0001a21e25 on the States panel after you changed customize? You should see battery_sensor_creation_disabled in the attributes column if customize worked. it should look like this:

emontes · June 28, 2018, 10:39pm

Almost there ( I think!)
By doing what you asked, I confirmed the entry was not there as I was using those ones on its own custom file (xiaomi.yaml) so I added them:

So then I sent an empty payload to sensor,pressure and sensor.humidity for both sensors and also on config/state.

So:

1530225005: Received PUBLISH from hass (d0, q0, r0, m0, ‘homeassistant/sensor/hunidity_158d000171dfdc_battery/state’, … (0 bytes))
1530225010: Received PUBLISH from hass (d0, q0, r0, m0, ‘homeassistant/sensor/humidity_158d000171dfdc_battery/state’, … (0 bytes))
1530225013: Received PUBLISH from hass (d0, q0, r0, m0, ‘homeassistant/sensor/humidity_158d000171dfdc_battery/config’, … (0 bytes))
1530225029: Received PUBLISH from hass (d0, q0, r0, m0, ‘homeassistant/sensor/pressure_158d000171dfdc_battery/config’, … (0 bytes))
1530225033: Received PUBLISH from hass (d0, q0, r0, m0, ‘homeassistant/sensor/pressure_158d000171dfdc_battery/state’, … (0 bytes))
1530225054: Received PUBLISH from hass (d0, q0, r0, m0, ‘homeassistant/sensor/humidity_158d0001a21e25_battery/state’, … (0 bytes))
1530225061: Received PUBLISH from hass (d0, q0, r0, m0, ‘homeassistant/sensor/pressure_158d0001a21e25_battery/state’, … (0 bytes))
1530225065: Received PUBLISH from hass (d0, q0, r0, m0, ‘homeassistant/sensor/pressure_158d0001a21e25_battery/config’, … (0 bytes))
1530225070: Received PUBLISH from hass (d0, q0, r0, m0, ‘homeassistant/sensor/humidity_158d0001a21e25_battery/config’, … (0 bytes))

Saw the battery levels showing unknown on the UI and restarted but they are still showing.
Appreciate the help, btw!

NotoriousBDG · June 28, 2018, 11:27pm

Awesome. That looks better.

Did you also have retain flag set when you sent null payload?

mosquitto_pub -h MQTTSERVER -p 1883 -u MQTTUSER -P 'MQTTPASSWORD' -t "homeassistant/sensor/pressure_158d0001a21e25_battery/config" -r -n
mosquitto_pub -h MQTTSERVER -p 1883 -u MQTTUSER -P 'MQTTPASSWORD' -t "homeassistant/sensor/pressure_158d0001a21e25_battery/state" -r -n

After clearing the topics, you can also try re-runing mosquitto_sub to verify they’re gone.

emontes · June 29, 2018, 9:39am

NotoriousBDG:

Did you also have retain flag set when you sent null payload?
mosquitto_pub -h MQTTSERVER -p 1883 -u MQTTUSER -P 'MQTTPASSWORD' -t "homeassistant/sensor/pressure_158d0001a21e25_battery/config" -r -n
mosquitto_pub -h MQTTSERVER -p 1883 -u MQTTUSER -P 'MQTTPASSWORD' -t "homeassistant/sensor/pressure_158d0001a21e25_battery/state" -r -n
After clearing the topics, you can also try re-runing mosquitto_sub to verify they’re gone.

I was doing from HA and not from the command line, now I did from both and they were still there.
Now come (again) another funny thing, only thing I could think of was a cache or something so I cleared cache on my browser and restart HA again and 3 of them vanished (still don’t understand why!).
But there’s still one (Pressure Downstairs) there and I can’t get rid of it even going through different browsers.
mosquitto_sub shows topics are empty.

emontes · June 29, 2018, 12:38pm

It’s finally done, @NotoriousBDG!
Man heh, it was really driving me nuts.
What really helped was doing the following:

mosquitto_sub -t “homeassistant/sensor/#” | grep -i pressure

I could still see the pressure topics there, I sent a null, cleared the cache on the browser, restarted HA and voila, everything is as it should be.
Again, I’d like to thank you for the help here and for the entire thing, it’s really helpful!

NotoriousBDG · June 29, 2018, 1:08pm

Glad to hear you got it working. Happy to help.

kepler · July 12, 2018, 8:05pm

Hello, just wanted to let you (and possibly others) know that I have used your code and adapted it to show offline devices! But now I see that I used an old version
I know very little about programming, so I just tried a few changes and got it working. Maybe (probably) there are errors in there, but it appears to be working

################################################################
## Packages / Offline devices alert
################################################################

################################################
## Customize
################################################

homeassistant:
  customize:
################################################
## Node Anchors
################################################

package.node_anchors:
  customize: &customize
    package: 'offline_alert'

  expose: &expose
    <<: *customize
    haaska_hidden: false
    homebridge_hidden: false

################################################
## Group
################################################

group.offline_alert:
  <<: *customize
  friendly_name: "Offline devices Alert"
  icon: mdi:steam

################################################
## Automation
################################################

automation.offline_alert:
  <<: *customize
  friendly_name: "Offline devices Alert"

automation.offline_alert_clear:
  <<: *customize
  friendly_name: "Offline devices alert Clear"

################################################
## Group
################################################

group:
  offline_alert:
control: hidden
entities:
  - automation.offline_alert
  - automation.offline_alert_clear

################################################
## Automation
################################################

automation:
- alias: offline_alert
  trigger:
- platform: time
  at: '10:00:00'
- platform: time
  at: '18:00:00'
  condition:
- condition: template
  value_template: >
      {% macro offline_state() %}
      {%- set threshold = 40 -%}
      {% set domains = ['light', 'switch', 'sensor', 'binary_sensor', 'zwave', 'lock'] %}
      {% for domain in domains -%}
      {% for item in states[domain] if ((item.state | lower == "unavailable")) -%}
      {{ item.domain }} {{ item.name }} {%- if not loop.last %}, {% endif -%}
      {% endfor %}
      {%- endfor %}
      {% endmacro %}
      {{ offline_state() |trim != "" }}
  action:
- service: persistent_notification.create
  data_template:
    title: "Offline devices"
    notification_id: offline-devices-alert
    message: >
      {% macro offline_state() %}
      {% set domains = ['light', 'switch', 'sensor', 'binary_sensor', 'zwave', 'lock'] %}
      {% for domain in domains -%}
      {% for item in states[domain] if ((item.state | lower == "unavailable")) -%}
      {{ item.domain }} {{ item.name }} {%- if not loop.last %}, {% endif -%}
      {% endfor %}
      {%- endfor %}
      {% endmacro %}
      {{ offline_state() }}
- service: notify.slack_notify
  data_template:
    message: "Offline devices"
    data:
      attachments:
      - color: '#52c0f2'
        title: "These devices are offline"
        text: >
          {% macro offline_state() %}
          {% set domains = ['light', 'switch', 'sensor', 'binary_sensor', 'zwave', 'lock'] %}
          {% for domain in domains -%}
          {% for item in states[domain] if ((item.state | lower == "unavailable")) -%}
          {{ item.domain }} {{ item.name }} {%- if not loop.last %}, {% endif -%}
          {% endfor %}
          {%- endfor %}
          {% endmacro %}
          {{ offline_state() }}

- alias: offline_alert_clear
  trigger:
- platform: time
  minutes: '/30'
  seconds: 00
  condition:
- condition: template
  value_template: >
      {% macro offline_state() %}
      {%- set threshold = 40 -%}
      {% set domains = ['light', 'switch', 'sensor', 'zwave', 'lock'] %}
      {% for domain in domains -%}
      {% for item in states[domain] if ((item.state | lower == "unavailable")) -%}
      {{ item.domain }} {{ item.name }} {%- if not loop.last %}, {% endif -%}
      {% endfor %}
      {%- endfor %}
      {% endmacro %}
      {{ offline_state() |trim != "" }}
  action:
- service: persistent_notification.dismiss
  data:
    notification_id: offline-devices-alert

NotoriousBDG · July 12, 2018, 11:09pm

This is awesome. Thanks for sharing!

Mariusthvdb · July 13, 2018, 8:10am

cool.
it so happens I’m using a variant of one of your templates:

  {%- set threshold = 70 -%}
  {%- set domains = ['light', 'switch', 'sensor', 'zwave', 'binary_sensor', 'camera'] -%}
  {%- for domain in domains -%}
    {%- for item in states[domain] 
      if ((item.attributes.battery_low is defined and 
           item.attributes['battery_low'] == true) or 
          (item.attributes.battery_level is defined and 
           item.attributes['battery_level'] | int < threshold)) -%} 
         {{ item.name }} below {{threshold}}: {{item.attributes['battery_level']}} 
         {%- if not loop.last %} 
      {% endif -%}
    {%- endfor -%}
  {%- endfor -%}

I was just about to ask if I can substitute the fixed threshold for an input_number.battery_alert.

{%- set threshold = {{states('input_number.battery_alert')}} -%}

Nothing I try does the trick unfortunately. forgive me for posting here, dont want to hijack, and if no short answer is available, will take it elsewhere. Thought it to be very related though…

NotoriousBDG · July 13, 2018, 11:25am

Check out the latest version on GitHub. It already has that feature.

kepler · July 14, 2018, 6:36am

Thank you for writing this code! I now also see that it needs some tweaking, but I will continue with my efforts. Learning everyday