I have a C8 that has some Z-Wave issues. The issues I have with the Z-Wave ghost item and one item that fell off the Z-Wave mesh network. Looking to figure out how to clear the ghost item and get the other item back onto the network.
I think this one is an old device that died, and I couldn't get it excluded.
This sensor is good, but no longer responding.
I tried using Z-Wave JS to remove it, but it didn't offer an option to do so.
Firmware 2.5.0.130; 7,23,1
I did the power hub and unplugged it, but it didn't help.
Any advice?
Thank you for your help.
I cannot seem to clear this. Tried restoring the DB and the radio. Still cannot clear this. Any suggestions?
If you're still in js mode, simply click refresh a time or two on that line and the remove button will appear
I have tried that it still doesn't work. I have two devices as far as I can tell that fell off the network too.
disconnect power from the devices. Shut down hub and unplug for 1 full minute. Power back up and then hit refresh on those lines a couple of times to see if the remove button shows up
Thanks I will try that again. The good news is I woke up this morning and it looks like all the devices are back online. I haven't checked to see if that other device has been removed if I leave it on JS, is this going to be a big problem in the future? I am thinking about going to c8 pro. Would this make my life easier in the long run? I just find Z-Wave very finicky at times. So I'm looking for the path of least resistance. Thanks again for your advice and help!
1 Like
I would only run z-wave JS on a c8 pro. Z-wave JS is much better at removing ghosts. The best way to remove ghosts when using zipgateway is a z-wave stick
1 Like
Before you try to remove the devices again, it should help to restart your radios...this only happens when you shut down you hub.
Settings> Shut down hub
Pull power after hub LED goes red
Wait 30s
Restore power
Wait a few minutes after your hub boots up and then try the Refresh>Remove again.
As @rlithgow1 said, at this point Z-WaveJS is generally the best option on a C8-Pro.
I tried that that still didn't work. I do notice other devices not working in the JS mode. I do have a c7 that all the radios are disabled on. But standing up another controller and then trying to insert it to remove it. I don't have the skills or the equipment to do that. I feel like it's stuck in the database and I need a way to remove it and it's less about the radio waves.
I guess it's just me that Z-Wave I find so finicky. I don't know where else to go with this other than start from scratch at this point. Any other suggestions before I trash this whole thing. I have too many devices to really do this with, but I might abandon the whole solution I do appreciate your assistance. I'm just frustrated with Z-Wave.
Is above still your current status, things are online/working, and your only issue is a remaining ghost?
Post a screen shot of your Z-Wave Details page showing any remaining ghosts.
Also, I think you know this, but running Z-WaveJS long term on a C8 is not officially supported, can be too much for pre-C8-Pro hubs, so at some point you probably will most likely need to switch back to ZipGateway. Some folks have had success w/Z-WaveJS on a C8, but that's the minority.
Yeah, the ghost remains. I can't figure out how to get it undone. It's the ghost of the previous door sensor that died. I replaced it with a new one, and everything was okay, but recently I noticed a ghost and tried to remove it. There's no device attached to it, so I can't set it as a virtual device and then remove it. I feel like I'm stuck and running in circles. And JS mode. Some devices stopped responding, but I've been slowly working through them, too. I know JS is the future, I want to get there. However, I sometimes struggle with Z-Wave. This environment's been updated since c5. I'm just looking for a way to clean things up, potentially get a pro, and then move forward. I'll probably leave my C7 in place because I don't think there's much difference between the C7 and the C8 other than the chipset, which I'm not using. I'm hoping if I can get the ghost resolved fix some of the problematic devices with JS to move forward. Just so you understand what I'm trying to accomplish and get a clean database to prepare myself for the next evolution. Sorry for the long-winded message. Sometimes I feel like this is a part-time job too LOL.
If your only ghost is a contact sensor, then you could be able to ignore it if it won't remove. Battery operated devices don't route, so nothing will try to route through it and get "lost" which is what can happen w/ghosts of mains-powered devices.
Thanks for the response. If I migrate to a new hub in the future will this bring the device along with it?
Yup - ghosts are in the Z-Wave database and "come along for the ride" when you do a migration. In general Z-WaveJS has been very good about removing ghosts, and you can try again to remove it on the C8-Pro w/the Refresh>Remove buttons on Z-Wave details.
You could try the Z-wave UZB stick ghost removal process, but if "things just work" and your only issue is a contact sensor ghost then I'm not sure it's worth the effort.
I have two I can't get rid of either.
I'm not stressing too much-trying anyway.
The cure may be worse than the illness.
2 Likes
Yeah, the second option is really difficult. I assume they have a Linux version. I converted everything over from Windows to Linux and I don't have a Windows device to run this through. I have to look at this further. I think I did this way back when a long time ago, but I've since removed all that. I do have three mono price shockwave sensors that don't seem to work underneath js. I'm looking to work through that as well or I might have to change the devices. I know they're really old and they were glitchy when they did work.
I don't see the PDF. I'm looking for the controller software to see if they have a Linux version.
Thank you all. The only last question I have really is the mono price shock sensors don't seem to work in JS so I have two last questions. Is do these devices work underneath js and if not what device should I look at to replace them if need be? Today I'm using a third-party device handler underneath legacy and they work okay at times. Wanted to see if you had any experience with them.
Trying to get this working in version 7 and it's very different than the old five version. There's a documentation is written on. Plus I'm fighting Linux in addition to this.
