@kfxo said in Adding Z-way as secondary controller to vera zwave network:
@iblis said in Adding Z-way as secondary controller to vera zwave network:
I have since added z-way as secondary and plan to exclude it before I clone the network. Since I did not do the above, is there anything I should look out for or that I can correct before I make the change?
Yes, there is a couple of things you should check to make the secondary controller exclusion less painless.
- Make sure Node1 is SUC/SIS, if not do the change and wait until every node in your network is updated with the new routes (manually wake up sleeping nodes if your in a hurry)
- Remove all secondary controller associations from nodes in the network before exclusion. This is not a problem if the primary controller also is running z-way-server since z-way automatically removes any association to a node that is no longer present in the network. This is one of the reasons Z-Way can be considered the Gold standard in Home Automation and unfortunately not many z-wave controllers on the marked today do this kind of maintenance by them self and what you end up with is more latency in your network due to nodes trying to communicate through association with hardware that is not present causing unnecessary traffic on your network (remember that according to z-wave protocol standards every node should try to communicate up to 4 times without getting a proper response before moving on to the next route).
- On your battery devices make sure the primary controller is set as the controller receiving wakeup notifications. If you did not make the <KeepMeInformedInsteadOfSIS> option change above before including z-way as secondary controller z-way will automatically set itself up as the receiving end after finish the first interview with your battery nodes.