Take over network from existing controller

zwave-js / node-zwave-js

Z-Wave driver written entirely in JavaScript/TypeScript

https://zwave-js.github.io/node-zwave-js/

MIT License

741 stars 594 forks source link

Take over network from existing controller #7096

Open AlCalzone opened 1 month ago

AlCalzone commented 1 month ago

To make migration from legacy controllers easier, especially when NVM backup/restore is not an option, consider the following flow:

Start learn mode, join existing network. As part of this, existing nodes' info is transferred to Z-Wave JS
Ask user to turn off existing controller
Read NVM, modify NVM to set own node ID to the node ID of the previous SUC
Write modified NVM
Restart to apply modified NVM
Maybe (investigate?): Change own role to SUC/SIS

TomMalfrere commented 1 month ago

I'm following... I have the following setup

Raspberri Pi 3B+ rev1.3
Raspian Bullseye 32bit OS
AEOTEC Gen5 ZW090 USB controller
z-wave-js UI in a docker
MQTT (mosquitto) in a docker
Domoticz (not in a docker)

I'm have issues lately with my AEOTEC Gen5 ZW090 USB-stick that becomes unresponsive after 2-3 days. A reboot (ZWave stick remains powered and plugin) fixes the problem.

I would like to move to

Raspberri Pi 3B+ rev1.4
Raspian Bookworn 64bit OS
RAZBerry
z-wave-js UI in a docker
MQTT (mosquitto) in a docker
Domoticz (in a docker)

How can I replace the Z-Wave controller in my network but make sure my devices are reported the same in MQTT ? This is a live system with 41 z-wave devices.

AlCalzone commented 1 month ago

If your Z-Stick is on firmware 1.2 you can just take an NVM backup and restore that on a new controller using Z-Wave JS UI.

TomMalfrere commented 1 month ago

If your Z-Stick is on firmware 1.2 you can just take an NVM backup and restore that on a new controller using Z-Wave JS UI.

"productLabel": "ZW090", "productDescription": "Z‐Stick Gen5 USB Controller", "manufacturer": "AEON Labs", "firmwareVersion": "1.0", "sdkVersion": "6.51.2", "protocolVersion": 3,

AlCalzone commented 1 month ago

It's possible that you can upgrade with the firmware updater from Aeotec (search for Z-Stick 5 firmware 1.2).

If not then this feature would be for you.

TomMalfrere commented 3 weeks ago

I tried updating the firmware this weekend. It did not work. It appears my stick is running since september 2017 so it was likely manufactured before 2018...

I just read : https://github.com/zwave-js/node-zwave-js/issues/6341 which affects me also. I went for option 6... I'm running for a few days now without a reboot... (normally every 2-3days)