Node-red-contrib-zwave-js transfer question

[magicman]

Hi,

i have a P400 with node red installed and use the zwave.js node to control all of my z wave devices which it does very well.
My question is I wish to set up another P400 for z wave control at the same location can i import the device numbers/names/locations from zwave.js of the existing z wave devices or do i have to add them all again?
I am using a aeotech stick on both P400 as a z wave controller.

Hopefully someone can help me with this?

Thank you in advance

[marcus-j-davies]

Hi @magicman

Do you mean, you want to move your devices to another stick?

[magicman]

yes but also keep the other stick active when using the P400 it is on

[rakgupta]

@magicman

yes but also keep the other stick active

If my understanding of Z-wave devices is correct (I use a different hub), a device can only be paired with one "controller" at a time. At least on my hub, if I need to add it to a different controller, I have to exclude it and then include it.

[marcus-j-davies]

ZWave has Slave/Master support.

2 controllers, CAN control the same network, but the devices in that network, will only have its LifeLine Node ID set to 1 controller - meaning only 1 Node RED instance, will know of any updates.

Its pretty messy.

currently, I don't think ZWave JS supports Slave/Master - or is at least, unsupported

You can only move the entire network to a different controller, via NVM backup/restore
this is supported in my module - but it doesn't allow 2 controllers, to take control - only move management to a new controller (until Salve/Master is supported in ZWave JS)

[magicman]

thanks for your reply @marcus-j-davies i only want to run one p400 and node red instance at once not together. I just want to know how to get the device information etc from one stick to the other?

[marcus-j-davies]

OK - I got to do a few things, then will document the process for you.
its an involved process - to ensure the same network data is moved

[magicman]

omg ty for your time

[marcus-j-davies]

@magicman

Are you running series 500 stick(s)?

It can migrate from 500, to series 700, if that is what you are doing.

[magicman]

they are Gen 5 marcus

[marcus-j-davies]

Ok..

Follow this to the letter.

1. Make sure both sticks are on the same Firmware version (Aeotec I think provide firmware update tools) - I have not yet implemented FW updating for controllers (I'm working on it)

2. Back up your security keys (in the Controller Node)
   If you lose them - you got to reset all your devices and re-interview

3. Update to the latest module version (I released a patch shortly ago) - v9.1.1

4. Backup your NVM (Transceiver Settings)
   After you have the file - go here : Z-Wave JS: Online NVM editor
   and upload the file, to make sure it can read the file correctly.

   You are not doing anything, its just to make sure - its a clean backup

5. At this point, gracefully stop Node RED (both)

6. Copy this folder (from old)
   ~/.node-red/zwave-js-cache

7. Place this folder, on the new system (same place) - replace if necessary
   ~/.node-red/zwave-js-cache - once placed on new system, start it up

8. Making sure the new stick is factory reset, insert into the new system.
   when it comes to configuring the controller - use the security keys you backed up.

9. Allow the controller to become ready (you will of course see no network devices)

10. Restore the NVM you backed up (Transceiver Settings)
    

    

after about a minute the controller will restart, refresh Node RED web UI - and your devices (should) be in there, and this new controller will have control.

DONT have both controllers on line - you will microwave your network in doing so.

Transceiver Settings

Good luck

[magicman]

1. Back up your security keys (in the Controller Node)
   2.If you lose them - you got to reset all your devices and re-interview*

Are these the encryption keys @marcus-j-davies ?

[marcus-j-davies]

Hi @magicman - that is correct.

[magicman]

thank you @marcus-j-davies will attempt the above procedure tonight . thank you again for your help