Unable to delete FAILED ghost device in 2.2.4

Upgraded to 2.2.4 two days ago and while I was adding devices to a relatively new system. Ended up with a ghost device that I am unable to delete.


I've tried Repair and Remove, but it comes back without fail. Unfortunately, it seems that another one of my devices is attempting to use it as a route, obviously without success.

I see some reference to this issue with 2.2.3 and a suggestion to unpair a successfully paired device that might have caused this, but I can't determine which device that might be. Any other ideas? Is there some expert way to kill it?

First, if you can remove power from the ghost device, do so. Devices are listed in the order in which they are added, so you know what came before and after the ghost, that should help you ID which device it is.

Then I'd power down your hub (use the Shutdown Hub option on the Settings page, remove power from hub for 30s, power it up again. Then try the Remove button repeatedly - you may need to try it multiple times. I've had ghosts that required 8-10 shots on Remove to get them to go away. I've also sometimes thrown in a Repair and Refresh along the way, but in the end it's the Remove button that will do the work.

If at some point the Remove button disappears, use the Refresh button and it should come back.

If it persists, you may need to get a UZB stick to remove it.

1 Like

Not discover.. Just refresh..

2 Likes

Note .. If the node responds to a ping, the SDK will not allow the removal

Well, must have missed something. After shutdown of hum and than a power down, system came back to life with about two thirds of my devices indicating FAILED (much as it did yesterday when I thought I had a problem upgrading to 2.2.4). This doesn't seem right. Attempt to Repair a node close to the hub doesn't help.

Why is it trying to route through another failed node that is further away?

There must be some methodology for repairing the mesh that I'm missing.

Did you update to today's release, 2.2.4.143?

If not go ahead and do that, and then from my experience a reboot after a FW update never hurts.

If you're already on 2.2.4.143:

AFAIK you still have the ghost, correct? Until that's gone your mesh is not going to be happy. Need to focus on getting rid of it...

Started working out from closest device and then further ones. Ultimately got most devices working again. Ghost device is now gone! Just updated to .143 and am rebooting. Thanks for the suggestions.

2 Likes