You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated to the latest available Home Assistant version.
I have cleared the cache of my browser.
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
When I edit something in frontend, I get some very strange bugs, this is happening from the 2024.11.x version, but with 2024.12.x it is even worst, now it is replacing cards completely, by duplicating others.
Here is a video which shows the issue exactly, I have more cards, all are different, but somehow he is replacing "AMBIENT" card with "LIGHTS" card, it is creating a duplicate by replacing the existing one (HA in normal mode). Take a good attention to "LIGHTS" card and "AMBIENT" card https://github.com/user-attachments/assets/9733e3aa-9df1-487c-97b6-e03e31551e36
Then, I tested the same card (nothing changed), but HA in safe mode. Same result, but you cannot see it visualy, with cards, you can only see the issue in the code change, which make the same issue by duplicating the card, by replacing the existing one https://github.com/user-attachments/assets/78096e0c-6921-49a9-8a1e-f8206b1e8a54
The thing is that even without this issue, the UI editor had some issues by not refreshing the card I select, and always I needed to do like in the safe mode workaround, clicking other card then back, to see the proper card... But, as I said, it is getting worst...
Checklist
Describe the issue you are experiencing
When I edit something in frontend, I get some very strange bugs, this is happening from the 2024.11.x version, but with 2024.12.x it is even worst, now it is replacing cards completely, by duplicating others.
Here is a video which shows the issue exactly, I have more cards, all are different, but somehow he is replacing "AMBIENT" card with "LIGHTS" card, it is creating a duplicate by replacing the existing one (HA in normal mode). Take a good attention to "LIGHTS" card and "AMBIENT" card
https://github.com/user-attachments/assets/9733e3aa-9df1-487c-97b6-e03e31551e36
Now, here is the workaround
https://github.com/user-attachments/assets/5626215a-4987-4271-bee7-cd0b41bf2163
Then, I tested the same card (nothing changed), but HA in safe mode. Same result, but you cannot see it visualy, with cards, you can only see the issue in the code change, which make the same issue by duplicating the card, by replacing the existing one
https://github.com/user-attachments/assets/78096e0c-6921-49a9-8a1e-f8206b1e8a54
And, same as the first sample, here is the workaround
https://github.com/user-attachments/assets/002def50-78ec-44f4-aada-08d2cc59bc4f
The thing is that even without this issue, the UI editor had some issues by not refreshing the card I select, and always I needed to do like in the safe mode workaround, clicking other card then back, to see the proper card... But, as I said, it is getting worst...
Oh, wait, here is the cherry on (top of) the cake :-D Making more dupes
https://github.com/user-attachments/assets/3613cd67-bceb-4769-8f79-04d3222b6e65
Describe the behavior you expected
E expect to work without replacing other cards and refreshing properly when I click another.
Steps to reproduce the issue
It can be seen in the videos
What version of Home Assistant Core has the issue?
Starting with 2024.11.xx and getting worst with 2024.12.xx
What was the last working version of Home Assistant Core?
100% was good in 2024.9.xx and could be good in 2024.10.xx but I forgot
In which browser are you experiencing the issue with?
All of them
Which operating system are you using to run this browser?
Windows 11 (but this is happening on any other OS)
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
The text was updated successfully, but these errors were encountered: