node-zwave-js: More interview timeouts with Schalge Connect Lock (BE469)
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 Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
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
I’m having problems with my Schalge Connect (BE469) Zwave (non-plus) lock. It’s worked well for the most part for multiple years and I’ve always been able to get it back up and going when things go south. This time is different, I can’t seem to get it to interview with the correct data. For example, there’s almost nothing there when I look at the User Codes section.
I just tried setting the timeout parameter higher as per https://github.com/zwave-js/node-zwave-js/issues/4746, but that didn’t help. In fact, it seemed to act exactly the same, which means either I did it wrong or it isn’t a timeout issue. I’ve attached the driver logs to this issue.
Device information
Schalge BE469 Node 17.
How are you using node-zwave-js?
-
zwave-js-ui(formerlyzwavejs2mqtt) Docker image (latest) -
zwave-js-ui(formerlyzwavejs2mqtt) Docker image (dev) -
zwave-js-ui(formerlyzwavejs2mqtt) Docker manually built (please specify branches) -
ioBroker.zwave2adapter (please specify version) -
HomeAssistant zwave_jsintegration (please specify version) -
pkg -
node-red-contrib-zwave-js(please specify version, double click node to find out) - Manually built from GitHub (please specify branch)
- Other (please describe)
Which branches or versions?
version:
node-zwave-js branch:
zwave-js-ui branch:
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?
Worked just fine until I started trying to reinterview it tonight… Not sure when things stopped working exactly.
Attach Driver Logfile
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (6 by maintainers)
I’d like to report that issue seems to be resolved, at least it is for me. Approximately 1 month ago, an attempt to add my lock failed much like as described in this issue. I don’t have a record of what version I was running at that time. A few days ago I upgraded my zwave js ui installation to latest. This put me at z-wave js ui 8.8.5 and z-wave js 10.10.0. This afternoon I again attempted to include my lock and was successful. The interview completed successfully and 6 hours later the lock node still active and functional.