OTA Firmware update causes driver to become unresponsive

[robarnold]

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

Performing a firmware update on a node causes the driver to become unresponsive - I can no longer ping nodes or operate other devices on the network. Logs seem to show repeated failures to send. Workaround is to restart the container - ZUI/the driver refuse to soft reset during a firmware update.

Device information

Manufacturer: Aeotec
Model name: ZWA037
Node ID in your network: 64

How are you using node-zwave-js?

• zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
• zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
• zwave-js-ui (formerly 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:
Home Assistant branch: latest
zwave-js-ui branch: 8.25.1 (latest)

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?

This version has worked with some but not all of this brand of device on my network. I haven't figured out a common pattern other than a general trend of "distance" - further away nodes tend to be more fickle. I think the fixes with #6260 helped with some of the devices I was trying to update (same models) but not all of them. This makes me think it's some kind of software/robustness issue somewhere in the zwave stack.

Attach Driver Logfile

https://gist.github.com/robarnold/db6ed6a4dcd977b8816ccabe9eb16dfd

[zwave-js-bot]

👋 Hey @robarnold!

Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log is required to diagnose most issues.

Please consider uploading a logfile that captures your problem.

[AlCalzone]

Seems to be another duplicate of #6260, again on firmware 7.19.3.
We may have to consider that version broken.