Aeon Labs WallMote Quad - Z-Wave JS - Press and LongPress

Blueprints Exchange
, ,
1

Hello All,
I am new to Home Assistant.

This is my first Blueprints for Aeon Labs WallMote Quad ( ZW130 by AEON Labs)

blueprint:
  name: Aeon Labs WallMote Quad
  description: Create automations for the Aeon Labs WallMote Quad
  domain: automation

  input:
    wallmote_quad_device:
      name: WallMote Device Quad
      description: A WallMote Quad device.
      selector:
        device:
          integration: zwave_js
          manufacturer: AEON Labs
          model: ZW130

    button_1_pressed:
      name: Button 1 Pressed
      description: Actions to run when button 1 is pressed.
      default: []
      selector:
        action:

    button_1_held:
      name: Button 1 Held Down
      description: Actions to run when button 1 is held down.
      default: []
      selector:
        action:

    button_2_pressed:
      name: Button 2 Pressed
      description: Actions to run when button 2 is pressed.
      default: []
      selector:
        action:

    button_2_held:
      name: Button 2 Held Down
      description: Actions to run when button 2 is held down.
      default: []
      selector:
        action:

    button_3_pressed:
      name: Button 3 Pressed
      description: Actions to run when button 3 is pressed.
      default: []
      selector:
        action:

    button_3_held:
      name: Button 3 Held Down
      description: Actions to run when button 3 is held down.
      default: []
      selector:
        action:

    button_4_pressed:
      name: Button 4 Pressed
      description: Actions to run when button 4 is pressed.
      default: []
      selector:
        action:

    button_4_held:
      name: Button 4 Held Down
      description: Actions to run when button 4 is held down.
      default: []
      selector:
        action:

mode: single
max_exceeded: silent

trigger:
  platform: event
  event_type: zwave_js_value_notification
  event_data:
    device_id: !input wallmote_quad_device
    command_class_name: "Central Scene"

action:
  - variables:
      action_name: "{{ trigger.event.data.value }}"
      property_key: "{{ trigger.event.data.property_key }}"
  - choose:
      - conditions: "{{ action_name == 'KeyPressed' and property_key == '001'}}"
        sequence: !input button_1_pressed
      - conditions: "{{ action_name == 'KeyHeldDown' and property_key == '001' }}"
        sequence: !input button_1_held
      - conditions: "{{ action_name == 'KeyPressed' and property_key == '002' }}"
        sequence: !input button_2_pressed
      - conditions: "{{ action_name == 'KeyHeldDown' and property_key == '002' }}"
        sequence: !input button_2_held
      - conditions: "{{ action_name == 'KeyPressed' and property_key == '003' }}"
        sequence: !input button_3_pressed
      - conditions: "{{ action_name == 'KeyHeldDown' and property_key == '003' }}"
        sequence: !input button_3_held
      - conditions: "{{ action_name == 'KeyPressed' and property_key == '004' }}"
        sequence: !input button_4_pressed
      - conditions: "{{ action_name == 'KeyHeldDown' and property_key == '004' }}"
        sequence: !input button_4_held
3 Likes
2

Excellent, well done!

3

Nice, had no ide how to do it. Will try it out.

4

Fantastic, thank you!

I can recommend also to include an additional action which is the KeyReleased event.
This way it can be used with e.g. covers, the KeyHeldDown starts the cover movement and the KeyRelease stops it.

5

Excellent work! I also reviewed your post about the Fibaro Keyfob, I found that it doesn’t exactly produce the same data as what was in the blueprint so I edited it and posted it on the blueprint exchange!

This automation works perfectly, thank you!

6

I tried this blueprint multiple times last night. Every time I imported the blueprint and tried to save the automation, my automations crashed. Automation tab/option disappeared from my HA. If I tried to go directly to the automation URL, everything was faded out. Solution was to delete the blueprint and restart.

Did not have time to debug a lot. Checked the logs quickly, but nothing out of the ordinary. I have other blueprints without problems. As others here write, this blueprint should work well - so it’s probably not the blueprint itself, but a combination. I appreciate any suggestions or help :slight_smile:

7

I have just added this blueprint and the issue I am having is saying that NO DEVICES are present, however, in my devices I see it listed, and from ZwaveJStoMqtt it is listed with no issues as ZW130

8

Sorted !!, was an issue with ZwaveJS to point at the local ZwaveJs2Mqtt, it was a port issue, now the devices are showing !! and btw the automation worked brilliant

9

hmm, has this automation stopped working for anyone else?