forum

Hi,

Been running my zstick for sometime now and completed code changes to allow for multiple z-way-server instances.

So I let my system detect the RaZberry and I had my main controller on port 8183 and the new on port 8283.

I was hoping to migrate over so that the RaZberry was primary, so first I tried including the new controller into the existing controller network.

I then did the change controller function which made the new RaZberry primary and nothing much seem to happen.

Tried to revert so that my existing Zstick was primary again, this completed and I excluded the RaZberry from the Zstick network.

Now the network seem's to be broken.

Right now, I'm considering resetting both controllers and re-including all my devices to the RaZberry.

Any idea's where I went wrong?

Thanks

Neil

Not very clear. May be you can explain better?

Hi, sorry... i'll try again.

I did another test before I went with the RaZberry as a primary controller.

1/. Reset RaZberry controller via its z-way-server, included a single node (TKB socket) and tested working ok.

2/. Reset Zstick controller via its z-way-server and included this controller into the above controllers network.

3/. With RaZberry still as primary controller, confirmed operation - OK

4/. Using the Zstick z-way instance, checked to see the node2 (TKB above) - OK, but no control from this z-way.

5/. Made Zstick the primary controller, still no control from Zstick and none from original RaZberry.

From here, I reset both controllers again and proceeded to populate the RaZberry again.

Only downside, some of the main's node's were a pain to re-include.

You always need to run interview for devices included not by this Z-Way. Becoming primary does not mean inherit interview data.