You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My steinels give "[Node 059] Error during node interview: Node 59 does not support the Command Class Version! (ZW0302). Results in no entities and strange behaviour.
#4009
Closed
3 of 11 tasks
eddriesen opened this issue
Jan 1, 2022
· 1 comment
· Fixed by #4029
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
YES, BUT a Home Assistant developer has told me to come here
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there.
Describe the bug
The problem
So , I have a strange phenomenon going on, and I'm not shure it's a bug or PEBCAK.
hassio on nuc, 2021.12.7
zwave_js addon: 0.1.51
USB stick: https://devices.zwave-js.io/?jumpTo=0x0271:0x0001:0x1a73:0.0
History;
Device information
https://devices.zwave-js.io/?jumpTo=0x0271:0x0002:0x1a72:0.0
and
https://devices.zwave-js.io/?jumpTo=0x0271:0x0001:0x1a73:0.0
How are you using
node-zwave-js
?zwavejs2mqtt
Docker image (latest)zwavejs2mqtt
Docker image (dev)zwavejs2mqtt
Docker manually built (please specify branches)ioBroker.zwave2
adapter (please specify version)HomeAssistant zwave_js
integration (please specify version)pkg
node-red-contrib-zwave-js
(please specify version, double click node to find out)Which branches or versions?
zwave_js addon: 0.1.51
Did you change anything?
yes (please describe)
If yes, what did you change?
Updated to latest available brach
Did this work before?
Yes (please describe)
If yes, where did it work?
Device got added correctly in previous branch ( +/- 2 yrs ago)
Attach Driver Logfile
Initial symptoms previous version
Additional information
Additional information; current version of the addon
The text was updated successfully, but these errors were encountered: