NVM backup creates 0-length file

[YogoGit]

Checklist

• I am not using Home Assistant. Or: a developer has told me to come here.
• I have checked the troubleshooting section and my problem is not described there.
• I have read the changelog and my problem is not mentioned there.

Deploy method

Docker

Z-Wave JS UI version

9.24.0

ZwaveJS version

13.9.1 (from release notes)

Describe the bug

Choosing Advanced Action -> NVM Management ->Backup. The generated file (just ran, it's NVM_20241119192140.bin) is empty (0 length), both on the system and the downloaded file.

Environment/Setup:
OS - Ubuntu 22.04 (x86)
Docker image: zwavejs/zwave-js-ui:9.24.0

USB Zwave Stick: Zooz ZST39 800LR (firmware v1.10/SDK 7.18.3) - Been running for ~12 months w/out issue

The environment seems correct, but I believe I may need to update the firmware, and I want/need a NVM backup prior to doing so.

To Reproduce

Click on the backup backup, expect to see a non-zero .bin file.

Expected behavior

A file containing something.

Additional context

Logfile contents:

2024-11-18T19:21:36.999Z CNTRLR   Backing up NVM...
2024-11-18T19:21:37.000Z CNTRLR   Turning RF off...
2024-11-18T19:21:37.013Z CNTRLR   Stopping hardware watchdog...
2024-11-18T19:21:37.050Z CNTRLR   Performing soft reset...
2024-11-18T19:21:37.064Z CNTRLR   Enabling Smart Start listening mode...
2024-11-18T19:21:37.067Z CNTRLR   Waiting for the controller to reconnect...
2024-11-18T19:21:38.074Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2024-11-18T19:21:38.286Z CNTRLR   reconnected and restarted
2024-11-18T19:21:38.288Z CNTRLR   Starting hardware watchdog...
2024-11-18T19:21:38.291Z CNTRLR   Switching serial API to 16-bit node IDs...
2024-11-18T19:21:38.296Z CNTRLR   NVM backup completed
2024-11-18T19:21:38.297Z CNTRLR   Turning RF on...
2024-11-18T19:21:39.179Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2024-11-18T19:21:40.284Z CNTRLR   Smart Start listening mode enabled
2024-11-18T19:21:40.292Z CNTRLR   Switching to 16-bit node IDs successful

Note, the weird wrapping issue is in the logfile (next try i\nn 100ms.)

[YogoGit]

Different result, but still with a 0-length file.

2024-11-18T19:58:13.062Z CNTRLR   Backing up NVM...
2024-11-18T19:58:13.063Z CNTRLR   Turning RF off...
2024-11-18T19:58:13.078Z CNTRLR   Stopping hardware watchdog...
2024-11-18T19:58:13.099Z CNTRLR   Performing soft reset...
2024-11-18T19:58:13.104Z CNTRLR   Waiting for the controller to reconnect...
2024-11-18T19:58:14.330Z CNTRLR   reconnected and restarted
2024-11-18T19:58:14.331Z CNTRLR   Starting hardware watchdog...
2024-11-18T19:58:14.332Z CNTRLR   Switching serial API to 16-bit node IDs...
2024-11-18T19:58:14.334Z CNTRLR   NVM backup completed
2024-11-18T19:58:14.335Z CNTRLR   Turning RF on...
2024-11-18T19:58:14.343Z CNTRLR   Switching to 16-bit node IDs successful

-rw-r--r-- 1 root root 0 Nov 18 12:58 NVM_20241118195814.bin

[kpine]

NVM backup on 800-series controllers requires SDK v7.19.0 or higher.

zwave-js/node-zwave-js#5257

[YogoGit]

Is there a way to backup the device to avoid losing data when I do the upgrade to a newer version of the firmware? (ie; how do I avoid a catastrophic loss if the firmware upgrade failed?)

Thanks!