-
-
Notifications
You must be signed in to change notification settings - Fork 623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Homeseer WD200+ dimmer not providing updates to MQTT topics on change #1426
Comments
Please test #1453 |
@AlCalzone #1453 did not solve this issue. Looking at new zwavejs logs it is the same message at the end after an update: |
Oh, right - I just skimmed through the issues with the polling support label. |
@crzykidd It might be that the device in question has a firmware issue. I would like to ask Homeseer about this, but I'll need another log that includes the entire interview process as well as a switching attempt. |
@AlCalzone I am attaching new logs. zwavejs_1.log has node 22 which is the Homeseer WD200+ from zwavejs2mqtt. For comparison since the switches seem to be working fine in OZW with zwave2mqtt, I am attaching a log for that as well in OZW_log.txt The switch in question in this log is node003. |
Describe the bug
When setting the changeValue topic with MQTT to turn on/off or set dim level the light changes to the correct setting but the MQTT topics currentValue and targetValue never get updated.
Discussion of issue: https://zwave2mqtt.slack.com/archives/C01DQ24SDKL/p1610818512273700
It looks like SupervisionCCReport command is failing in the zwave logs.
Device information
Which device(s) is/are affected (make/model)? Homeseer WD200+
What are the node IDs? 22
Last Known Working Configuration
New device
Previously working device (node-zwave-js)
Previously working device (other platform)
Installation information
How did you install
node-zwave-js
?node-zwave-js
?zwavejs2mqtt
?git clone
-yarn install
-yarn run build:full
)To Reproduce
Steps to reproduce the behavior:
Logfile:
zwavejs_1_WD200_LightOn.log
The text was updated successfully, but these errors were encountered: