I think you have enough advice here.
This is a shameless plea for you to stay in the community. You contribute some really good stuff and it would be a sad loss/big void to see you go. I can send snacks and drinks if that hel;ps... 
2 Likes
Unfortunately it's the opposite for me. After the overnight maintenance, every device has stopped working again, even those that slowly came to life yesterday.Back to just getting these logs over and over and 100% unresponsiveness:
I don't disagree with you, however, it's irrelevant. Hubitat is the one we're paying. If they purchased a shoddy SDK, they should be suing whoever made it. The fact of the matter is, using this new SDK is a decision HE made and it has caused my hub to become completely unresponsive. If your car had faulty brakes, and you crashed as a result, Ford saying "well in fairness, we bought those brakes from a 3rd party" wouldn't make you feel any better nor would it matter. It's the same situation here.
My zwave logs are flooded every 10th of a second with this message "seqNo: XXX, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0" from any device that tries to communicate with the hub.
I thought I was, but I tried this multiple times and it didn't work.
What I just need is a functional hub. Right now it doesn't have a single functional z-wave device. Pretty much this overnight maintenance that is supposed to fix my mesh destroys it every night. It slowly starts working during the day (no idea why), then the overnight maintenance runs and breaks everything again. I don't want to give up, but I'm not even convinced that the ghost node is the cause of 100% of zwave devices failing every morning. I think there's a bug here and I don't think there is anything I'm capable of doing about it. If I can't get my hub working, I mean seriously, what option do I have?
2 Likes
Just for tracking purposes, no, this did not resolve my issue. Both are now included with no security and 1 of them has energy reporting disabled. I'm back to everything logging the same message. I don't know if it's relevant, but the majority are these 4 devices repeating over and over:
I left the zwave logs open overnight. Everything looks good until 7:06am, then those logs started. Not sure if that time is significant for any jobs that run. There were some "Unknown"s prior to that, but starting at 10:06 it was
@bcopeland I know it's the weekend so not exactly expecting a response, but any insight would be helpful. I'm totally stuck here.
For anyone wondering, how do you get an S0 device to pair without security, it doesn't appear Hubitat gives you an option to do this. It pairs automatically as S0. I followed this advice from darthandroid on the Inovelli forum:
If it’s S0-capable, Hubitat won’t prompt about security and just add as S0; You’ll read about people struggling to use insecure devices with S0 devices because you can’t force hubitat to pair an S0 device as insecure currently. (A workaround is to kill power to the S0 device during pairing, causing the security setup to fail and fall back to insecure)
I don't know if there is a better way? I mean if the recommendation is to not use S0, seems like there should be an easier way? But this is what I did.
2 Likes
What shows up in the log when you try to remove that ghost node?
Presently just "Failed node 3E remove status: 0"
sometimes it says no reply, other times zwave network is busy, other times status is 2
Last several hundred attempts have all been 0 though.
Just to double check, when zwave gets into a bad state, are you doing the classic shutdown the hub, pull power for 30 seconds, and power it back up dance? I think on occasion that can help the zwave radio recover.
Truthfully I didn’t read through every message carefully to see if you mentioned doing this already, so apologies if this is a repeat.
I didn't mention that, but yeah I've tried that. I've left it powered off for quite longer too out of desperation, but no luck
1 Like
@bobbyD when one does a backup is the zwave device database stored there as well? Is one possible strategy simply to do a backup before adding any device in case the device add goes south, and if it does and creates a ghost, simply restore from the previous backup?
No, zwave data is only backed up if you have the hub protection cloud backuos.
Just purchased. Cheaper than an aneurism.
As a note though, I can't say whether or not your theory is correct and that it would revert the issue. I just know local backups don't have it at all.
Ah ok. Well, probably worth the $30 anyway tbh.
Btw I was always surprised this device wasn't supported. To my knowledge there is no other device on the market that can monitor and control 240V devices. If there is an alternative you'd recommend I'll look into it, but I don't think any exist?
1 Like
I have a v1 paired without encryption, reporting power every 5 minutes and it works fine. If I were in your shoes, I would put the C5 to good use to minitor the washer and dryer and use a virtual device via hub mesh to push the state over to the main hub. For example, I use a virtual contact switch (reports both on/off and open/close) to enable notifications and reminders on Alexa devices when washer/dryer are done.
Hah. That was plan A until I apparently discovered a bug with hub mesh that will be fixed in 2.2.8 as well.
You are like bad luck Brian lately. 
2 Likes
This has been discussed in the forum. I believe that the only way is to use a USB Z-Stick as a secondary controller and do the inclusion through PC Controller. I’ve never done it myself.
Apparently, if the only security choice offered by the device is S0, the Z-Wave API fo he 700 series chip mandates that no other choice (including no security) can be offered. Hubitat just reports what the API shows. However, SiLabs’ own PC Controller seems to be able to do whatever is needed.
1 Like
PC Controller maintains the capability for “backward compatibility” given that most Z-Wave sticks are IIRC still using the 500 series chip - there are at least 3 700 sticks out now but I’m not sure if PC Controller would let them use the 500 series SDK.
2 Likes
I had very similar issues to what you describe when I moved over to my C7. Z-Wave was very frustrating and unstable while that unremovable ghost device was still there.
I purchased a UZB7 stick from Mouser and using it to remove my ghost fixed a lot of my issues. It also came in handy on a few occasions afterwards.
https://www.mouser.com/ProductDetail/Silicon-Labs/SLUSB001A?qs=u16ybLDytRbJsMfgk3EnSA%3D%3D
As described above, changing (reducing) the reporting of power devices also helped a lot. It also helped to remove my Zooz Zen40 sensors back to my C5 hub.
1 Like
I finally went this route this weekend. It turns out that the Silicon Labs stuff (at least v4) works on a Windows 7 VM, which is good because that's what I had available. Got rid of two ghost nodes that have plagued me for a while. Then I went to exclude my Silicon Labs zwave stick and IT became a ghost node. Thank goodness HE was able to get rid of it, otherwise my HEs would have achieved orbital velocity, likely in many small pieces.
