Dashboard became a copy of another dashboard

ildar170975 commented 3 months ago

Checklist

[X] I have updated to the latest available Home Assistant version.
[X] I have cleared the cache of my browser.
[X] I have tried a different browser to see if it is related to my browser.
[ ] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

Got a very crucial issue while attempting to test another issue. A whole storage-mode dashboard was replaced by another storage-mode dashboard - i.e. I got 2 (almost) same dashboards:

Assume dashboard_1 has 20 views, dashboard_2 has 10 views.
You need to move card_X from some view on dashboard_1 to some view of_dashboard_2:

Then move this card back to the original view.
Result: dashboard_1 becomes SAME as dashboard_2 - only this card_X is a difference. And a json file for this lost dashboard is overwritten with a content of another dashboard. Here the 1st "lovelace.lovelace" (dashboard_1) file became a copy of the "lovelace.lovelace_css" (dashboard_2) (as I said - only the moved card_X is a difference):

What I tried to do:

Opened that json file of the overwritten dashboard (sudo nano lovelace.lovelace).
Pasted a content of the same file from a backup.
Cleared a browser's cache just in case.
But still the dashboard is shown as a copy of another dashboard.
Fixed only after rebooting HA.

Describe the behavior you expected

see above

Steps to reproduce the issue

as above

What version of Home Assistant Core has the issue?

2024.4.1

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Chrome 123.0.6312.106

Which operating system are you using to run this browser?

Win10x64

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

github-actions[bot] commented 1 week 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.

ildar170975 commented 1 week ago

Cannot (& do not want to) reproduce. Closing.

home-assistant / frontend