ZHA & Z-Wave Lovelace Cards

Configuration
, , ,
1

I installed my new HUSBZB-1 yesterday, and everything seems to be working great. I’m just curious though… what is the purpose of the Lovelace cards for ZHA and Z-Wave when the devices already show up in the other cards, i.e. lights, switches, sensors, etc.?

776×191 6.07 KB

I’m also curious about the ZHA configuration panel. I installed the Sengled lightbulbs yet I am getting entity IDs for more than just the light (light.kitchen_1). What are the other entity IDs for?

Thanks,

Dennis

2

Using a switch as an example.

The switch will show up as a switch even if there is an issue with it. The Z-wave card as you will report if there is an issue with the device or the network. If a device is failed it would show as failed in the zwave card but not necessarily in the switch. (I can’t recall, the switch may change to unavailable).

This can be helpful to have in the frontend for troubleshooting but the entities are more useful to me in an automation to let you know if something has failed.

1 Like
3

Where do you get these cards?

4

I use this script to check for zwave issues. It’s set to run every couple hours. It will notify of any problems.

########################################
zwave_health_check:
  alias: Zwave Health Check

  sequence:
    - condition: template
      value_template: "{{ states.zwave | selectattr('attributes.is_failed', 'defined') | selectattr('attributes.is_failed','eq', True ) | list | count >= 1 }}"
  
    - wait_template: "{{ is_state('script.notify_all_engines' , 'off') }}"

    - service: script.notify_all_engines
      data_template:
        title: "ZWAVE Problem"
        who: "john"
        message: >-
          {{ states.zwave | selectattr('attributes.is_failed', 'defined') | selectattr('attributes.is_failed','eq', True ) | map(attribute='name') | list | join(', ') }}
1 Like