node-zwave-js: Network Breaks Nightly Until Zwave-JS Restart Since Friday
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?
YES, BUT a ZWaveJS2MQTT developer has told me to come here
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
What causes the bug? Every evening (sunset - 4AM approx), automations fail to execute and Zwave devices become unavailable
What do you observe? Unable to control/manage nodes. Early testing appears that if I restart the zwavejs2mqtt container, nodes become available again, but network healing is unstable. What did you expect to happen? Stable behavior. When restarting the container and initiating a heal, the heal rate is ~50%.
I am attaching log archives going back to Friday when the behavior began (can’t remember if Silly was enabled that far back, but I turned Silly on shortly thereafter over the weekend. Todays 2021-12-01.log**.old** is before I restarted the container this morning and began troubleshooting, so it should contain information on the network “crash”.
The 2021-12-01.log is a fresh log starting with a container startup, network graph view, followed by a network heal (~50% success on the heal), then me shutting down the container.
I’ve also attached my Zooz controller’s NVM backup along with my homeid.json
Device information
All devices
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) - Manually built from GitHub (please specify branch)
- Other (please describe)
Which branches or versions?
zwavejs2mqtt: 6.0.2 zwave-js: 8.8.2 home id: 3745883352 home hex: 0xdf45a4d8
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?
Prior to Friday all automations and control worked as expected.
Attach Driver Logfile
zwavejs_2021-11-30.log.gz zwavejs_2021-11-29.log.gz zwavejs_2021-11-28.log.gz zwavejs_2021-11-27.log.gz zwavejs_2021-12-01.log zwavejs_2021-12-01.old.log df45a4d8.json.txt NVM_2021-12-01.bin.txt
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 21 (7 by maintainers)
Guys please… No stories, post logs 🙏
@Eriner - my response to your issue indicating my stick was showing neighbors (yours wasn’t, as I understood?) was shortly after doing myriad of things to get random nodes reconnected like you. Not all of my nodes were responsive, but most. I guess I can’t be 100% certain my stick shows neighbors when the network goes haywire, but another data point to check if downgrading to 5.12.0 is an issue.
I can say that I have had weeks worth of success at a time with the Zooz stick, so hopefully all is not lost. To be continued…
Yes, restarting zwavejs