Energy: cannot remove undefined entities

[smitterer]

The problem

When an entity is not available anymore (for example if the entity got removed and didn't have a unique_id), it can not be removed from the energy configuration.

Happened to me after upgrading to the latest Fronius integration which removed the sensor "inverter total energy" / created some new one for that.

See https://community.home-assistant.io/t/energy-can-not-remove-undefined-entity/367158

What version of Home Assistant Core has the issue?

2021.12.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

energy

Link to integration documentation on our website

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

See https://community.home-assistant.io/t/energy-can-not-remove-undefined-entity/367158

[owenglaze]

I am having a related issue with deleted utility meter energy sensors clogging up the drop-down menu on the energy dashboard. These zombie sensors do not exist in home assistant. They also appear to prevent new energy sensors that actually exist from appearing in the menu (the drop-down menu only shows 8 sensors no matter what). I had to change the name of one of my new sensors to a zombie sensor so I could actually select it (total_grid_energy_delivered for my "Grid Energy Returned" sensor).

[IZZE2000]

Yes, same here. I went from Shelly for Hass to the native integration. Now i have several zombie Shelly for Hass entities in the energy configuration that i cannot remove.

[probot-home-assistant[bot]]

energy documentation energy source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (energy) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[ahmeduno]

Same problem here

[cdk222]

I have the same issue. These entities do not exist in settings\entities after searching for disabled\hidden\unavailable etc. I simply cannot find where to delete them. Unfortunately they are no clogging my device menu as I have over 40

[bsp9493]

I have the same issue. These entities do not exist in settings\entities after searching for disabled\hidden\unavailable etc. I simply cannot find where to delete them. Unfortunately they are no clogging my device menu as I have over 40

I too have the same issue, did not notice it until today while doing some system maintenance.

zombie entries that do not exist anywhere, unable to add new ones to energy panel

[Kimble8650]

I have the same problem with the shelly integration. I was configuring shelly devices, and in the hassle of figuring out how to add them, some zombie entities were created. Now I cannot add my correctly configured "washing machine" entity to the correct area, most prob. because there are zombie entities floating around, which I cannot delete.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[nclapham01]

I have the same problem still with version 2022.8.6. After adding some energy monitoring light switches and then removing the devices from home assistant, the entities still remain in the energy dashboard and there's no option to remove them.

[TheRoarman]

I think it’s because of the history. If u have time next week, I’m going to try and remove the old entities from history to see if it removed them from Energy dashboard.

On Thu, 25 Aug 2022 at 19:48, nclapham01 @.***> wrote:

I have the same problem still with version 2022.8.6. After adding some energy monitoring light switches and then removing the devices from home assistant, the entities still remain in the energy dashboard and there's no option to remove them.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/61864#issuecomment-1227583834, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4MUJET3EZBUXSX2AVT3C3V26WXJANCNFSM5KDCJWGA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[caco3]

same to me, I renamed then and now can no longer remove the old generic ones:

Maybe its just a layout issue and the names are to long?

[martienpoels-bank2loyalty]

Hi, I have the exact same issue, so would be great to have a fix for this.

[Iceman248]

I noticed quite a few zombie entries myself.

[witmannmark]

Same problem also! Will be good to solve it.

[witmannmark]

I solved the problem with a very easy method. You must rename the ID one of existing energy measurement sensor to the ID, what you can't delete from energy dashboard. After that you can delete it from dashboard, (Because it is again an existing id) and you can rename back the ID.

[raoulteeuwenPE]

I think i have the same problem, and no clue how to solve. I have this helper, which seems to record data, but still throws an error and showing as 'entity not available' in dashboards

[cg6]

I had this issue, it is due to the long name of the old entities. I was able to zoom out the browser (ctrl & -) until everything was tiny and eventually the trashcan icon showed up. Deleted now!

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.