I'm a longtime ST user and new to Hubitat. I've successfully migrated about 70 devices to Hubitat so far (both Z-wave and Zigbee), but I simply cannot get Hubitat to include many of my Z-wave devices. I can exclude/include in ST with no problem, so I know I'm triggering the device inclusion method properly, but Hubitat refuses to recognize them.
Devices that I cannot get Hubitat to include:
GE 14284 Enbrighten Z-Wave Plus Smart Outdoor Switch
GE 12722 Z-Wave Wireless Smart Lighting Control Light Switch
GE 14288 Enbrighten Z-Wave Plus Smart Outlet Receptacle
GE 14291 Enbrighten Z-Wave Plus Smart Light Switch
Some of those exact same devices I have successfully paired on a C-7 hub (2x14284, 2xGD00Z-4), so I know it can - if the system isn't gummed up.
Have you tried doing a shutdown on the HE hub, and unplugging power for 30s?
Either that, or wait for the next hub software version that fixes even more pairing issues (there are definitely zwave and pairing issues in 2.2.3.119).
Although even when the new release comes out I would still recommend doing a shutdown and remove power for 30s one time to get everything 'cleaned out'.
On a normal hub reboot the zwave side never gets completely powered down/reset. That is why SOMETIMES a full "pull the power for 30s" can help when a reboot does not.
Really the only scenario that helps in is one where the zwave/zigbee side get really goofed up.
Long term, as they get more fixes in this new product, pulling power (after a graceful shutdown, of course) is not something you should expect to have to do.
Side note - I would avoid doing zwave repairs for now, too.... I was able to get my hub/zwave side of things in a bad place multiple times when doing repairs on that release.
Or if it's fixed before the t-shirts ship out they can be sent to a third world country like they do with Super Bowl champion shirts for the losing team.
Hi everybody,
So, this is one of these times when I want to put my Hub into orbit with a banner attached to it big enough for everybody to read it from the surface of the earth and marked with words I won't write here.
I have 3 hubs using Hub Mesh (a marvel, btw). 1 C4, 2C5. I purchased my C7 a year ago or so and decided to do the migration of my C4 (which contains most of my Z-wave devices and all my safety sensors (leak, smoke, natural gas...) and water valves. No need to say this one is one critical hub and that's why I wanted to migrate it to the C7, hoping to gain better reliability.
I think I understand the basics of what a mesh network requirements are and I made sure to add my devices from the center out.
However, I'm losing my mind because since yesterday I had to do a complete shutdown and pull-the-plug-for-30-seconds almost every 2 or 3 paired devices, the hub failing to pair them and generating ghost devices that would return status 2 when the "remove" button was pressed, even though those devices were phisically powered down.
Has anyone any understanding of what is going on with this hub and why it is such a pain to pair devices with it? Should I give up and wait for HE to come with a better solution where it doesn't take up to 15 minutes to just successfully pair one single device?
If you have any chatty devices, like some sensors which report on regular intervals, or any power monitoring devices those could be causing some issues. Check the devices preferences and make sure the driver selected when pairing did not set them a very short reporting interval by default. For some reason this seems to grind the ZWave radio on the C7 to a halt. Increasing the reporting intervals will help. Also check the paired security for any that paired with S0, as this adds extra overhead and has been known to cause issues if there are a lot of messages using S0.
Thank you for your help @jtp10181, it gives me a track to follow which is what I needed at that point (before building a rocket capable of reaching orbital velocity).
I have had difficulty pairing if the devices are newer Z-Wave plus devices and can pair at various security levels (S0, S2, etc.). If these devices do not establish a direct connection to the hub for pairing, it would often fail.
Is it a C7 issue? Is it a mesh issue (not propagating the security pairing thingies)? Don't know.
What worked for me is to move the hub closer to the device being paired with the new Z-Wave plus security. Once I did this, I stopped creating ghosts and got things paired consistently.
I see what's going on. After pairing 18 nodes, 17 of them became unreachable (according to logs after network repair). Also, I see that their Routes are all linked to a... non-existing node (node 01)... And, yep, did cold reboot, same route, all of them except one are routed through a non-existing node... no wonder why this can't work. This has to be a bug in their firmware. @bravenel ? @bcopeland ? Any idea how to reset all SUC's ?
Thanks for the help! For future readers: I can confirm it’s a matter of doing things the proper way: do not exclude and run repairs at the same time do not associate far away from the hub and do not chew the hub either… although I was really hoping chewing it would help. I think @bcopeland will now have enough data for future foolproof of the association process… for he had to deal with the best fool ever! lol thanks everybody and thanks again @bcopeland!
Although I wish they saw what I can see here... still getting ghost devices generated every step of the way... It remains problem/ inclusion times out before init is done or something like that. It's like the hub doesn't finish including fast enough or so...
Well, well, well... 29 nodes successfully created... And then, an hour later, without doing anything, all nodes unreachable, no repair possible and 2 nodes became ghosts after reboot. All these devices were working fine on a C4... there is clearly a huge problem with that hub. 4 years with HE, 2 years with ST, never seen such a mess. This cannot be just a user issue. I did nothing, everything was working and 1 hour later, everything down, 2 dead nodes, impossible to remove them, impossible to ID them for now and almost all nodes marked as failed during repair
Quit doing repairs, unless you for some reason you know you need to do an individual repair. Full repair isn't doing what you think it is, and probably doing more harm than good. From what I understand, the C7 should rarely or never need a full repair. You are far better off adding a few devices, let the hub do it's thing for 30 minutes or an hour, then resume adding more.
Did you try to do a shutdown, pull the power at the wall, wait 1 minute, and reboot. And then leave the hub be for 30 minutes or so after booting to settle out all these changes?
