Zooz ZEN72

Sanfam · February 15, 2022, 3:52am

@dheat , @LarsenTech and @millerstevew , the issue is actually not the automation but the default configuration of the switch. The Zen72 by default has scene control disabled. As such, your double tap events don’t fire a central scene event.

In the config for the switch, set Scene Control to Enable and try again. It should work.

@IOT_Ninja , might be worth adding a comment to the main post about this.

dave5k · February 17, 2022, 4:47am

@IOT_Ninja can this be expanded to support the Zooz ZEN74? It is essentially the same switch in toggle format instead of paddles. Best I can tell it has identical functionality. I created my own blueprint to do this but would be nice to just have one unified blueprint for this purpose.

IOT_Ninja · February 17, 2022, 10:11am

I can edit and re-upload as a separate BP later to address the specific case of the ZEN74 since it uses the same scene/attribute values as the ZEN72. Unfortunately, I don’t think HA BPs allow for multiple model selectors (per this feature request), and removing the model restriction could result in issues if a user tried to use the wrong BP with on a similar Zooz product.

dave5k · February 24, 2022, 6:09am

Ok, that makes sense. I’ll just use my own local copy, works well enough for me! Thanks for making this.

bromarc339 · April 1, 2022, 7:42pm

Thanks! I adapted this for my zen77.
I am hoping to have the switch operate (through z-wave) like a normal up/down dimmer and increase/decrease brightness when the light is on and the up/down is held. What can be used for loop conditions to facilitate this?

IOT_Ninja · April 1, 2022, 11:17pm

No additional settings should be needed. Standard press-and-hold dimming is the default out of the box.

doomi · June 22, 2022, 4:28am

I can’t get it to work out of the box when the switch is in smart bulb mode. It doesn’t do anything when I hold.

I can get it to dim a step/percentage by using call service - dim, but can’t get it to loop continuously if I hold the switch. Just one step. Then if I release and hold it will do another step.

Any suggestions?

ajb004 · June 23, 2022, 5:02pm

I’m having the same problem except I’m not calling a service. I’m using the increase/decrease brightness device attribute. Everything works great except when I hold the up or down paddle, it will only move brightness one step.

ajb004 · June 26, 2022, 4:47am

@doomi I think i found a fix for the dimming. I had to turn slowRefresh off in the central scene section of the zwave options. Seems to be working now. Hope this helps.

doomi · June 27, 2022, 2:10am

@ajb004 Very interesting! I’m not seeing that option. Are you using mqtt or zwave JS?

ajb004 · June 27, 2022, 3:59am

@doomi I’m using zwave2mqtt running in a container on a raspberry pi with a Zooz Zwave adapter. I don’t use MQTT though, I use the Web Socket Server

doomi · October 3, 2022, 3:11am

@ajb004 I finally had a chance to move everything over to mqtt and this worked. Just wanted to say thank you for your guidance.

fergbrain · November 20, 2022, 7:54pm

I’m also trying to setup the up/down dimmer when up/down is held. I tried adding a Repeat action to the “Bottom Paddle Hold” option that would keep going until the button was released (by listening to the “KeyReleased” event…based this on this post: Integrate Zooz ZEN34 with Home Assistant – PCB Isolation). Here’s the relevant YAML for the “Bottom Paddle Hold” action that I created:

repeat:
  until:
    - condition: device
      device_id: 8110xxxxxxxxxxxxxxxxxxxxxxxxxxxx
      domain: zwave_js
      type: value
      command_class: 91
      property: scene
      property_key: "002"
      value: KeyReleased
  sequence:
    - service: light.turn_on
      data:
        brightness_step_pct: -10
      target:
        entity_id: light.living_room_recessed_lights_group
    - delay:
        hours: 0
        minutes: 0
        seconds: 0
        milliseconds: 500

But I kept getting this error:

Value 24-91-0-Scene 001 can't be found on node Node(node_id=24). Got <homeassistant.components.blueprint.models.BlueprintInputs object at 0x7f6a9c17c4c0>

Here’s the full error:

Blueprint Zooz ZEN72 generated invalid automation with inputs OrderedDict([('zooz_zen72', '8110xxxxxxxxxxxxxxxxxxxxxxxxxxxx'), ('dimmer_up_1x', [OrderedDict([('service', 'light.turn_on'), ('data', OrderedDict()), ('target', OrderedDict([('entity_id', 'light.living_room_recessed_lights_group')]))])]), ('dimmer_down_1x', [OrderedDict([('service', 'light.turn_off'), ('data', OrderedDict()), ('target', OrderedDict([('entity_id', 'light.living_room_recessed_lights_group')]))])]), ('dimmer_down_hold', [OrderedDict([('repeat', OrderedDict([('while', [OrderedDict([('condition', 'device'), ('device_id', '8110xxxxxxxxxxxxxxxxxxxxxxxxxxxx'), ('domain', 'zwave_js'), ('type', 'value'), ('command_class', 91), ('property', 'Scene 001'), ('value', 'KeyReleased')])]), ('sequence', [OrderedDict([('service', 'light.turn_on'), ('data', OrderedDict([('brightness_step_pct', -10)])), ('target', OrderedDict([('entity_id', 'light.living_room_recessed_lights_group')]))])])]))])]), ('dimmer_down_2x', [OrderedDict([('service', 'homeassistant.turn_off'), ('data', OrderedDict()), ('target', OrderedDict([('entity_id', 'switch.adaptive_lighting_living_room')]))])]), ('dimmer_up_2x', [OrderedDict([('service', 'homeassistant.turn_on'), ('data', OrderedDict()), ('target', OrderedDict([('entity_id', 'switch.adaptive_lighting_living_room')]))])]), ('dimmer_down_release', [])]): Value 24-91-0-Scene 001 can't be found on node Node(node_id=24). Got <homeassistant.components.blueprint.models.BlueprintInputs object at 0x7f6a9c17c4c0>

