Zooz ZEN72

Blueprints Exchange
, , ,
62

It worked for me but I had to make a new copy of the yaml file and make the following changes. You can just save it as zooz-zen72-800lr.yaml in the same folder and rename it. I think what is important is the “Model Name” matches.

blueprint:
  name: Zooz ZEN72 800LR
  description: Automations helper for the Zooz ZEN72 800LR Dimmer Switch using the Zwave
    JS integration. Credit and thanks goes to OP and contributors of this thread -
    https://community.home-assistant.io/t/zooz-zen72/322433/53
  domain: automation
  input:
    zooz_zen72:
      name: Zooz ZEN72 800LR
      description: The ZEN72 Switch to interact with.
      selector:
        device:
          integration: zwave_js
          manufacturer: Zooz
          model: ZEN72 800LR
          multiple: false
63

Thanks for the blueprints, it’s been helpful. I’m using this with smart bulbs, so local control is disabled. I was previously using Pico’s but am migrating since these look more like regular light switches and of course I don’t have to bundle all the wires in the switch.

Anyway, the previous blueprint I was using for the pico’s allowed the hold button to continue raising the brightness or dimming of the lights. I’ve tried just inserting the action into the hold - but isn’t not quite right. Was hoping someone might advise what I need to switch.

Previous blueprint for Pico: The section for dim down is near the end…

 - conditions:
    - condition: trigger
      id: down_pressed
    sequence:
    - repeat:
        sequence:
        - service: light.turn_on
          data:
            brightness_step_pct: '{{ step * -1 }}'
            transition: '{{ speed / 1000 }}'
          target:
            entity_id: !input entity
        - delay:
            milliseconds: !input speed
        until:
        - condition: numeric_state
          entity_id: !input entity
          attribute: brightness
          below: 1
  - conditions:
    - condition: trigger
      id: down_released
    sequence:
    - delay:
        milliseconds: 100
  - conditions:
    - condition: trigger
      id: off_pressed
    sequence:
    - service: light.turn_off
      data:
        transition: !input transition_off
      target:
        entity_id: !input entity

Brightness Increase:

  - conditions:
    - condition: trigger
      id: up_pressed
    sequence:
    - repeat:
        sequence:
        - service: light.turn_on
          data:
            brightness_step_pct: !input step
            transition: '{{ speed / 1000 }}'
          target:
            entity_id: !input entity
        - delay:
            milliseconds: !input speed
        until:
        - condition: state
          entity_id: !input entity
          attribute: brightness
          state: '100'
  - conditions:
    - condition: trigger
      id: up_released
    sequence:
    - delay:
        milliseconds: 100
64

Hey, I’m not sure if you addressed this (didn’t see it in this thread), but I believe it is (now?) possible to allow multiple models. I noticed the code inside the ZEN32 BP by @fxlt.

        device:
          filter:
          - integration: zwave_js
            manufacturer: Zooz
            model: ZEN32
          - integration: zwave_js
            manufacturer: Zooz
            model: ZEN32 800LR
          multiple: false

Thanks for putting this BP together, it’s a huge time saver.

65

All, I have updated the BP with the following changes:

  • Added support for ZEN72 800LR version
  • Added Scene 003 actions for external momentary dumb switch press/hold/release events (see top post for details and Zooz links)
  • Added support for value_raw events
  • Added loop-on-hold option
  • Added selector option for automation mode
  • Uncommented 3x actions

Some of these are significant changes, so please make sure you read and understand them before re-importing the BP.

Please test and let me know if any additional edits are needed!

2 Likes
66

Just got a chance to try this. I’m getting an error.

image
image1467×153 16.1 KB

My YAML on the BP is pretty simple so far.

alias: ZEN72 - Living Room Cans
description: ""
use_blueprint:
  path: X/Zen72.yaml
  input:
    zooz_zen72: fe159969c00e06661f33defcceae3363
    dimmer_up_1x:
      - service: light.turn_on
        metadata: {}
        data:
          transition: 1
        target:
          entity_id:
            - light.living_room_cans
    automation_mode: single

I just copied and pasted the updated BP into my BP .yaml. I did noticed that VS Code was throwing some errors at that point, but didn’t make any changes.

image
image892×509 42.6 KB

I removed the line breaks that VS Code was flagging, but that didn’t make a difference.

I’m gonna swap back to the previous version for now, but any ideas what I did wrong?

67

It’s something on my end. The old version is giving the same error.

68

Still haven’t figured this out.

I’d originally been importing you BP from a GitHub repo I set up so I could have versioning.

Last night I made the changes manually that made it all stop working. At the end of the night I got the old version working again by reimporting from GH. However that didn’t work for the new version and I’m still getting an error with that.

69

Looks like I had some improper formatting in the repeat loops. Please let me know if you’re still having issues.

1 Like
70

You’re awesome Ninja! That fixed the errors, and now this is all ready for when the ZAC99s show up that I ordered. Thank you so much for your help and the time spent writing this.

71

I modified this one to create a blueprint for a Zen71 800 LR. I’m still tweaking it, so I’m not ready to post it for general use quite yet.

72

Can someone explain what “action” I need in my automation in order to use the feature of holding the top or bottom paddle to brighten or dim my smart bulbs that the zen72 is controlling?

73

I haven’t tried this, but it’s something I’ll need to do as I recently swap some smart bulbs into a fixture controlled by one of these switches.

I believe you would set up a repeat action with an incrase light by X %. (Scratch that, repeat is built into the blueprint I believe).

74

Can you explain what you mean by this?

75

Set the mode to restart.

In the hold action, use the light.turn_on service call, and define a brightness step (%) or brightness step value.

Turn on the Loop <Upper/Lower> Paddle Hold Action toggle.

Define a paddle hold loop delay.

Let me know if you have any issues that require BP revisions.

76

I was able to follow and set up the first step to set up the service call. But where do I set the ‘Loop <Upper/Lower> Paddle Hold Action’ toggle?

UPDATE - I found the issue. At some point before you added support for the 800 series, I had created a copy of the blueprint and modified it manually. I just needed to pull the newest updates!

77

After getting the newest blueprint, I was able to follow these directions. But I still can’t get the hold action to do anything.

1 Like
78

Have you enabled Scene Control (Parameter 13) in your Zwave switch settings?

See earlier post #21.

80

Yes, scene control is enabled

81

@flintstones-fred I too ran into an issue with my ZEN72 700 series dimmer on the hold actions. Listening to the event in developer tools I noticed that the raw value (value_raw) did not match the blueprint on KeyReleased and KeyHeldDown. I corrected the values in the blueprint (KeyReleased from 2 to 1 ; KeyHeldDown from 1 to 2), but that broke everything. Instead I removed the or value_raw == <NUMBER> from all the conditions and now everything is working.

82

@okimdone Thank you, this fixed the paddle hold issue for me.

I also want to add that this blueprint works for the ZEN74 toggle dimmers as well. I just needed to add the following to the device filters in the yaml file.

  - model: ZEN74
  - model: ZEN74 800LR