Gradually turn on lights.

[cd12172]

HI -

Direct question-

• is there anything obvious wrong with my configuration below
• since the ZEN32 scene controller really has no on/off state (for btn 1-4), and I am using it as a toggle without concern for long press or multi press - am I better off just looking for any change to x_hass.state in a rule condition to trap a toggle?

Detailed Use case -
A-Use ZEN32 scene controller to group and control sonos players
B-Keep ZEN32 lights sync'd with real world sonos states. [B is alread working in my implementation by controlling the always on/always off led parms on the ZEN32]

Environment
Reactor - latest-23063-c464b68
hass - 2023.12.3 core / 2023.12.0 Supervisor
Zwave JS UI - 9.3.2

• the add ons are running on the hass instance in a virtualbox vm

prior reading:
Using Zooz ZEN32 Scene Controller as Trigger
Adding remotes, scene controllers as entities to MSR
MSR Manual - Handling Home Assistant Events

**Current ZEN32 zwave description to MSR - reactor.yaml **

      event_targets:
        "event.sonos_scene_controller_scene_001":
          name: "ZEN32 Button 1"
          capabilities:
            - button
          events:
            - event:
                event_type: zwave_js_value_notification
                data:
                  node_id: 008 # Put your ZWaveJS node ID here
                  property: scene
                  property_key: "001" #  001=button 1, 002=button 2, etc.
              response:
                button.since:
                  from: event.context.id
                button.state:
                  from: event.data.value
                  map:
                    KeyHeldDown: hold
                    KeyPressed: single
                    KeyPressed2x: double
                    KeyPressed3x: triple
                    KeyReleased: release
        "event.sonos_scene_controller_scene_002":
          name: "ZEN32 Button 2"
          capabilities:
            - button
          events:
            - event:
                event_type: zwave_js_value_notification
                data:
                  node_id: 008 # Put your ZWaveJS node ID here
                  property: scene
                  property_key: "002" #  001=button 1, 002=button 2, etc.
              response:
                button.since:
                  from: event.context.id
                button.state:
                  from: event.data.value
                  map:
                    KeyHeldDown: hold
                    KeyPressed: single
                    KeyPressed2x: double
                    KeyPressed3x: triple
                    KeyReleased: release
                    #
                    # dump_all_states - This is for troubleshooting. Do not enable unless asked.
                    #dump_all_states: false

Findings-
-The Hass logbook is seeing the events - also seen in the screenshot below

• no update to the MSR created "ZEN32 Button 1"
• The MSR manual indicates my HASS version is newer than supported (2023.11.3). I am assuming the issue is in my config.

Area of interest:

• Is my cannonical names correct in the Reactor.YAML code above - I took it from the Reactor entity dialog screenshoted below i.e. event.sonos_scene_controller_scene_001

[Pabla]

Take a look at this thread

[cd12172]

Thanks - I referred to that post and a predesseor in my original post. I also went through the API documentation, still unable to trap events as a button.

[toggledbits]

You don't need to configure any custom events. The ZWaveJSController mapping for the ZEN32 produces five entities, usually named xxx Scene001 through ...005 (where xxx is your base device name). These all publish the button capability.

See also: https://smarthome.community/post/15176