[X] I have read the changelog and my problem was not mentioned there.
Describe the bug
When I attempt to include the locks (through zwavejs2mqtt or zwavejs) they fail to interview completely, leaving parameters missing or values as undefined, including the User Code section (see image below).
Looking at the logs shows many Timed out while waiting for a response from the node (ZW0201) errors throughout. Moving the lock within inches of the stick doesn't seem to make a difference.
Attempts to Re-Interview the device result in a loss of nearly all to all the information previously interviewed. Similar to (#1517).
Device information
Manufacturer: Schlage/Allegion
Model name: BE469ZP
Node ID in your network: 28
(I have 2 of these locks, both have the same issue. One is brand new. One is firmware version 11.0 and the other is version 10.4. Both devices behave the same way.)
Aeotec Z-Stick Gen 5 Plus (ZW090)
How are you using node-zwave-js?
[X] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)
Which branches or versions?
version:
zwavejs2mqtt: 6.15.2
zwave-js: 9.6.2
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
This lock worked at a previous house but started developing issues after moving to a new house. It was excluded then began having issues when I tried to include it again. I was using zwavejs and was having issues there before moving to zwavejs2mqtt and experiencing the same issues.
AlCalzone
commented
2 years ago
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem was not mentioned there.
Describe the bug
When I attempt to include the locks (through zwavejs2mqtt or zwavejs) they fail to interview completely, leaving parameters missing or values as undefined, including the User Code section (see image below).
Looking at the logs shows many
Timed out while waiting for a response from the node (ZW0201)errors throughout. Moving the lock within inches of the stick doesn't seem to make a difference.Attempts to Re-Interview the device result in a loss of nearly all to all the information previously interviewed. Similar to (#1517).
Device information
Manufacturer: Schlage/Allegion Model name: BE469ZP Node ID in your network: 28
(I have 2 of these locks, both have the same issue. One is brand new. One is firmware version 11.0 and the other is version 10.4. Both devices behave the same way.)
Aeotec Z-Stick Gen 5 Plus (ZW090)
How are you using
node-zwave-js?zwavejs2mqttDocker image (latest)zwavejs2mqttDocker image (dev)zwavejs2mqttDocker manually built (please specify branches)ioBroker.zwave2adapter (please specify version)HomeAssistant zwave_jsintegration (please specify version)pkgnode-red-contrib-zwave-js(please specify version, double click node to find out)Which branches or versions?
version: zwavejs2mqtt: 6.15.2 zwave-js: 9.6.2
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?
This lock worked at a previous house but started developing issues after moving to a new house. It was excluded then began having issues when I tried to include it again. I was using zwavejs and was having issues there before moving to zwavejs2mqtt and experiencing the same issues.
Attach Driver Logfile
zwavejs_2022-08-17.log