node-zwave-js: Nodes recently becoming unavailable repeatedly
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
For a while now, although I am not sure since what zwavejs version update, I am finding some of my nodes unavailable. This presumably happens after interacting with them. I’m not completely sure since 99% of the interactions go through automations and I am having trouble replicating this behavior manually. For this reason I’m not able to provide accurate logs at this time. I’ve enabled the logging to file and will upload these logs the moment I find another node unavailable.
I have been using this exact setup for a couple of years and have never had any issues with it. It seems to me that the zwavejs driver is perhaps a little bit more “aggressive” in marking a node as unavailable in case a packet isn’t received on time. The only way for me to get the node back online is to re-interview it twice.
I realize this is not a lot of information to go on but I was wondering whether this seems like familiar behavior to anyone and if yes what the recommended course of action would be?
Device information
Manufacturer: Aeotec Model name: Z-Stick Gen5 ZW090 / FW1.2 Node ID in your network: Multiple
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: 12.0.0 / HA Addon ZwaveJS2MQTT
zwave-js-ui branch: 9.0.1 / HA Addon ZwaveJS2MQTT
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?
No response
Attach Driver Logfile
will provide later
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Comments: 30 (10 by maintainers)
Looking at that graph, I’m inclined to say the position of your controller may still not be ideal. Most of the nodes are not connected with 100 kbit/s. If changing the location does not help, you may want to look into setting priority routes. Those are routes that are always attempted first when sending a command to a device. It makes the most sense when forcing a direct connection at high speed. You can do that on the network map, select a node where you are relatively sure it should have a direct connection, select no repeaters and 100 kbit/s speed, then save the priority route and ping the device to confirm. If that helps, it may indirectly help your further-away devices too.
Honestly, I’d currently not upgrade. The 700 series is a shitshow, especially in Europe, and upgrading to 800 series requires you to unpair and re-pair all your devices, at least for now.
I can confirm that this is working with my 500 series controller.
Ok that last one is a firmware bug in the stick that has gotten unnoticed until very recently --> https://github.com/zwave-js/node-zwave-js/issues/6363 Seems to be related to your other log snippets though, so maybe that’s it already.