Using the IDE, create a new device with a name you can easily identify. I usually create a virtual switch. Assign it to the appropriate Location and Hub.
Give things a few minutes to propagate
Using your app, delete the device. You’ll probably have to force delete.
I did this a few days ago and happened to have the hub events log open in a window. I saw some Z-wave deletion messages.
Unfortunately force deleting fails. It gets stuck ‘Deleting device’ for a very long time, and then presents me again with the option to force delete. The second attempt does the same thing.
I can see in the logs it restarting the zwave, but thats it.
[ 2020-11-18 11:48:16.000 AM PST
*8 minutes ago* ](https://graph.api.smartthings.com/hub/?all=&source=true&max=25) HUB zwStatus ready Z-Wave is ready
[ 2020-11-18 11:48:12.000 AM PST
*8 minutes ago* ](https://graph.api.smartthings.com/hub/?all=&source=true&max=25) HUB zwStatus starting up Z-Wave starting up
[ 2020-11-18 11:48:10.000 AM PST
*8 minutes ago* ](https://graph.api.smartthings.com/hub/?all=&source=true&max=25) HUB zwStatus power cycle Z-Wave power cycle started
I think you’re at the limit of what us mere mortals can do. Time to queue up at SmartThings support and get them to dig about in the guts of the system
I actually started with them, they told me that I had to exclude the device. But with a broken device they said I was out of options. Maybe I will try adding an actual device instead of a virtual device and matching the ID
I’ve had a case in with Support for the same thing for a few days now. They said they needed time to look into it but haven’t gotten back with a solution yet.
Email. I’m planning on replying back to their message with a request for update today.
Since I can’t see anything detrimental by having these ghost devices, I’m almost tempted to just let it be. I’m concerned that attempts to eliminate them might botch my configuration in some way.