-
-
Notifications
You must be signed in to change notification settings - Fork 592
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
Inovelli LZW36 - Light turning off reliably after ~2 hr 10 min #2159
Comments
Let me know when you have a log. This seems oddly specific and I would assume this is some really weird interaction. |
Can you turn on debug logging for zwave-js-server and the HA integration and include those as well? The combination of the three logs (zwave-js, zwave-js-server, and the integration) will help narrow this down more quickly. You can add the following to your
You can also call the
|
Here's my log of the switch rebooting itself, it doesn't look like anything happens from zwave-js prior to the reboot. |
@firstof9 So is this where the reboot happens?
Which would make this the change in HA that triggered the state ~2 hours before?
@AlCalzone OZW doesn't support supervision, right? Could this be a fw bug resulting from a supervision command? We could try disabling that CC and see if it fixes the device, which would pinpoint the bug to that section of the fw? Or rule out that one difference between us and OZW where this isn't happening? It would explain why this only happens upon switching to zwave-js. Edit: @firstof9 is going to test my crazy theory in the morning by adding the compat flag manually to disable Supervision. |
I'm gonna say yes, that's the only thing that shows up in the logs when the thing RGBed me. |
@blhoward2 You could be right - there's at least something the device does incorrectly in regards to Supervision. When the device is first controlled with supervision, it immediately reports success for a supervision session we never used (0):
It then reports that the command we sent is in progress:
10 seconds later when the device is turned back on with
we receive the final message for the previous session and the response that our current command is in progress:
The final update for this never comes. |
After the modifications to disable the supervision CC the switch seems to no longer "reboot" itself. Attached is the log from the whole 2+hrs of debug. |
@AlCalzone Ive informed Inovelli. Should I push a PR to add the compat flag for now until it's fixed? |
Yup sounds like a good idea |
I am now experiencing this with my LZW36. Turning on and off fan in Home Assistant turns on and off the light entity along with the fan. Debug Logs: Also might be related to #2154 Running v 0.1.20 |
Please create a new issue for this. |
Checklist:
Describe the bug
After a reliable amount of time (near 2hr 10min), Inovelli and Home Assistant users on ZJS are experiencing the "Fan" endpoint of the device turning off. This is only when controlled "ON" by Home Assistant, not when the light is physically toggled.
Device information
Inovelli LZW36
Node ID: 16
Did you change anything?
Did this use to work before?
How are you using
node-zwave-js
zwavejs2mqtt
(latest) docker imagezwavejs2mqtt
(dev) docker imagezwavejs2mqtt
Manual Docker buildnode-zwave-js
branch:zwavejs2mqtt
branch:HomeAssistant
version 2021.3.4node-zwave-js
branch:zwavejs2mqtt
branch:node-red-contrib-zwave-js
To Reproduce
Steps to reproduce the behavior:
Additional context
Did not seem to be the case on earlier versions of ZJS integration into HA.
Logfile:
Incoming, will replace once available.
The text was updated successfully, but these errors were encountered: