In that case, just Re-join the device that has the bad route. It will be cleared when it rejoins.
I have 5 zigbee battery devices with routes directly connected to the hub, show offline but still function.
Since pairing the devices I have added repeaters (plugs not bulbs). In an attempt to repair the zigbee mesh and get the devices back online I unplugged the hub for 30 mins and plugged it back in. It’s only been a few hours since the unplug. In the IDE I now have ghost devices in the route for 4/5 devices but all 5 show online (which is new) and all 5 funtion how they should.
Do I need to give it more time?
If I leave the ghost devices will it cause issues?
If yes, is there a way to get rid of them or am I left with deleting and readding the devices?
If everything seems to be working ok, wait 48 hours and then check the IDE again.
If possible, use/trigger each end device a couple of times during the waiting period.
Remember that the IDE only shows you one particular route reported to the cloud. Not necessarily the most frequently used route.
After the hub was offline, it can take awhile for everything to get synced up again, so just be patient. 
2 Likes
I have some devices that aren’t working, and have noticed that their routes are listed as:
This Device (0C0B) ↔ Unknown Route (????) ↔ Home Hub
So I’ve followed the steps outlined in this post: FAQ: How to remove ghost devices from your z-wave and zigbee networks but on Step 9, in the “How to remove a ghost device from your Z-Wave network” section, when I click Create I receive this error:
Oh No! Something Went Wrong!
Error: 500: Internal Server Error
URI /device/save
Reference Id 0076ba69-c1cc-4ff1-af4c-c73e77282f3a
Date Sun Oct 17 17:38:20 UTC 2021
Does anyone know how can I get these Ghost devices removed?
Thanks in advance
Dicky
oh fun the internal server error for no good reason.
Try logging into the IDE using a browser in incognito mode. More often than not it will clear that.
That said - for this a specific case:
This Device (0C0B) ↔ Unknown Route (???) ↔ Home Hub
you dont need to create a new device to remove it in that case. You dont know what the offending network ID actually was (??? is not a valid ID) so you cant delete a ghost. To fix that one - you may want to just try rejoining (no removal, just rejoin - it’s zigbee (4 digit ID)) whatever 'This Device (0C0B) ’ is. As long as you dont delete the device in ST, the rejoin should keep the existing id and not require you to recreate anything.
I followed these guidelines but when I tried to delete the Ghost account within the app, it would not delete, even after forcing delete twice. The only way to delete the Ghost device was using IDE - but after rebuilding Zwave multiple times and days the Ghost accounts referred to as an unknown device in the route continued.
I can’t see how to delete the ghost account by using the exclusion utility from the Hub.
Sometimes if these Ghost accounts appear to be eliminated, new ghost accounts occur after rebuilding Zwave. What is causing the creation of these new ghost accounts?
Ghost DEVICE not account.
And also do NOT follow these instructions to the letter anymore. With Groovy going away the IDE is not authoritative anymore and you need to start looking at the new tools to manage your system. (yes ZWave and Zigbee management tools suck in the new environment. Keep asking support for everything that’s missing)
The advent of Drivers and the new environment impact the devices listed in the IDE and now devices using drivers show up as ‘unknown devices’ in the hierarchy. So you can’t tell if it’s a ghost or not simply by using that logic alone. You also need to chase down a given device ID and determine if the ‘ghost’ is using a driver or a DTH (is it listed as a ‘placeholder’ in the IDE) and if it is dont attempt to use these instructions to clear a ghost.
As they’re due to start automatically migration of devices in ledlss than 20 days to drivers at this point this article will become less and less helpful.
4 Likes
The Edge devices showing as Unknown just caused me to force delete devices. I thought they were ghost devices, only to find out I screwed up my mesh. ST should just get rid of the IDE if it can’t show the correct data. Misleading data is more dangerous than no data.
1 Like
So I’ve got a few TRUE ghost devices it seems. But I’m not able to delete them in the ST app (android) once I’ve created them in IDE. I click remove but nothing happens. So I wound up deleting them in the ST API browser. But I don’t think that is having the right effect.
Any ideas? How are we able to clean up the ghost devices in this new environment?
Pretty sure you shouldn’t be creating devices in the IDE. Actual physical devices should only be added using the app.
1 Like
Creating a virtual device using the IDE and assigning it the device network ID of a ghost device has been part of the “forum approved” method for getting rid of a ghost. I used it successfully myself a few years back.
If there’s any non-IDE way to go about this it has to have the ability to force assignment of a specific network ID.
With the latest firmware you should not be seeing an issue of ghost devices after a few days as the hub is by supposed to clean it up by itself. If you are seeing this issue, I would recommend sending an email to support@smartthings.com to investigate it.
4 Likes