It's been several weeks now, but I am still not able to exclude or include z-wave devices. I have tried several that I have and I'm absolutely stuck. I have a C-7 Running 2.2.5.131. There are several ghost devices that show up that I can't remove no matter what I do. I'm not sure where the problem is anymore. It started when I was installing several Zooz S2 On/Off Switches. I installed 4 of them and then at the 5th one I can't add or exclude any devices anymore. Any ideas to try?
One thing that may kick things off again is to gracefully shutdown the hub.
Settings -> Shutdown Hub.
When the hub has shutdown, remove the power to the hub. Do this from the 'outlet' side not by pulling the usb cable from the hub as these can be fragile and it is always best to leave these plugged in.
After power down wait 30s to 1min and then apply power again.
This will reboot the z-wave radio. A reboot of the hub with no power down does not.
This may or may not get things going again but it is worth a try.
Good luck.
1 Like
Maybe look at the procedures on this page might help, I know it helped me in the past 
https://docs.hubitat.com/index.php?title=Join_and_Reset_Instructions
Inability to include/exclude could be caused by your ghost nodes. They need to be removed, regardless.
One thing to try first: power down the devices whose failed pairings caused the ghost nodes (usually the next couple of higher nodes) then hit Refresh a few times for those devices on Z-Wave Details page. That should bring up Failed for that node and a Remove button, that will let you remove the devices. You can’t get the device to Fail if the hub can still ping the node, and some types of ghost nodes still respond.
Doesn’t hurt to reboot (not reset) the Z-Wave radio after this too. See details in post above.
If that doesn’t work to remove the ghost nodes, bring out the big guns, use a Z-Wave USB stick and SiLabs’ PC Controller, part of the free Simplicity Studio software.
Here is @danabw’s writeup:
Also, after you clear up your ghosts, the next time you try to add them, if they fail--then try clicking "Discover" next to the ghost node to see if that will fix things.
It worked for one of my S2 devices (but I still am wholly unable to include my S0 lock right now--there's something amiss with inclusion it seems).
This one I have done several times LOL. I even left the dang thing fully unplugged for a few days to see if that would make a difference and I was a bit miffed at it hahaha.
1 Like
at the moment all the zwave devices I have are zooz and two of them I now am seeing are not supported any longer grrr. So all I have are the on/off switches to exclude/include and these procedures do not work. I have done it in the past for several other switches so its not.
What are you seeing as not supported?
Also.. Could you screenshot your Z-Wave Details page?
That supported list is also more of a guideline .. It is by no means a comprehensive list, you will find many things that work fine that are not on the list.. And sometimes devices get pulled when too many people have problems with a specific device..
ZEN25 S2 Double Plug and the Zooz 4-in-1 Sensors. I do have at least one of each of those working on my system at the moment so I'm not sure if they are the ones that are causing problems or not.
1 Like
Ooo.. Yea.. this thing is the devil.. In my testing I have witnessed it doing some really nasty stuff, like watchdog resets, which would cause some pretty big routing issues for any device that was routing through it..
This one should work, although I hear it's a bit of a battery hog and a bit slow on S0 and since it supports S0 only it can be a pain point as the 700 series SDK doesn't have a method of skipping S0 bootstrapping for S0 only devices.
2.2.6 is getting an update which should help with more "ghost node" creation during inclusion. Most of the time these "ghost nodes" are actually real nodes included without security and the Z-Wave certification secs say we are supposed to stop discovery, but if you click the "Discover" button on a node that hasn't been reset or excluded, it might discover for you on 2.2.5. 2.2.6 will continue discovery on these S2 KEX failures as they are a valid node, just without security..
2 Likes
So I'm a slight novice here and I want to make sure I'm doing it properly. Based on the security alone I'm guessing that 09 is my on/off switch and 021 is the double plug that is sitting unplugged next to my keyboard for weeks?? I'm assuming I will need to put my switch into inclusion mode when I hit discover? Because so far all of my attempts at hitting all of those buttons do absolutely nothing. If I need to wait for the next update I will Do you know when the update you mentioned will come out? If it doesn't fix with that update I'll try removing the double plug I have in rules now and see if it is messing things up as well. But to be honest I'm having tons of issues at times with devices so I'm continually troubleshooting why they are unresponsive. It's lovely when everything responds as it should though 
As far as the 4in1 the compatibility list specifically says it is not compatible with C-7. And I do know certain features do not work well but I don't know if it's the sensor or HE that is the issue. LOL I only know the battery dies on them when they stop running my motion-sensing automations.