I think this should work, right? But I can’t figure out what the issue is that is causing the error.

IOT_Ninja · November 23, 2022, 6:15am

Can you go to dev tools, listen to zwave_js_value_notification events, and provide the full output?

I’m guessing that Zooz may have changed the configuration of that switch so that both the value and value_raw return the integer/string corresponding to the scene value (ie, 00 for both, vs my bp that is based on value = KeyPressed)

mmx · November 24, 2022, 2:57am

Yup, you guessed right. I upgraded my ZEN72 and ZEN32 switches to firmware 10.30 and noticed my automations stopped working. After spending hours troubleshooting, I discovered value now mirrors value_raw.

Here is a sample event:

event_type: zwave_js_value_notification
data:
  domain: zwave_js
  node_id: 13
  home_id: 4232454107
  endpoint: 0
  device_id: 322f2a2ecb4e24aa8b5c8ad6794758dd
  command_class: 91
  command_class_name: Central Scene
  label: Scene 002
  property: scene
  property_name: scene
  property_key: "002"
  property_key_name: "002"
  value: 0
  value_raw: 0
origin: LOCAL
time_fired: "2022-11-24T02:56:11.787964+00:00"
context:
  id: 01GJKS0W0B97SJRADR5NS3A0W3
  parent_id: null
  user_id: null

IOT_Ninja · November 24, 2022, 3:21am

I actually chatted with Agnes at Zooz today, and she was adamant that this is an issue on the HA/Zwave JS side not correctly interpolating the Zwave value_raw, and hadn’t heard any other reports of this issue.

When I get some time, I suppose I should probably rewrite my BPs to cover both scenarios, just to be safe.

mmx · November 24, 2022, 4:06am

Prior to updating the firmware, I had the latest zwave_js (8.5.0) and HA Core (2022.11.4) working just fine with firmware <=10.10. My other Zooz switches, such as the ZEN71 and ZEN76, keep sending their value as strings like before (they haven’t been updated).

If it makes your life easier, please feel free to use the changes pasted below. I ended up modifying the BP to read value_raw and compare the integer attributes listed on this page (section “Manual control”).

action:
- variables:
    scene_id: '{{ trigger.event.data.label }}'
    attribute_id: '{{ trigger.event.data.value_raw }}'
- choose:
  - conditions: '{{ scene_id == ''Scene 001'' }}'
    sequence:
    - choose:
      - conditions: '{{ attribute_id == 0 }}'
        sequence: !input 'dimmer_up_1x'
      - conditions: '{{ attribute_id == 3 }}'
        sequence: !input 'dimmer_up_2x'
      - conditions: '{{ attribute_id == 5 }}'
        sequence: !input 'dimmer_up_4x'
      - conditions: '{{ attribute_id == 6 }}'
        sequence: !input 'dimmer_up_5x'
      - conditions: '{{ attribute_id == 1 }}'
        sequence: !input 'dimmer_up_hold'
      - conditions: '{{ attribute_id == 2 }}'
        sequence: !input 'dimmer_up_release'
  - conditions: '{{ scene_id == ''Scene 002'' }}'
    sequence:
    - choose:
      - conditions: '{{ attribute_id == 0 }}'
        sequence: !input 'dimmer_down_1x'
      - conditions: '{{ attribute_id == 3 }}'
        sequence: !input 'dimmer_down_2x'
      - conditions: '{{ attribute_id == 5 }}'
        sequence: !input 'dimmer_down_4x'
      - conditions: '{{ attribute_id == 6 }}'
        sequence: !input 'dimmer_down_5x'
      - conditions: '{{ attribute_id == 1 }}'
        sequence: !input 'dimmer_down_hold'
      - conditions: '{{ attribute_id == 2 }}'
        sequence: !input 'dimmer_down_release'

enormous · November 24, 2022, 4:16am

Hey there. Would you be able to share your Zen74 version? If you’ve already got it sorted would save me the work.

IOT_Ninja · November 24, 2022, 4:21am

If it follows the same Scene/Attribute values as the ZEN72, all you have to edit is the model line in the existing BP. (Probably also want to edit the descriptions too, but they aren’t strictly required, at least for functionality.)

mmx · November 24, 2022, 4:28am

If you get to talk with Agnes again, here’s a ZEN72 vs. ZEN77 debug output from zwave_js that highlights the issue (the states object array is missing).

EDIT: the filename on the right in the image says “ZEN76”, but it’s actually from a ZEN77 with latest firmware (10.30.2).