Eaton 5-Scene Keypad (RFWC5) not broadcasting any event when turning off

The problem

I’m trying to configure the RFWC5 with Home Assistant and z-wave-js. I had it working before with the deprecated (now gone) z-wave integration, so I managed to get most of it working again, but turning off a button is not triggering any event in Home Assistant. The device itself is working in zwavejs2mqtt.

What works:

• Receiving an event through zwave_js_value_notification when pressing on the button to turn it on
• Toggling the light on all buttons through zwave_js.set_value

What doesn’t work:

• Receiving an event when pressing the button to turn it off.

The Indicator value entity created in Home Assistant doesn’t get updated automatically as it did with the previous integration, which is fixable through an automation (attached below). But it relies on being able to receive these notifications when pressing a button.

I tried all 3 events (zwave_js_notification, zwave_js_value_notification, and zwave_js_value_updated) just to see what I could find, but none of them are triggered when turning a button off. There doesn’t seem to be a way to receive these notifications currently.

What version of Home Assistant Core has the issue?

2022.5.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

z-wave-js

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Diagnostics information

No response

Example YAML snippet

The automation to update the Indicator value when receiving a z-wave-js notification. This works only when turning the button on.

- alias: Update scene controller indicator value when a button is pressed
  trigger:
    - platform: event
      event_type: zwave_js_value_notification
      event_data:
        node_id: 6
  action:
    - service: zwave_js.refresh_value
      data:
        entity_id: sensor.scene_contrl_indicator

Anything in the logs that might be useful for us?

The Home Assistant logs are empty.

The log in z-wave-js when turning the button on (this works):

2022-05-28T02:49:37.099Z CNTRLR   [Node 006] [!] [Scene Activation] sceneId: 1                      [Endpoint 0]
2022-05-28T02:49:37.100Z CNTRLR   [Node 006] [~] [Scene Activation] dimmingDuration: "default" => " [Endpoint 0]
                                  default"
2022-05-28T02:49:37.101Z SERIAL » [ACK]                                                                   (0x06)
2022-05-28T02:49:37.103Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  │ type: multicast
                                  └─[SceneActivationCCSet]
                                      scene id:         1
                                      dimming duration: default
2022-05-28T02:49:37.116Z SERIAL » 0x0109001306028702251d5c                                            (11 bytes)
2022-05-28T02:49:37.116Z DRIVER » [Node 006] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      29
                                  └─[IndicatorCCGet]
                                      indicator: 0 (default)

The log in z-wave-js when refreshing the indicator value (this works):

2022-05-28T02:49:37.246Z DRIVER « [REQ] [SendData]
                                    callback id:     29
                                    transmit status: OK
2022-05-28T02:49:37.256Z SERIAL « 0x0109000400060387030774                                            (11 bytes)
2022-05-28T02:49:37.257Z CNTRLR   [Node 006] [Indicator] value: metadata updated                    [Endpoint 0]
2022-05-28T02:49:37.258Z CNTRLR   [Node 006] [~] [Indicator] value: 6 => 7                          [Endpoint 0]
2022-05-28T02:49:37.259Z SERIAL » [ACK]                                                                   (0x06)
2022-05-28T02:49:37.259Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[IndicatorCCReport]
                                      indicator 0 value: 7
2022-05-28T02:49:37.263Z SERIAL » 0x0109001306028702251e5f                                            (11 bytes)
2022-05-28T02:49:37.264Z DRIVER » [Node 006] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      30
                                  └─[IndicatorCCGet]
                                      indicator: 0 (default)
2022-05-28T02:49:37.265Z SERIAL « [ACK]                                                                   (0x06)

The log in z-wave-js when turning the button off (this doesn’t work in Home Assistant):

2022-05-28T02:49:59.746Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  │ type: multicast
                                  └─[BasicCCSet]
                                      target value: 0
2022-05-28T02:49:59.747Z CNTRLR   [Node 006] treating BasicCC::Set as a report
2022-05-28T02:49:59.747Z CNTRLR   [Node 006] [~] [Basic] currentValue: 0 => 0                       [Endpoint 0]
2022-05-28T02:49:59.759Z SERIAL « 0x010a0004000604200100ff2d                                          (12 bytes)
2022-05-28T02:49:59.760Z SERIAL » [ACK]                                                                   (0x06)

Additional information

No response

[hamstercat]

I’m still trying to make it work, I’ve stopped using the physical buttons while I figure this out. I should get back to it and try again see what I’m missing. I will update to the latest version this week-end and see where that leads me.

Where I left it at is that the device works well in zwave-js, I’m just not managing to receive an event (any event) in Home Assistant when I press the button to turn it off.

I’ll re-interview the device and provide logs if I can’t figure this out, but do let me know if you manage to make it work on your side!

[ken-wolfe]

While I am not exactly proud of my solution, I have a solution… Maybe someone else has a better idea…

The automation that I am using above for turning off the lights, is now a generic “listener” which runs a script that updates the indicator on that scene controller. Then I made a new automation that listens for when the indicator changes and looks at the value of the indicator to figure out whether to turn off the light. It’s pretty ugly right now. I am going to figure out how if I can use a bitmask in the YAML to remove some conditions. Everything works though. I really wish the indicator could get auto updated when this event happens. That would save a bunch of automations.