GE Switches and Dimmers do not reflect double-up or double-down because they use the BasicCC for those events

Describe the bug

GE dimmer/switches are capable of double tap events, but those are not captured here and result in the current value going out of sync with the device.

These are the steps to make it work under qt-openzwave: https://community.home-assistant.io/t/howto-add-double-tap-support-for-ge-switches-and-dimmers-in-ozw-beta/228871/16.

The original qt-openzwave issue which has more detailed info is at: OpenZWave/qt-openzwave#60.

This appears to result from this because the devices use BasicCC for these events despite supporting the Multi-Level Command Class: #388

Non-compliant or not, it is how they work… Is there a way to IgnoreMapping here like in ozw 1.6?

Note: If possible, these devices should also auto-associate the controller into group 3 so that it receives the double-tap events.

To Reproduce Steps to reproduce the behavior:

1. Pair switches in zwavejs2mqtt.
2. Double tap up or down

Device information Which device(s) is/are affected? Various GE switches and dimmers (confirmed on 14294, 14291) What are the node IDs?

Logfile:

Note: I have a script that resets the light to the default levels upon turning on. That accounts for the 50 --> 50 messages.

Double-tap up (from a prior double-tap up state, hence 255–>255):

Double-tap up from off, just in case being in a former double-tap state affects it (note this one is out of order on the console log):

(The current value goes to 255 and HA thinks the device is now at 100%, but the physical dim has not changed. They are now out of sync. The currentValue is 255, the target Value is 50.)

Double-tap down:

For comparison, off to normal on:

For comparison, on to normal off:

Console log:

[robertsLando]

The problem is explained here

@larstobi The fix needed in DOcker contrib is explained there

[robertsLando]

@kpine In version 6 there are value notification and value updated events to distinguish them