Z-Wave device battery level

Configuration Z-Wave
10

I believe this happens because the values are None when HA is started

11

Should there be a fix for it or is it okay to receive them?

12

any news for this problem? i have the same error

13

Ultimately I don’t know if there should be a fix but I have found that I receive these at startup and they do not cause any problems. My understanding is that this displays because the template (or maybe zwave?) hasn’t yet initialized. Once it has these errors stop and the template displays correctly in the UI.

14

They are initialization errors at startup and can be safely ignored unless they persist. They are caused by the fact that template sensors are initialized pretty quickly but if they rely on ZWave values, those may not be available for a minute or more as your ZWave network slowly initializes itself. In the meantime you may get hundreds of these errors. Annoying but not harmful.

15

For what it’s worth, it seems you can get rid of the warning WARNING:homeassistant.components.sensor.template:UndefinedError: 'None' has no attribute 'attributes'. The templating doc here contains the following example:

{% if states.device_tracker.paulus %}
  {{ states.device_tracker.paulus.attributes.battery }}
{% else %}
  ??
{% endif %}

I tried it myself by changing my value_template from

{{ states.binary_sensor.living_area_door_sensor_2.attributes.battery_level }}

to

{% if states.binary_sensor.living_area_door_sensor_2 %}
  {{ states.binary_sensor.living_area_door_sensor_2.attributes.battery_level }}
{% else %}
  n/a
{% endif %}

and so far, I’m not seeing the warnings anymore after restarting HASS.

6 Likes
16

Great find! Thanks for sharing! Now my log file is much cleaner

17

Definitely going to give that a try - thanks!

18

Noice! I thought I’d just have to live with these, which is a problem since I have so many templated sensors.

Thanks!

19

@fanaticDavid, Can I use in my configuration file while defining the sensor itself like below?

sensor:
  - platform: template
    sensors:
      thermostat_downstairs_current_status:
        value_template: '{{ states.climate.downstairs.attributes.operation }}'
      thermostat_downstairs_current_status_fan:
        value_template: '{{ states.climate.downstairs.attributes.fan }}'
      thermostat_downstairs_away_mode:
        value_template: '{{ states.climate.downstairs.attributes.away_mode }}'

Thanks

20

I’m sorry but I’m not quite understanding your question. I’m also not familiar with the climate component.

21

I know this thread is old, but it fits my question :wink:

I have a zwave motion sensor that gives me several sensor nodes and a zwave.node_name entity, that shows up in the front-end:

How can I access the battery level with a value template?

22

That would look something like this:

- platform: template
  sensors:
    hall_sensor_battery:
      value_template: >-
        {%- if states.zwave.hall_sensor_4 -%}
          {{ states.zwave.hall_sensor_4.attributes.battery_level }}
        {%- else -%}
          n/a
        {%- endif -%}
      unit_of_measurement: '%'
      entity_id: zwave.hall_sensor_4
6 Likes
23

Thank you for your very quick answer! It works :slight_smile:

1 Like
24

My pleasure :slight_smile:

25

Wondering if anyone would know the answer to this, Prior to somewhere around release 0.39 or 0.40 when battery levels suddenly began to appear I was unable to get my Schlage zwave lock to show me a battery level through a template. I would get this message -> ‘Error rendering template: SecurityError: access to attribute ‘__32’ of ‘DomainStates’ object is unsafe.’

Release 0.39 or 0.40, I believe, began showing the battery levels and I didn’t need a template to have them show in the front end but with release 0.41 the battery levels disappeared again and I am back to having templates to show battery levels however just as prior to 0.39 I can not get my Schlage lock to show me a battery level.

Does anyone know of a solution to this message? -> Error rendering template: SecurityError: access to attribute ‘__32’ of ‘DomainStates’ object is unsafe. (zwave.__32 is the entitiy id of my lock, also I did set it up with a network key and it works as expected, just unable to show the battery level on the front end)

Thanks!

26

Try this for a template:

states.zwave["32"].attributes.battery_level
27

I tried this in the Dev Tools but received this error message -> “Error rendering template: TemplateSyntaxError: expected name or number”

{% if states.zwave.[“32”] %}
{{ states.zwave.[“32”].attributes.battery_level }}
{%- else -%}
n/a
{%- endif -%}

Since it’s a syntax error I am thinking it’s a typo or it doesn’t like the [“32”] for the name?

28

Remove the period between zwave and [“32”]. I didn’t put one there :wink:

29

Good catch, unfortunately that didn’t do it either. Sorry, one thing I failed to mention is that there is 2 underscores prior to the node number of 32 as shown below. If I do not use the underscores the message reads "Error rendering template: UndefinedError: ‘None’ has no attribute ‘attributes’.

“{{ states.zwave[”__32"].attributes.battery_level }}" in the Dev Tool the message it still displays -> “Error rendering template: SecurityError: access to attribute ‘__32’ of ‘DomainStates’ object is unsafe.”.