NVM Backup fails

sender · August 10, 2025, 7:24pm

Using the new backup in zwavejs I get:

2025-08-10 21:17:07.589 CNTRLR Backing up NVM…
2025-08-10 21:17:07.589 CNTRLR Turning RF off…
2025-08-10 21:17:07.597 CNTRLR Stopping hardware watchdog…
2025-08-10 21:17:09.237 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:09.238 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:09.239 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:09.245 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:09.246 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:09.248 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:09.249 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:09.262 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:17.627 CNTRLR Turning RF on…
Z-Wave error ZWaveError: Timeout while waiting for a response from the controller (ZW0200)
at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7057:23)
at ZWaveController.externalNVMReadBuffer (file:///usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:8013:33)
at ZWaveController.backupNVMRaw500 (file:///usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:8376:29)
at ZWaveController.backupNVMRaw (file:///usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:8344:11)
at ControllerMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/controller/message_handler.js:164:36)
at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:62) {
code: 200,
context: ‘response’,
transactionSource: ’ at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7057:23)\n’ +
’ at ZWaveController.externalNVMReadBuffer (file:///usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:8013:33)\n’ +
’ at ZWaveController.backupNVMRaw500 (file:///usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:8376:29)\n’ +
’ at ZWaveController.backupNVMRaw (file:///usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:8344:11)\n’ +
’ at ControllerMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/controller/message_handler.js:164:36)\n’ +
’ at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:62)’
}
2025-08-10 21:17:28.835 CNTRLR Backing up NVM…
2025-08-10 21:17:28.835 CNTRLR Turning RF off…
2025-08-10 21:17:28.841 CNTRLR Stopping hardware watchdog…
2025-08-10 21:17:30.466 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:30.467 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:30.475 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:32.306 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:32.306 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:32.340 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:32.347 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:32.361 DRIVER unexpected response, discarding…
2025-08-10 21:17:33.932 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:33.940 DRIVER no handlers registered!
2025-08-10 21:17:33.947 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:38.936 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:38.942 DRIVER Dropping message because it contains invalid data
2025-08-10 21:17:45.729 CNTRLR Turning RF on…
2025-08-10 21:17:50.532 DRIVER Attempting to recover unresponsive controller by reopening the serial port…
2025-08-10 21:17:51.796 DRIVER Serial port reopened. Returning to normal operation and hoping for the best…
2025-08-10 21:18:02.317 CNTRLR « [Node 104] received wakeup notification
2025-08-10 21:18:02.317 CNTRLR [Node 104] The node is now awake.
2025-08-10 21:18:02.567 CNTRLR » [Node 104] Sending node back to sleep…
2025-08-10 21:18:02.591 CNTRLR [Node 104] The node is now asleep.
2025-08-10 21:20:23.037 CNTRLR Backing up NVM…
2025-08-10 21:20:23.037 CNTRLR Turning RF off…
2025-08-10 21:20:23.044 CNTRLR Stopping hardware watchdog…
2025-08-10 21:20:24.673 DRIVER Dropping message because it contains invalid data
2025-08-10 21:20:33.054 CNTRLR Turning RF on…
2025-08-10 21:20:36.252 DRIVER Dropping message because it contains invalid data
2025-08-10 21:20:37.855 DRIVER Attempting to recover unresponsive controller by reopening the serial port…
2025-08-10 21:20:39.108 DRIVER Serial port reopened. Returning to normal operation and hoping for the best…
2025-08-10 21:20:53.180 CNTRLR [Node 060] treating BasicCC::Set as a report
2025-08-10 21:20:53.234 CNTRLR [Node 060] treating BasicCC::Set as a report

it does not backup… Whats wrong?

freshcoast · August 10, 2025, 7:50pm

Which controller? What SDK version? You’ll need to turn on debug logs to learn more.

sender · August 10, 2025, 8:13pm

The Debug Log:
dpaste/scaPp (Python)

wmaker · August 11, 2025, 7:07pm

I thought this version would work but searching around it appears to be a known problem with a fix coming:

github.com/zwave-js/zwave-js

Cannot Backup NVM on Z-Stick Gen5 USB Controller v1.2

opened 12:51PM - 11 Aug 25 UTC

closed 12:55PM - 11 Aug 25 UTC

AlCalzone

### Discussed in https://github.com/zwave-js/zwave-js/discussions/8045 <div typ…e='discussions-op-text'> <sup>Originally posted by **sanderlv** August 10, 2025</sup> ### Checklist - [X] I have read and followed the above instructions - [X] I have checked the [troubleshooting section](https://zwave-js.github.io/zwave-js/#/troubleshooting/index) and my problem is **not** described there. - [X] I have read the [changelog](https://github.com/zwave-js/zwave-js/blob/master/CHANGELOG.md) and my problem was **not** mentioned there or the fix **did not work**. ### Describe the issue What is happening? Using the new backup in zwavejs I get not backup. <img width="828" height="1215" alt="image" src="https://github.com/user-attachments/assets/f8a73065-583d-4df2-a6e9-08c5bf583f86" /> What did you expect to happen instead? Succesfulll backup Anything else we should know? ### Software versions Driver version: 15.10.0 Server version: 3.2.1 Home ID: 3677275745 Server URL: ws://core-zwave-js:3000 ### Z-Wave Controller (Stick/Dongle/...) Z-Stick Gen5 USB Controller v1.2 ### Device information Z-Stick Gen5 USB Controller v1.2 node id 1 ### Checklist - [X] I [made sure](https://zwave-js.github.io/zwave-js/#/troubleshooting/index?id=rule-1-use-the-driver-log-luke) 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 [message.txt](https://github.com/user-attachments/files/21707474/message.txt) </div>

sender · August 11, 2025, 8:01pm

Correct, I opened that request.

kartcon · August 12, 2025, 12:07am

Where can I find info on the “new backup”? I noticed today that my usual way of opening the store folder and right clicking no longer shows a download icon! What to do in the mean time??