Seems to me the system is just trying to inform you of something better if you want it. Those entities it triggered on may exist even without solar and prob why it popped the repair.
If you don’t need it then… Just hit ignore?
My thanks to all of you, sorry I missed that in the deprecated list, thought I didn’t use themes!
All working now.
Best regards, Colin
I got hit by this one as well. This one seems like it’s going to be ‘fun’ to go through and fix.
Oh well, I already needed to go in and update my ESPHome devices due to other recent changes, so, guess this’ll make that higher on my priority list (FML)
1 Like
Do you backup before updating?
For me. The backup part takes 20 minutes. While the actual update only takes 2
Nope. Backup is disabled. Update to 5.1 took almost half an hour.
Faulty scrolling badge fading still happening in 2025.5.1
This PR was included wasn’t it?
How do we dismiss the new “Home Assistant cloud backup” advertisement? I specifically do not have default_config: or cloud: in my configuration.
3 Likes
I use Docker. How do I take advantage of the automatic backups before updates? I update by pulling a newer image, not through the UI, since it’s Docker.
Sidebar broken (using LCARS Theme)
Is this theme related (due to the style-changes) or something general?
Does someone know a fix?
This update changed a lot of the sidebar and other UI code, so the theme probably needs to be updated to support it.
1 Like
You cannot. I used to run it in Docker and I just had an update button in the UI that used the shell command integration to pull the new image and rebuild the container; you could probably create a script in Home Assistant to take a backup and then run that command and trigger it via a UI button.
This is a custom theme. Suggest to ask in the corresponding repo. Perhaps the theme should be updated to new HA variables.
1 Like
Any suggestion how to put the badges at the bottom in YAML?
Likewise, broken for me as well coming from 2025.4.4. Will hold off upgrading as I have a lot of local Tuya devices.
Wonder if there will be a fix applied in 2025.5.1 to save having to muck abour?
1 Like
There is already an update for Local Tuya in Hacs
1 Like
Thanks for the heads up.
Nothing showed up under updates but as suggested I manually downloaded via HACS, & did a restart once installed. All tested well. It updated my existing from 5.2.1 to 5.2.3.
I’ll update my Primary HASS now. Thanks again. 
Mmm, I checked HACs and 5.2.4 shows as downloaded.
If I go to Settings → Integrations → Add Integrations, it is there BUT if I select to install, it wants to redo everything. Isn’t there an “update” method as the one earlier worked fine and seemed to Auto do it from HACs from 5.2.1 to 5.2.3. A tad confused now?
I’m sure I updated to 5.2.4, but indeed, if I check the integrations page, I see
I would not worry about it, as long as it loads.
A breaking change I had, that I didn’t see mentioned:
If using the Xaiomi Mijia ZigBee button (the one shown in this image, and using the unique_id for anything, you need to add _CLIENT after that ID.
Before 2025.5, the event from a Xiaomi button looked like this:
event_type: zha_event
data:
device_ieee: 00:15:8d:00:02:3c:d3:3c
unique_id: 00:15:8d:00:02:3c:d3:3c:1:0x0006
device_id: c8fb76c582bd0beb8f23ef31e2b262c2
endpoint_id: 1
cluster_id: 6
command: click
args:
click_type: single
params: {}
origin: LOCAL
time_fired: "2025-05-11T10:00:06.923185+00:00"
context:
id: 01JTZCK80BHYHSK3TRPNMVGN22
parent_id: null
user_id: null
After, it looks like this:
event_type: zha_event
data:
device_ieee: 00:15:8d:00:02:3c:d3:3c
unique_id: 00:15:8d:00:02:3c:d3:3c:1:0x0006_CLIENT
device_id: c8fb76c582bd0beb8f23ef31e2b262c2
endpoint_id: 1
cluster_id: 6
command: click
args:
click_type: single
params: {}
origin: LOCAL
time_fired: "2025-05-11T10:00:06.923185+00:00"
context:
id: 01JTZCK80BHYHSK3TRPNMVGN22
parent_id: null
user_id: null
So automations stop working for these devices. I don’t use other Xiaomi Mijia ZigBee devices, but I would suspect that it could be an issue for others as well.