[bug] Qubino Flush Dimmer - using I2 status updates are not triggered after restart
See original GitHub issueVersion
Checklist:
- I am not using HomeAssistant. 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 problem was not mentioned there.
Build/Run method
- Docker
- PKG
- Manually built (git clone - npm install - npm run build )
zwavejs2mqtt version: 2.3.0 zwave-js version: 6.6.2
Describe the bug
Context / Setup
I am using a Qubino Flush Dimmer. It has 3 different inputs for physical switches. I1 is used to control the dimmer itself. I have hooked up I2 to a second switch. In the configuration I have set up [10-112-0-100] Enable / Disable Endpoints I2
to [9] Sensor binary
.
This gives me another Basic
report [10-32-2-currentValue] Current value
which toggles from the values 0 to 255 and vice versa whenever I press the mono-stable switch on I2.
The Problem
Whenever I restart zwavejs2mqtt it doesnt report anymore. I can see in the debug log that the zwave event is coming in, but I dont see the Basic
section in the control panel nor it isn’t reported to mqtt. When I re-interview the node everything works fine after that.
To Reproduce
Steps to reproduce the behavior:
- restart zwavejs2mqtt
- Click the switch connected on I2, no mqtt message nor update on control panel.
- re-interview the node and the problem is gone.
Expected behavior
After restarting zwavejs2mqtt it should still report the toggle on I2 without re-interviewing the node.
Issue Analytics
- State:
- Created 3 years ago
- Comments:18 (11 by maintainers)
Top GitHub Comments
I have a fibaro installed somewhere else. I will switch the qubino with the fibaro. I think this is the best solution for me, since I am using the I2 only in one place.
I have asked qubino if they could instruct me to do a firmware update on myself. But they unfortunately wont do it. They also don’t support OTA updates. So I am stuck with that old firmware. Kinda disappointing.
@AlCalzone thanks a lot for your support so far. I really like zwave-js and zwavejs2mqtt. You guys are doing an amazing job! Best zwave implementation so far. Thanks!
Nice! Then I’ll update the PR so it closes this issue 😃