I installed a device tracker and created entities via yaml. Now I can’t delete these read-only “ghost” entities it created. I deleted the HACS intgration and yaml entries, rebooted several times, but cannot delete these rogue entries. I’ve read I can dig into the registry files to manually delete, but COME ON-- this is a common problem, posts are plentiful on the problem, surely there is a better way to get rid of old ghost entries like this?
1 Like
Sure that they are really still there and not only in the browser cache? Refresh your browser or look with a fresh browser fist, before manipulating any files.
Most of the time it is just a caching issue of the frontend.
And just in case, you have opened the settings of the entities and deleted them there, haven’t you?
Sure install this integration from Frenck 
GitHub - frenck/spook: Spook 👻 Not your homie , then you can with a service call, and much more with this integration.
Reset browser cache, updated to latest HA, rebooted several times, these entities can’t be deleted-- read-only device_tracker. Deleted them from known-devices.yaml as well.
Sorry, but you completely misunderstand me. Perhaps the readme on Frenck’s repository misled you. Me too at first. But it’s a really handy integration. Read it a little better please, and try it out, that’s all I can say. Definitely not for trolling, try to help!!! That’s why I’m on this community, to help and be helped. Thx!
I guess Frenck thinks his description is funny. It’s not, if you really need some of those services. I think some of these should be included in HA core. I’ll try it, sorry for jumping on you.
No problem it’s solved! Glad to be @ service.
His descriptions are meant to let you know that the integration isn’t guaranteed. It’s also meant to scare away people from using it because it may cause issues if you misuse it.
The reason this integration exists is because these services are not (and most likely won’t be) in core.
1 Like
Understood, this HACS integration I suppose is meant for hard core devs. As HA becomes more newby/non-dev friendly I guess you want to shield dangerous integrations. My point is somewhat common issues, like “ghost” entities, should have a clean-up function. Or fixed so ghost entities don’t exist to begin with.
1 Like
Yes, this is the path main teams wants, but bugs happen.
1 Like
Jeez. As soon as I installed Spook, my ghost entities vanished. Weird. It’s as if it ran the ghost entity function upon installation.
1 Like
Okay that’s exactly what it did. It automatically “spooked” and floated around to find my orphaned entities and killed them. Yikes. It also found a lot of dashboard items that pointed to nothing. Pretty powerful!