Eaton/Aspire RFWC5 5-button Controller Scene Deactivate Event

[apetrycki]

I'm trying to find a way to get Home Assistant to recognize that a button press has occurred to deactivate a scene. When a scene is deactivated, I get:

16:51:41.143 CNTRLR [Node 019] treating BasicCC::Set as a report
2021-09-22 16:51:41.146 INFO ZWAVE: Node 19: value updated: 32-0-currentValue 0 => 0

HA does not see this as an event or update. "Basic" is not seen in the network dump. What I would like to do is trigger an Indicator LED refresh when this event occurs like I used to be able to do with the old Z-Wave integration, which would then trigger an automation to turn off the scene.

Why are the Basic CC target/current value IDs missing, or should the device treat Basic Set as an event?

zwave_js_dump.json.txt

[AlCalzone]

From your dump it looks like the device uses Scene Activation CC to communicate which button was pressed. Don't you get any event when the scene should be deactivated?

A more complete driver log than just these two lines would be helpful.

[apetrycki]

Also, any idea why the messages are received twice? I always get 2 reports of the same value over MQTT.

[AlCalzone]

but then I'd need 2 automations instead of just the 1

True, but you send less commands over a very constrained network.

Do you have sample output from a controller that does report which scene was deactivated?

Nope, sorry. I only have a handful of devices and scene controllers aren't very popular.

I also noticed that Z-Wave JS advertises sensors for the scene and scene delay but they don't show up in HA. Is this just something that's not supported yet? I tried doing a rediscover.

You'll have to ask that in the HA repo. The driver isn't concerned with HA's sensors.

Also, any idea why the messages are received twice? I always get 2 reports of the same value over MQTT.

You probably have the controller twice in the node's association groups (or 255, the broadcast node).

[kpine]

I also noticed that Z-Wave JS advertises sensors for the scene and scene delay but they don't show up in HA. Is this just something that's not supported yet? I tried doing a rediscover.

You'll have to ask that in the HA repo. The driver isn't concerned with HA's sensors.

For one reason, Scene Activation notifications are usually handled as events in HA, so there's no need for a sensor. But I think the other reason is that the sceneId value ID is value-less. The driver provides the value ID and metadata, but the value ID has no value, at least that's the case from the provided dump. Without a value, there's no state for a sensor.

[AlCalzone]

But I think the other reason is that the sceneId value ID is value-less.

That's also because it is handled as an event.

[apetrycki]

Thanks for the PR and all the info!

[AlCalzone]

#3398 and corresponding PR #3399