Create Secondary Controller

[juwi_uk 3]

Hi I'm a new HC2 user (received unit today) battling to setup with what it seems is very little documentation to help;  i'm getting there but I guess a world of pain still ahead if I head some of the other posts.

 

Can someone point me in the right direction on how to pass info from HC2 so that I can create a secondary controller with my old unit (that used to be the primary unit before HC2 turned up).

 

I know how to put my remote in learn mode BUT the bit I'm struggling with is how to SEND the config from HC2.  Seemed a lot  more intuitive on Primary Controllers I've used before.

 

These options on the "Z-Wave Network" seem my only choices but neither looks to be what I need to send the config to the secondary.

 

1.  "Add Secondary Controller"
2. "Controller Transfer" 
3. "Broadcasts Node Information Frame"

I did try one of the above in my tests and ended up making my HC2 a secondary for a scary moment (and scary it was when a new user 1hour out of the box!)!! 

 

Any help much appreciated.

 

Regard

 

Julian

 

 

[piters 0]

Hi there,

 

same question here: what is the difference between "Add Secondary" and "Controller Transfer" and what is their aim?

Could anyone give a step-by-step explanation on how we could use FGHC2 as primary plus a number of remote controls as secondaries, and use these remote controls for inclusion/exclusion?

Is FGHC2 (firmware 4.0.42) acting as SUC/SIS or could it be made to act as one? (this, as I seem to have seen somewhere) would allow to delegate inclusion/exclusion...

 

thanks in advance for any help,

 

cheers,

 Piotr

[j.nowacki 5]

So far only the connection between multiple HC controllers over LAN is available, mentioned secondary controller feature is not fully functional yet. Eventually it will allow to connect some other devices over Z-wave network to provide some redundancy.

[elev8john 0]

Is the secondary controller functionality available as yet please? If so what devices have people tested it with?

[RiccardoCanetta 13]

Hi

if the goal is to have a second box in case the primary fails (i.e. cold standby), I have done the following:

- upgraded both HC2 to same release

- backup of primary HC2

- shutdown

- copied the backup just done from one  USB stick to the other, using a Mac

- powered up the new HC2

- created a new backup of the empty config of the new box

- the "transferred" backup appears in the available backups list

- restore of the backup

 

Now I am running all the existing config on a new box

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

 

Hope it helps

Riccardo

[j.nowacki 5]

Hi

if the goal is to have a second box in case the primary fails (i.e. cold standby), I have done the following:

- upgraded both HC2 to same release

- backup of primary HC2

- shutdown

- copied the backup just done from one  USB stick to the other, using a Mac

- powered up the new HC2

- created a new backup of the empty config of the new box

- the "transferred" backup appears in the available backups list

- restore of the backup

 

Now I am running all the existing config on a new box

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)">

 

Hope it helps

Riccardo

 

Such activity might have voided your warranty, since you should not interfere with usb memory as it is integral part of hardware. Things you have done might influence behaviour of controller e.g. in remote access.

 

As for the secondary controller, I will post my reply from other thread in that topic:

 

This is mechanism of adding secondary controller as Z-wave describes it: you can send node ids etc to another controller, but configuration of devices, device they report to etc will stay the same. It is not transfer of everything: scenes, virtual devices etc will not be visible on secondary controller. So in your situation: you will be able to see Z-wave devices from old controller on new one, but to make them fully work you would need to reconfigure every one of them, change their associations to make them report to new controller and recreate all other devices.  And even then there are some devices that will keep try to communicate id 1 (so old controller) and there will be no other way than re-inclusion to make them work. This is how Z-wave enforces implementation of this function on z-wave certificated devices.