node-zwave-js: [Bug]: Qubino smart light switch relay missing
Checklist
- [] I am not using Home Assistant. Or: a developer has told me to come here.
- I have checked the troubleshooting section and my problem is not described there.
- I have read the changelog and my problem is not mentioned there.
Deploy method
Docker
Zwavejs2Mqtt version
6.5.2
ZwaveJS version
zwave-js: 8.11.6
Describe the bug
I am unable to control the relay inside the device. There should be an endpoint, endpoint1 and endpoint2. The latter should be the relay.
Now I am only able to control the led light. The binary switch disables the led instead of the relay switch.
2nd bug parameter: [46-112-0-3] Touch Functionality: Disable Alarm: is set to Enabled (1) but is not listed as default. Yet the manual states that 1 is the default.
Parameter no 3. – turning off alarming Values (size is 1-byte dec): • Default value 1
2022-03-13 10:15:42.887 INFO ZWAVE: Node 46: value updated: 37-0-currentValue false => true
2022-03-13 10:15:43.120 INFO ZWAVE: Node 46: value added: 32-0-currentValue => 255
2022-03-13 10:15:43.143 INFO ZWAVE: Node 46: value added 46-32-0-currentValue => 255
2022-03-13 10:15:44.826 INFO ZWAVE: Node 46: value updated: 50-0-value-66049 0 => 38.9
2022-03-13 10:15:53.350 INFO ZWAVE: Node 11: metadata updated: 49-0-Power
2022-03-13 10:15:53.353 INFO ZWAVE: Node 11: value updated: 49-0-Power 167 => 139.1
2022-03-13 10:15:57.877 INFO ZWAVE: Node 46: value updated: 37-0-currentValue true => false
This is me turning on the relay with the touch controls and trying to turn it off again with the button in zwavejs2mqtt. It targets the same value yet, it is different. I’m unsure what happend here. Already tried doing a re-interview. This was working before I did a docker upgrade from 6.5.0 to 6.5.2.
To Reproduce
Nvt
Expected behavior
Have the ability to control the relay.
Additional context
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (9 by maintainers)
Sorry, I already merged. Can re-open if the file doesn’t fix the issue.
I always forget to mention that, you need to this file too in a subfolder
templates
next to the file you’re testing.When I get to it at some point, I’ll make it so the embedded config DB will be used as a fallback. Then that’s not necessary anymore.
@thecobra666 Can you try this file as described here.
If it works, I can include the change in the next release.
@zwave-js-bot add compat flag to 0x0159:0x0008:0x0052:0.0
(removed your logs because they contain the network key)
It could also be that the driver determined the endpoints to be unnecessary and does not expose them. Make sure to capture a driver log (level debug) of the inclusion (or maybe a re-interview before that), so I can check if that’s the case.
Hi, this is not mentioned in the manual but is indeed required for the mini dimmer. There are also no settings I needed to change on the device. It’s installed as is and was working as such. But to rule it out, I’ll exclude and include the device again tonight and report back. If not okay I’ll enable the silly debug log and attach it also.