home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.93k stars 30.15k forks source link

Unable to delete settings from Energy management feature #84074

Closed cociweb closed 6 months ago

cociweb commented 1 year ago

The problem

Hello, I've borrowed a portable energy meter. Later on I've played with the energy management feature. Let's say, as I don't have currently proper device to measure any energy parameters I've decided to roll back any energy management setting, I've just decided, I was not able. the only thing to demolish this feature is to set everything back manually, or load a very old backup.(no yaml or integration deletion possibility)

So any deletion/reset option for the Energy Management view could be appreciated.

Thank's

What version of Home Assistant Core has the issue?

N/A

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

https://www.home-assistant.io/docs/energy

Diagnostics information

-

Example YAML snippet

-

Anything in the logs that might be useful for us?

-

Additional information

-

issue-triage-workflows[bot] commented 1 year ago

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.

cociweb commented 1 year ago

Dear Bot, HA is updated, but the issue is still persist. ;) Only a workaround is possible: modify the lovelace yaml file manually. Thank you for your understanding. :)

issue-triage-workflows[bot] commented 1 year ago

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.

cociweb commented 1 year ago

Dear Bot, HA is updated, but the issue is still persist. ;) Thank you for your understanding. :)

issue-triage-workflows[bot] commented 1 year ago

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.

cociweb commented 1 year ago

This is still an issue.

issue-triage-workflows[bot] commented 9 months ago

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.

cociweb commented 9 months ago

bump

joostlek commented 9 months ago

Can you maybe elaborate more on what the problem is? Maybe add some screenshots?

cociweb commented 9 months ago

actually, there is nothing to shot: it's a conceptual issue, that you are not able to delete the configuration of the board/not able to fully empty/clean the energy board (restore the default) - as of now, at least 1 device should always remain. I've tried it from UI, but I also did not find the default yaml config of it as well.

Also if you change your mind during the install wizard, you are not able to exit from it. There is no back/cancel/exit button.

If I think it deeeper: maybe it's a frontend issue.

The only way to restore the energy dashboard's defaults is to restore a backup where it was not configured yet.

Also there is no possibility to wipe the data from settings>dashboards>energy.

joostlek commented 9 months ago

Ah right, I think that's more of a frontend issue indeed

cociweb commented 9 months ago

Can we transfer this issue, or should I reopen it over there?

issue-triage-workflows[bot] commented 6 months ago

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.