Migration from zwave.me UZB to HA ZWA-2

Configuration Z-Wave
1

Today I received the ZWA-2 and of course happily started a migration…

About an hour ago! :wink:

Something does not compute here.

afbeelding
afbeelding1438×795 76.5 KB

Looking at this pic for the whole hour.
Afraid to cancel, don’t want to brick something…

  • Installation method Home Assistant OS

  • Core 2025.8.2

  • Supervisor 2025.08.1

  • Operating System 16.1

  • Frontend 20250811.0

  • Z-Wave JS addon 0.21.0

  • Driverversion: 15.11.0

  • Serverversio : 3.2.1

  • Dongle: ZWAVE.me UZB

  • firmware 5.39 (SDK: 6.82.01)

According to the migration instructions this should work out of the box…

Need help, guys :wink:

2

You would have to look at the driver debug logs to see what is going on. Not sure what is actually visible w/o debug enabled, but you could check the add-on logs for something.

1 Like
3 
Code 1000: 
2025-08-16 00:50:30.790 CNTRLR   Backing up NVM...
2025-08-16 00:50:30.790 CNTRLR   Turning RF off...
Z-Wave error ZWaveError: Could not turn off the Z-Wave radio before creating NVM backup! (ZW0203)
    at ZWaveController.backupNVMRaw (file:///usr/src/node_modules/zwave-js/src/lib/controller/Controller.ts:8401:10)
    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: 203,
  context: undefined,
  transactionSource: undefined
4

First off, either Z-Wave JS is not throwing an error that HA can handle, or HA is just not handling the error. Based on some recent changes, I’d guess the former but I don’t know for sure. The unhandled error is the reason for the hang.

There there’s the question of why the radio can’t be turned off. Not sure if that’s a Z-wave.me problem or not.

I’d submit an issue to the home-assistant GitHub project and they can sort it out.

1 Like
5

Do you think it’s safe to cancel for the time being?
Have a direct link to where to submit the issue?

And again, thanks for yours, as always, super fast helping hand :wink:

6

I think you can just cancel it, it never even attempted a backup. For reproduction purposes I would turn on driver debug logging and just do a manual backup. The driver debug logs are going to be needed to troubleshoot anything.

If you want to submit an HA issue: https://github.com/home-assistant/core/issues/new?template=bug_report.yml, they will help triage the problem.

And/or if you want to submit a Z-Wave JS issue (e.g. the radio toggle failure itself has nothing to do with HA): https://github.com/zwave-js/zwave-js/discussions/new?category=request-support-investigate-issue

In either case, having those driver level debug logs will be needed.

1 Like
7

thank you, tomorrow I will do, now it’s time to jump in bed :smiley:

8

For good measure, you might also try unplugging and re-plugging the USB stick. Maybe it got in a bad state and needs a power-cycle (rebooting the host won’t do this). As this person seemed to experience in the past: https://github.com/zwave-js/zwave-js/issues/3904#issuecomment-995271019

2 Likes
9

Waked up, tapped a good cappuccino, pulled the old stick for 10 seconds, sticked it back, started the migration, took 2 sips of the coffee, migration complete.

You made my day again, @freshcoast :wink:

1 Like