[fw 7.17.2] Cannot heal any node

darkbasic 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

Fw 7.17.1/7.17.2 seemed to fix my network issues for a while, but after replacing some dead nodes (and all the battery powered ones) I've done a full heal and the same old pre 7.17.1 issues are back once again. One of the nodes has been marked as dead right after being successfully healed and now I cannot heal any node period.

This is what I got in the zwavejs2mqtt logs:

2022-05-04 11:49:49.630 INFO ZWAVE: Calling api healNode with args: [ 84, [length]: 1 ]
2022-05-04 11:49:49.639 INFO ZWAVE: Success zwave api call healNode false

but nothing is shown in the zwavejs ones, despite having debug logs enabled.

I'll attach zwavejs2mqtt and zwavejs debug logs of yesterday (when I started removing/adding some nodes) and today (when the "cannot heal" issue appeared).

Linked issue: https://github.com/zwave-js/node-zwave-js/issues/3906

Device information

Manufacturer: Aeotec Model name: Z-Pi 7

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)
[X] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?

zwavejs2mqtt: 6.7.1.2a08abd zwave-js: 9.0.2 home id: 3578308563 home hex: 0xd548a7d3

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?

fw 7.17.1/7.17.2 used to fix it for a while, but today I've replaced some dead nodes, removed the battery powered ones and did a network heal. Same old pre-7.17.1 issues happen again now.

Attach Driver Logfile

zwavejs2mqtt_2022-05-04.log zwavejs2mqtt_2022-05-03.log.gz zwavejs_2022-05-04.log zwavejs_2022-05-03.log.gz

blhoward2 commented 2 years ago

Your title says can't heal any nodes, but as you describe it appears they all healed except the last one, correct?

You also say "the same" issues as before, but you only describe one issue that some experienced whereas the 700 fw issues resulted in a constellation of problems. Please confirm the issues you are experiencing.

The Z-Pi 7 works a little differently than the sticks. Have you tried restarting the host? They are particularly susceptible to power fluctuations.

darkbasic commented 2 years ago

Your title says can't heal any nodes, but as you describe it appears they all healed except the last one, correct?

Nope, they all healed including the last one, but after doing so one node has been marked as dead and I have not been able to heal any node from that moment.

I've debugged this with Al Calzone on Slack and it appears like this might be due to the controller being stuck in a never ending heal, possibly because I've tried to heal a node marked as dead without pinging it first. I'm testing a PR with additional debugging logic right now.

darkbasic commented 2 years ago

I still didn't manage to reproduce the original issue w/ https://github.com/zwave-js/node-zwave-js/pull/4567 I'll keep an eye on this and let you know.

AlCalzone commented 3 weeks ago

There have been quite a few changes, both in terms of Z-Wave SDK/Firmware, and handling of route rebuilding (formerly called healing). If this is still an issue, please open a new one with updated information.

zwave-js / node-zwave-js