How to get rid of dead entities?

Configuration
1

Made an AWFUL mistake today. Under some stupid whimsy decided to add another Remote Home Assistant custom integration :frowning: One was working flawlessly between my 2 HA instances in different locations sending data in one direction from slave to master for some years already- very convinient. But my stupid idea to make traffic in both directions resulted in ā€œmirrorā€ effect despite my idea that different prefixes would block such behavior - and result was a massive amount of sensors like c2_c2_c2ā€¦ (some thousands of them)- and despite uninstalling Remote Home Assistant after numerous attempts to delete them on both instances had to give up. Any ideas- the only way I see now is to delete them permanently from core entities registry and database- but how?
Best (and very frustrated with my stupid mistake), JR

2

Do you have backups from the time before?

1 Like
3

Iā€™m not sure how you set things up, but you can go to Settings > Devices & Services > Entities. Filter as necessary, bulk select, and delete via the action menu.

4

Yes I have backups but will loose over 1 week of statistics data then :frowning:

5

Thanks for the suggestion but that is just this that does not work for me :frowning:

Todo properties
Todo properties552Ɨ219 20.2 KB

No deletion
No deletion486Ɨ216 10.8 KB

Todo mess
Todo mess1875Ɨ852 157 KB

This is the mess I managed to create :frowning:

6

You can carefully edit the .storage entity_registry when the system is shutdown (or extract that file from a backup)

7

Was using that method some years ago- but then it was Core install, not HA system as now- all addons cease with ha core stopā€¦
And the worst thing about backups is that I do not think I will want to build some 10s of sensors gathering data from another instance- but will definitely try. Shame I was delaying 2026.4 install- then the backups would be very recentā€¦

1 Like
8

I simply donā€™t see you being successful without that restore here. You recursively dumped thousands of ents and canā€™t tell which was real except for names.

Make a backup of what you have now and research importing the stats later if you need them that badly.

Youā€™ll be fighting this install forever if you choose to go forward with it and honestly without the stats my choice would STILL be to restore and accept it. Thatā€™s gonna be a nasty fix if at allā€¦ Sorry.

9

Then remove the integration responsible for this. After that, remove the unwanted entities and add the integration again.

10

I think the spook integration can remove the entities if they are marked as orphaned.

1 Like
11

Wow, that name is diabolical.

12

Thanks everyone for suggestions :slight_smile:
Lessons learned:

  1. Backup before every significant change and use scheduled backups to prevent data loss
  2. Managed to fix by downloading existing databases and changed .yaml configurations made after last backup
  3. Restored both instances to available backups
  4. Made some SQL magic to fill lost data (especially long-term stats)
  5. And once again- backup, backupā€¦
  6. Failed on cleaning core.entity_registry due to low knowledge of system- json was cleaned up but restored itself due to my insufficient knowledge about HAOS (some years ago on core that was not a problem)
  7. Spook (which I already had) gave some hints but not about this issue- or maybe I was not so good :frowning:
    So once again- kudos to everyone who teached and encuoraged me
    Best, JR