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.
For anyone having trouble with HACS a new version (2.0.2) has just been released that should fix things.
not yet, but in preparation
Nooooo way?!? Who the ā¦ was thinking that local backups need encryption without possibility to decrypt?? Is that really the case? Thatās soā¦not nice 
Backups stored in the cloud, yes encryption is good. But local in same (for me) /usr/share/hassio for folderā¦ 
same here! I am using only Manual backups. Latest version introduced more mouse clicks and unnecessary setup. Not to speak of forced encryption for Manual backupsā¦
i have restore to old Version because these two ingtegrations dont work after Update to 2025.1: