Zooz ZEN72

Tags: #<Tag:0x00007fc40e6fe850> #<Tag:0x00007fc40e6fe788> #<Tag:0x00007fc40e6fe698> #<Tag:0x00007fc40e6fe558>

This blueprint is for simplifying the scene configuration for the Zooz ZEN72 Dimmer Switch, for use with the Z-Wave JS Integration, listening to the zwave_js_value_notification used in release 2021.04+. It’s adapted directly from my ealier ZEN30 and ZEN27 blueprints.

Each of the two ‘buttons’ on this switch has 7 different configurable scene options:

  • 1x, 2x, 3x, 4x, 5x Tap Up Button
  • 1x, 2x, 3x, 4x, 5x Tap Down Button
  • Press and Hold Up Button
  • Press and Hold Down Button
  • Release Up Button
  • Release Down Button

This blueprint aims to simply and condense all of the scene triggers into a single automation.

Note that a few of the options conflict with default configuration options, and have been commented out in the blueprint action area. You can remove the comment tags at your own risk to remap them.
For example, triple tapping enters the inclusion/exclusion modes. Single taps would also be important to leave as-is, unless you’re using smart bulbs and only want the switch to trigger them. Full info from Zooz here. I made notes on the scenes with default behaviors in the input area.

blueprint:
  name: Zooz ZEN72
  description: Automations helper for the Zooz ZEN72 Dimmer Switch using the
    Zwave JS integration.
  domain: automation
  input:
    zooz_zen72:
      name: Zooz ZEN72
      description: The ZEN72 Switch to interact with.
      selector:
        device:
          integration: zwave_js
          manufacturer: Zooz
          model: ZEN72
    dimmer_up_1x:
      name: Top Paddle 1x
      description: "Action to run on dimmer upper paddle single tap.
      Default: Turn on dimmer switch load to last/custom/full/max brightness."
      default: []
      selector:
        action: {}
    dimmer_up_2x:
      name: Top Paddle 2x
      description: "Action to run on dimmer upper paddle double tap.
      Default: Turn on dimmer switch to full/max/custom brightness."
      default: []
      selector:
        action: {}
    dimmer_up_3x:
      name: Top Paddle 3x
      description: "Action to run on dimmer upper paddle triple tap.
      Default: Enter inclusion/pairing mode."
      default: []
      selector:
        action: {}
    dimmer_up_4x:
      name: Top Paddle 4x
      description: Action to run on dimmer upper paddle quadruple tap.
      default: []
      selector:
        action: {}
    dimmer_up_5x:
      name: Top Paddle 5x
      description: Action to run on dimmer upper paddle quintuple tap.
      default: []
      selector:
        action: {}
    dimmer_up_hold:
      name: Top Paddle Hold
      description: "Action to run on dimmer upper paddle press-and-hold.
      Default: Increase dimmer brightness level."
      default: []
      selector:
        action: {}
    dimmer_up_release:
      name: Top Paddle Release
      description: Action to run on dimmer upper paddle release.
      default: []
      selector:
        action: {}

    dimmer_down_1x:
      name: Lower Paddle 1x
      description: "Action to run on dimmer lower paddle single tap.
      Default: Turn off dimmer switch load."
      default: []
      selector:
        action: {}
    dimmer_down_2x:
      name: Lower Paddle 2x
      description: Action to run on dimmer lower paddle double tap.
      default: []
      selector:
        action: {}
    dimmer_down_3x:
      name: Lower Paddle 3x
      description: "Action to run on dimmer lower paddle triple tap.
      Default: Enter exclusion/un-pairing mode."
      default: []
      selector:
        action: {}
    dimmer_down_4x:
      name: Lower Paddle 4x
      description: Action to run on dimmer lower paddle quadruple tap.
      default: []
      selector:
        action: {}
    dimmer_down_5x:
      name: Lower Paddle 5x
      description: Action to run on dimmer lower paddle quintuple tap.
      default: []
      selector:
        action: {}
    dimmer_down_hold:
      name: Bottom Paddle Hold
      description: "Action to run on dimmer lower paddle press-and-hold.
      Default: Decrease dimmer brightness level."
      default: []
      selector:
        action: {}
    dimmer_down_release:
      name: Bottom Paddle Release
      description: Action to run on dimmer lower paddle double tap.
      default: []
      selector:
        action: {}

mode: single
max_exceeded: silent

trigger:
  - platform: event
    event_type: zwave_js_value_notification
    event_data:
      command_class_name: Central Scene
      device_id: !input zooz_zen72

