Firmware upgrade fails with timeout after second device of the same kind/firmware, restart needed to upgrade second device

[ocalvo]

Checklist

• I have read and followed the above instructions

• 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 or the fix did not work.

Describe the issue

What is happening?

I have 12 sensors that need to be upgrade it on a network with 125 nodes.
The sensors that are close of the central node can upgrade, but far away nodes fail with timeout.

What did you expect to happen instead?

After upgrading one Multi sensor the second attempt fails with timeout.

Steps to reproduce the behavior:

1. Start upgrade on the Attic Sensor (the furthest)
2. Wait
3. At about some random percentage, 15%, 20%, 30%, the upgrade fail.

If the Zwave-JS addon is restarted, then upgrading the next Multisensor works fine.
It seems that something need to be reseted correctly for multiple upgrades of the same device kind works.

I have confirmed that I can upgrade a door sensor and then a multisensor. But the 3rd multisensor also fails with timeout.

2024-12-28T19:53:29.447Z CNTRLR   [Node 126] Firmware update timed out
2024-12-28T19:53:29.450Z CNTRLR « [Node 126] Firmware update (part 1 / 1) failed with status Error_Timeout
2024-12-28 13:53:29.454 INFO Z-WAVE: [Node 126] Firmware update finished with error.
   Status: Error_Timeout.
   Wait before interacting: No.
   Result: {"success":false,"status":-1,"reInterview":false}.

Anything else we should know?

Software versions

zwave-js-ui: 9.27.8
zwave-js: 14.3.7
home id: 3452859137
home hex: 0xcdce7301

Home Assistant Z-Wave Integration: 3.18

Home Assistant Z-Wave JS Addon: 3.18

ioBroker.zwave2 Adapter: ?

If you are using something non-standard, tell us here: ...

Z-Wave Controller (Stick/Dongle/...)

discussions

Device information

Manufacturer: Aeotec
Model name: Multisensor 7
Node ID: 126

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

No response

[zwave-js-bot]

👋 Hey @ocalvo!

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 on loglevel debug is required to diagnose most issues.

Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one:

• Z-Wave JS UI
• Home Assistant Z-Wave Integration
• ioBroker.zwave2 Adapter