I'm seeing with a couple devices now, both 500 series chips, where pairing is timing out.
On my Zen16 the device seems to think pairing is fine, but the hub will report: "Z-Wave Inclusion timed out, status:7". Trying to pair a z-stick so I can remove a couple ghosts, it does same thing. In the z-stick case, the z-wave pc controller software reports "Learn mode completed. Replicated failed".
Unclear if it's the case or not, but also thinking this might be causing issues with a couple of my Ring Contact Sensors V2.
Any idea on what might be going on, how I can resolve, etc?
Just tried again, and it looks like the z-stick got a partial list of neighbors, but hubitat doesn't show anything related to the z-stick having included.
yeah, there's "update neighbors". doesn't do anything. re-excluded, and same thing trying to reinclude now, hub just says it times out, and pc controller says "learn mode completed replicated failed". =/
Mine joined up fine, and I see all my devices, so other than a potential issue w/your particular UZB stick, I don't think we have a general PC Controller/UZB stick issue here.
Regarding "Update" - this is the button I was referring to. Note the comments in this post that seem may be similar:
just got into a partial pair state again. it got 8 of the 41 zwave devices in my mesh. Update is greyed out so I can't click it. It also still doesn't show up on the HE side of things...
Log from PC Controller side
I can only imagine it's because of those ghost entries, but who knows. =/ I'd buy a 700 series stick if I thought it would make a difference. =/
Sorry, no idea if it would help, but I've never heard of the 500 series being limited in anyway. Really annoying/odd. I don't think I have any additional info to add. Maybe @support_team can help.
I have been having exactly the same issue since my migration to the C8 several weeks ago and I have a 700-series stick. Sometimes if I light some sage, bow three times to the east, rub the C8 gently between the antennas, and power cycle it for a couple of minutes, I can get the stick to properly include. But not often. It's as if the communication between the stick and the C8 somehow times out halfway, or the device thinks it is done but the hub doesn't. My mesh on the surface looks like it's in solid shape.
I've been having a similar issue with Ring gen 2 keypads and a smartstart. They appear to be included, then they either have partial functionality or they work fine for a few hours and stop. Or the keypad thinks it has successfully included but yet a ghost with a discover button shows up on the hub.
Might be moot... I might have finally gotten the ghosts to delete. they were in the unknown "discover" and "pending" state. Hit discover, then "refresh", then finally "Remove" (again) and they SEEM to be gone.
this is what i'm seeing as well with my ZEN16 multirelay. it seems to think it's done, but the hub doesn't think so. makes me think we might have a Zwave sdk issue... or a hub firmware issue.
I think you may be right... especially since I can fire up a C7 and get this to work every time. The counter-argument is that these are one-off issues, especially since the folks at Hubitat are unable to replicate them -- and they have tried at least some of them. But if that were the case there is something about the migration and the C8 that have exposed them, since they were all running fine on the C7.
I've been having a heck of a time with Ring keypads so I fired up a C8 with nothing else on it - zero zwave devices. I paired the ring keypad to it and it worked great. For a couple hours. And then it stopped working, with a red "network" indicator on the keypad. It was about 15ft from the hub the whole time, with a 40kbps direct connection (that's the fastest these ring keypads will support).