action:
  - variables:
      scene_id: "{{ trigger.event.data.label }}"
      attribute_id: "{{ trigger.event.data.value }}"
  - choose:
      - conditions: "{{ scene_id == 'Scene 001' }}"
        sequence:
          - choose:
              - conditions: "{{ attribute_id == 'KeyPressed' }}"
                sequence: !input dimmer_up_1x
              - conditions: "{{ attribute_id == 'KeyPressed2x' }}"
                sequence: !input dimmer_up_2x
              #- conditions: "{{ attribute_id == 'KeyPressed3x' }}"
                #sequence: !input dimmer_up_3x
              - conditions: "{{ attribute_id == 'KeyPressed4x' }}"
                sequence: !input dimmer_up_4x
              - conditions: "{{ attribute_id == 'KeyPressed5x' }}"
                sequence: !input dimmer_up_5x
              - conditions: "{{ attribute_id == 'KeyHeldDown' }}"
                #sequence: !input dimmer_up_hold
              - conditions: "{{ attribute_id == 'KeyReleased' }}"
                #sequence: !input dimmer_up_release
      - conditions: "{{ scene_id == 'Scene 002' }}"
        sequence: 
          - choose:
              - conditions: "{{ attribute_id == 'KeyPressed' }}"
                sequence: !input dimmer_down_1x
              - conditions: "{{ attribute_id == 'KeyPressed2x' }}"
                sequence: !input dimmer_down_2x
              #- conditions: "{{ attribute_id == 'KeyPressed3x' }}"
                #sequence: !input dimmer_down_3x
              - conditions: "{{ attribute_id == 'KeyPressed4x' }}"
                sequence: !input dimmer_down_4x
              - conditions: "{{ attribute_id == 'KeyPressed5x' }}"
                sequence: !input dimmer_down_5x
              - conditions: "{{ attribute_id == 'KeyHeldDown' }}"
                sequence: !input dimmer_down_hold
              - conditions: "{{ attribute_id == 'KeyReleased' }}"
                sequence: !input dimmer_down_release

*15/7/21 Edit: Uncommented Hold and Release actions after reports that they were disappearing during Blueprint import.

@ziptbm, can you try this out, and let me know if I need to make any edits? I’m assuming the Zen72 follows the typical Zooz trigger.event.data.value conventions, but I can edit or switch to using the value_raw data if needed.

It seems to work just like the version I modified of your ZEN27 blueprint.

Only thing I haven’t figure out is incremental dimming a Hue bulb using the paddles. Should this blueprint be able to do that?

I commented out the 3x press, Hold, and Release functions in my blueprint. Did you un-comment the applicable lines before deploying?

I try to avoid smart bulbs whenever possible, and tend to find double taps easier/quicker than holds, but I did a quick test and it seems to work fine for me. What do your trace logs show?

(I don’t have any ZEN72 switches, so this was completed on a ZEN30, but should still be applicable.)
Screenshot from 2021-07-14 22-07-13

Alternatively, if you want to explicitly define dimming steps, you can set the dimming percentage by using the call service:
Screenshot from 2021-07-14 22-32-47

Screenshot from 2021-07-14 22-33-03

Interesting. It looks like for your ZEN27 and ZEN72 blueprints that the commented out lines for 3x press, Hold, and Release are all gone from the YAML presented to me through File Editor. I see in your code above those are hashed out, but they’re not even listed for me in my UI. I will try adding those back manually to see what happens.

I’m assuming you commented out 3x press due to the pair/unpair functionality. Why did you comment out Hold and Release?

I am using most of these switches with Hue bulbs, so I’ve disabled the physical control of the switch and I am instead having the blueprints adjust the Hue entity. It’s overkill, but the bulbs came with the house, so it didn’t make sense to swap them out. As a result, the Hue bulb groups aren’t shown as Devices, which is why I believe my only option is to use the Call Service action and then step brightness. I may need to group the Hue bulbs myself within HA to make those visible as devices.

Still a work in progress, but MUCH better now that the Scene 1 and 2 swap was figured out.

Local dimming, and the 20% night mode. If the commented lines are completely disappearing, I might uncomment at least the hold/release options.

I have a similar setup in the bedroom, where I have disabled local control for the relay output on a ZEN30 and use it to control multiple outlets on a ‘Tasmotized’ power strip.

Even if you group them together, I think you still have to use a call service to trigger a group in an automation.

The lines themselves for 3x, Hold, and Release did not import with the yaml file via the Blueprint import. The yaml just skipped them entirely, so there are no hashtags to remove. I had to manually insert the two lines for Hold, but have not added the others back yet. Weird…it’s like the blueprint import skips over importing those lines due to the hashtags or something.

No, I was saying that I would un-comment the applicable lines in the Blueprint, so that they would actually import correctly. HA has a tendency to remove commented lines (especially when switching between visual and YAML editing, as well as importing), which is very frustrating.

2 Likes

Got it. Well, thanks again for building this blueprint! It’s super helpful.