It potentially affects any hub that sends COMMAND_CLASS_SUPERVISION commands.
My understanding is that COMMAND_CLASS_SUPERVISION is a way to send a command that requires the receiving devices to respond with a status (success/failure). Without it, the device will acknowledge that a command was received (ACK), but will not acknowledge wither or not is was able to execute the command successfully.
Without COMMAND_CLASS_SUPERVISION, the device would need to send reports in order for the hub to determine if the status actually changed
2 Likes
@Eric_Inovelli @EricM_Inovelli. Right. So it doesn’t affect only HA as others use node-zwave-js, you just haven’t seen reports as those aren’t as popular. Any hub using supervision would experience this. OZW doesn’t support it so nothing running on OZW triggers the bug.
Hubitat also supports it so this is likely happening there too. Though those drivers have to be changed to use Supervision I believe (versus we do it across the platform) so it’s possible no one has done that yet.
Also, @firstof9 confirmed that disabling Supervision for this device seems to fix it. Logs of the run with it disabled are available at the link I posted earlier.
I need to talk to @alcalzone but I assume we’ll disable this for now for all users unless the fw can be rolled out quickly.
1 Like
Got it, ok thanks for letting me know - very helpful! I’ll regroup with @EricM_Inovelli when he gets here and I’m sure we can get this taken care of fairly easily on our end with the manufacturer.
3 Likes
We’re going to push a PR to the device file today disabling it for now. Let us know when it’s fixed please.
1 Like
This makes sense of what I’ve been seeing. I have my preferences to return to previous state on return to power, but I have seen the lights cycle as if it was air gapped and turned back on.
Thanks for the support here Eric! I never witnessed it but noticed my fan was always turning off, so glad we got it figured out!
Sometimes doing it the “right” way (ZJS programming) brings out the littlest of mistypes lol.
So do we have to exclude the device and then include again after this fix?
I was able to do a re-interview from the zwave2js-mqtt web interface and that fixed it for me.
Just re-interview the node.
Hi, I re-interviewed my Inovelli node but it is still turning off after 2 hours. I must be doing something wrong I’m guessing. Any other tips or suggestions I could try? Thank you!
Make sure you’re running the latest zwavejs.
Check your log for errors while re-interviewing as well.
Thank you for your quick reply. I’m on Current version: 0.1.26 which should be the latest version. I will turn my log level up and try a re-interview again and let you know what I see. Thank you again.
Might be good now. I restarted HA did another re-interview and 3 hours later fan is still on. I should have started with a restart. Thank you again.
2 Likes