I'm in process of writing device handlers for my devices. Some devices I have to change association group because Hubitat by default associates with the wrong group. Like associating with normal group instead of multichannel one with Fibaro Double Switch 2, or to group 1 instead of 5 for Fibaro RGBW Controller (in older zwave spec the last group was designed for the hub not the first one).
Not a big deal, I've been through this with Smart Things and my device handlers take care of it where appropriate.
But after reboot today some of my devices stopped reporting, I checked what is happening and turns out zwaveHubNodeId was set to 0. My code relies on the accuracy of zwaveHubNodeId to set hub node id in the device so it tried to set it to 0. After another reboot zwaveHubNodeId was correct again.
Is this a freak occurrence? A bug? Did anyone else encounter it? How often does this happen, should I hard code hub node id in my DTH?
I thought the hub id was always 1 in Hubitat? Is it even configurable, I've never looked?
1 Like
the primary controller in a z-wave network always gets node id 1
1 Like
That's what I thought I knew, but I didn't say it as confidently as you did. 
Thanks!
I know primary hub always has node id 1 but are there no plans for slave hub support?
I don't see why there would be for this target audience / device? To answer the actual question, though, I have never seen Hubitat say there are any plans to add support for secondary controllers.
That said, you can pair a secondary controller with it right now - many of us already have. It is only good for things like finding ghost devices, though, as the primary controller (Hubitat) has no way of addressing or accessing devices paired to a secondary controller.
I too have my Aeotec Z-stick paired to my Hubitat for monitoring etc.
It's just future-proofing on my side 
secondary controller inclusion as well as including Hubitat into another network are currently not supported.
1 Like
