Two primary z-wave controllers in conflict.

I use an Aeotech USB Z-wave stick in an openhab as my primary controller and have previously added my ISY as a secondary controller. The setup had once given me problems when moving devices from a homeseer, but has been rock solid for a while now. I add nodes on the stick, then sync the network and they would populate into the ISY.

I needed to upgrade my ISY firmware to support a new device and when I did, the ISY lost it's connection to the Z-wave network. I put the ISY in learn mode and actuated the z-wave add function of the stick and the ISY re-synced. However, it now thinks it is the primary controller with a node ID of 22. Although the openhab can see the ISY, the ISY fails to contact node 1 (the stick) or 2 (itself in the old config). I assume this is due to the node ID disagreement. Other than that the ISY can query and control all the network nodes without issue.

It cannot transfer the primary role as it cannot contact the other controller. Last time I had an issue like this it wound up wiping my network out and I needed to re-include everything, which I would like to avoid. Is there a way to force the ISY to enter the network as a secondary controller?

Edited January 19, 20214 yr by gsnipes