Q-Light Zerodim 2-Pol event not supported by zwave-js
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist
-
[X] I have checked the troubleshooting section and my problem is not described there.
-
[X] I have read the changelog and my problem was not mentioned there.
Describe the bug
What causes the bug? Manual controll of device doesn´t turn off the state
What do you observe? When physically turning of the light dimmer, zwave-js doesn´t use the message sent by the dimmer.
What did you expect to happen? Light to be set off.
This issue has been discussed in slack: https://zwave-js.slack.com/archives/CLBT7K407/p1654623836846899
Device information
Manufacturer: Q-Light Model name: ZERODIM 2-Pol Node ID in your network: 007
How are you using node-zwave-js?
- [ ]
zwavejs2mqttDocker image (latest) - [ ]
zwavejs2mqttDocker image (dev) - [ ]
zwavejs2mqttDocker manually built (please specify branches) - [ ]
ioBroker.zwave2adapter (please specify version) - [ ]
HomeAssistant zwave_jsintegration (please specify version) - [ ]
pkg - [ ]
node-red-contrib-zwave-js(please specify version, double click node to find out) - [ ] Manually built from GitHub (please specify branch)
- [ ] Other (please describe)
Which branches or versions?
version:
node-zwave-js branch: 9.3.0
zwavejs2mqtt branch: 6.11.0
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
No, it never worked anywhere
If yes, where did it work?
No response
Attach Driver Logfile
👋 Hey @geirra!
It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS. Please make sure you upload the correct one.
To sum up some info provided by @AlCalzone on slack, since i know others are seeing this problem to.
2022-06-07T18:34:19.214Z DRIVER « [Node 007] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 187
└─[MultiChannelCCCommandEncapsulation]
│ source: 1
│ destination: 0
└─[MultilevelSwitchCCReport]
current value: 42
target value: 0
duration: 1s
info by alcalzone
Basically the device tells zwave-js "I'm at 42. In 1 second I'll be at 0"
These types of events are not support atm.