node-zwave-js: [Investigate 700 Bug] Nodes being marked dead; may be specific to Inovelli LZW31 devices
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
-
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 upgraded my Aeotec Z-Stick 7 yesterday. This morning, I noticed one of my automations did not trigger a light switch as it should have (a ZEN32). The logs indicate that a LZW31 device had a sudden burst of traffic and then the ZEN32 device was marked dead.
The death of node 85 (ZEN32) with 10 minutes for context: dead_node_85.log
The full activity of node 42 (LZW31) in that log file: node_42.log
Per the recommendation of @blhoward2, I ran a network heal. That was mostly successful with 68/69 nodes healing successfully. One did not heal - that was a different LZW31 (node 55): node_55.log
Another LZW31 was marked dead. node_31.log
I have 9 LZW31 devices (out of 69 total Zwave nodes). All are running firmware 1.57.
Device information
Manufacturer: Inovelli Model name: LZW31 Node ID in your network: 31, 42, 55
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?
version:
node-zwave-js
branch: master (8.11.1)
zwavejs2mqtt
branch: master (6.4.1)
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 problems on the Aeotec Z-Stick 5+ for the last couple of months.
Attach Driver Logfile
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 39 (26 by maintainers)
It’s been a little bit since I’ve seen a node die unexpectedly. I’m going to go ahead and close this and I’ll reopen with trace data if it recurs.
We’ve flirted with if there was a way to put the stick in promiscuous mode (like a zniffer but your network only, doesn’t require new fw)
It does for my reference UZB3 from SiLabs too