I have a stubborn ghost that I can't remove, from the HE logs I get "Failed node 1F remove status: 0 SDK failure node is no longer in failed node list". The device is shown as SPECIFIC_TYPE_POWER_SWITCH_MULTILEVEL so I air gapped all my other dimmable switches, but I have a feeling this ghost isn't for one of them. I picked up a Aeotec Z-Stick and tried following the USB Sticks removal process, but the is Failed never turns the device name red.
I've tried a soft reset, unplug for 5 mins, and various other suggestions including a last ditch wrap in 2 layers of foil, under a metal bowl, in a metal box, but I'm still able to control the nearest zwave switch even with that much metal surrounding the HE hub.
I've read the only other options at this point may be to fully cut power or move the hub physically far enough away from any device, but are there any other options with the PC stick to try?
Just to clarify, what you're saying is you air-gapped all of your dimmers that are currently installed, correct? Did you also air-gap your switches? Just in case an incorrect device ID occurred, safest to air-gap all of 'em.
Also, in some cases air gap doesn't kill the radio. I believe it does for all Z-Wave+ GE/UltraPro/Jasco switches, but not sure about other brands. So if you have a ghost device that doesn't kill the radio when air gapped, then you may have to kill power.
You should have a shot at IDing specifically which device caused the ghost. Usually it's one of the devices just after the ghost in your device list. So if you need to kill a circuit then you should be able to get by just killing one circuit.
Unfortunately only my dimmable switches have an air gap. I think this ghost is from a device that fell off the mesh that I missed when I added it back. I may work backwards on the zwave device list and see if I hit it as I've got 48 zwave devices so really hoping to avoid a reset.
If you cannot remove it using PC Controller, its not a ghost node because a device still thinks it is attached to that node and is responding to the ping.
Are you sure you are trying to remove the correct node? The node numbers are decimal notation in PC Controller and the DNI listed on the device page of the hub is HEX.
Z-Wave details shows both DEC (0xHEX)
You could hit the On/Off buttons in PC Controller to see if a device responds as well.
Thanks for this hint, yeah I'm using the decimal from HE to try on the PC Controller. Unfortunately, just getting timeouts using the "Basic Set ON" and "Basic Set OFF" buttons, other switches do respond when they are clicked.
You said you wrapped the hub in foil? What about the USB Stick? Thats what is pinging the device. But then it might not be able to talk to the hub so not sure how the removal would make its way to the main database.
Not sure how something is responding to the is Failed ping if not responding to on/off commands.
Removed failed is available, but that also timed out. I took the hub a mile away to see if I could get it to remove, but still got the same "Failed node 1F remove status: no reply" and "Failed node 1F remove status: 0 SDK failure node is no longer in failed node list" messages when I tried to remove.
I'll have to search the forums more, this seems like it may be a z-wave db corruption.
Sounds like those messages are from the Hub? The Hub can be unreliable at removing nodes.
What about in PC Controller? Usually that will remove them no problem as long as nothing is responding to the ping. I have never had one take more than one try to remove that way.
If you want to remove while off-site with PC Controller I think you would need the hub and the USB stick together.
In your screenshot, why does it say node 0? Did you actually have a node selected?
What version of PC Controller do you have? Your logs look different than mine.
I appreciate you doing that check! I'm also on 5.54.103 I'm not sure what that Node 0 was from, but yeah I had device 31 selected. I'll try bringing the PC Controller off-site and see if there's any luck removing away from all the devices.
