I had the same problem. Removed and added HACS again. After that I had to download all integrations and cards again. For some I had to add the custom repositories again, before I could download.
Now all works as before, but this 2025.1 update was a shitty one. Would expect better quality control by the developers.
Wait… are you saying that with the new backup system, even if manual and local, that I can’t get into it to parse out individual files, but my only option being a full restore? If that’s the case, then I may revert and never go beyond 2024! That’s ridiculous!
Please tell me I’m wrong.
EDIT: I just successfully reverted to 2024.12.5. I’ll wait to see how this sorts out. It appears I’m not the only one unhappy atm.
I’m another one here.
Oh, it’s small all right, 0 bytes when my NAS is asleep :).
It’s got dozens of terabytes of free space, though, while each HAOS backup is only about 1GB, so minimizing the backup size is not an important goal for me. Minimum the power consumption from the NAS, as well as the noise from the platter based hard disks when I’m in the room, is more important, and that is why I use autosuspend on Ubuntu and WOL on clients that need to access the NAS.
Of course, I could switch every single client to backup at 4:45am instead of the current 2am, but I feel like the flexibility to choose a different time should be there, as it is in Samba backup.
Feedback taken. Interesting
Ha! Yeah, now you see the issue.
There is a python script. I assume it still works as the encryption has not changed, just uses an automatically generated key string instead of user set password. See: Backup/Snapshots no longer decryptable? - #12 by Taapie
Mandating something should not be part of an MVP philosophy. That is akin to ideology.
Because it was removed but we still have the harder to set up but extremely reliable option of MQTT. I’ve only had to make one small tweak to the yaml in over 3 years.
Yeah got that, someone already pointed it out to me.
This update is great, love the new zooming function for the time series data, but it’s not implemented correctly on mobile (still some bugs when using touchscreen instead of mouse). But the real problem for me is that 2 of my integrations stopped working: OpenRGB and AIMP, so i cannot control the RGB on my keyboard and cannot set the music using HA, which is kind of a bummer…I had to restore my HA instance to an older version, and voila the integrations are working… 
Never had to restore to an older HA version before and i’m using HA 5 years++.
alias: Create Backup at 6am
description: ""
triggers:
- trigger: time
at: "06:00:00"
conditions: []
actions:
- action: backup.create
metadata: {}
data: {}
mode: single
This automation creates an unencrypted backup to the local file system.
I think my guide is slightly more up to date and it’s not archived yet.
https://www.reddit.com/r/homeassistant/comments/pwa3nv/energy_tab_with_dte_energy_energy_bridge/
Too many breaking changes. Kills the Victron App and a few other things
Both of those are 3rd party integrations. If you want them fixed you will have to open an issue with the 3rd party developers (if there isn’t one open already).
As said before, encryption for local backup is pointless, doesn’t increase security. Make it an option for local and NAS and mandatory for the cloud.
So still using the Samba backup add on. 
Thanks, but in my case, i use the tv backlight with wifi. the only way i see is via the cloud. Hope, there will be a fix for govee
Mee too… After updating today, the custom ecowitt integration stopped working for me, but if I go through the “official one”, it still displays “Config flow could not be loaded: {“message”:“Invalid handler specified”}” as it has always done… So why is the integration there if it doesn’t work? Or is it some other specific problem that just some people have?
The problem is that the OpenRGB hasn’t been updated over 2 years and the AIMP for well over 4 years. So not much i can do, also what changed in the main code that broke so many integrations? Python version? There isn’t any mention of this in the breaking changes section of the 2025.1 release. I always read it before updating but i thought this update won’t break anything, but i was wrong…
I have a Meross thermostat (mts200) but it was detected by the homekit integration when i first installed it, and that did everything I needed.
You may want to stick with Meross cloud, but Homekit might be a viable alternative for you if you’re stuck.
Probably time to say goodbye to AIMP. The dev is not active.
The OpenRGB dev is still around though. Open an issue and see what happens.