Well - another user reported he was not able to restore an old backup on a 2025.1 system - so forgive me for being silly !
Iāve rescued myself from errors a few times by simply copying an original file from a recent backup. The automatic backup just before any upgrade was also very useful as a fallback, and it seems that is also missing at the moment, which seems like a major oversight. I agree with most of the others whoāve commented: Encryptionās fine for cloud backups, but not needed for local.
I guess Iām also going to stick with 2024.12 for now as this all seems like work in progress that isnāt going to help most people in its current state.
confirmed.
using the Google Backup add-on to do exactly that. Iāve disabled its creation of backups, but use it now to upload all automatic backups to my Google drive and have some versioning control. even still accepts the settings for ignoring partial backups or not, and all the other goodies, like the stale sensorsā¦
seems a great match, the new automatic and encrypted upload to the cloud, and sync using Google backup
to each their own, so feel free ofc. thereās only one person in charge of your system
That user though was in very specific circumstances making life difficult, and, also reported he managed to pull it off after allā¦
so impossible it was not
why ofc?
Did I offend you in some way?
No other way around. Tried to restore my 2024.12.2 backup to a new 2025.1.0 instance without succes
Edit: o wait what you say is true too. Couldnāt use the backup that would downgrade it too. I thought it was because of the mandatory passphrase not being used in the old backups? But maybe thatās not the case.
no? why d you ask? ofc=of course? so I honestly confirmed what you wrote.
o dear, no, not my intention at allā¦ I always use thatā¦ aarghhh. not much of a slang user here I am afraid
This change:
removed a deprecated method for handling media player features. My guess is that youāre using a media player platform that still relies on the old method ?
Apparently āof courseā is the more common interpretation and it is what I thought it meant. TIL the otherā¦
Thatās a straw man, surely? The feeling in this thread is that the community wishes the contributors had prioritized spending time with family and friends, over working on this MVP.
pff, good to know Tom, thanks for saving my dayā¦
A PR has been raised to add Google Drive integration for backup
Add Google Drive integration for backup by tronikos Ā· Pull Request #134576 Ā· home-assistant/core
Iām not 100% sure, but previously if you added a network storage folder in settings and pick that as default backup storage, I think it is created there right away. At least I saw a file being opened there as soon as I start a backup. And there also was no local file.
I am confused by the new functionality though and havenāt had the time to check it out fully. Even with my default pointing to a NAS, I now have checkboxes for local, NAS and Cloud. I have no clue which one is first now and which get copies. Or if local even works when the default is A share. Or on which of the three it will delete old ones.
You didnt miss anything.
That time is hardcoded and cant be changed.
Yes, but you can still use rclone, samba backup, Google drive backup and next cloud backup.
My point being there is no vendor lock in conspiracy as suggested by some
Yep saw that. At the moment only locations are extendible. Other options may or may not happen. e.g. time of back up, encryption on/off, different numbers of local and remote backups.
Yeah for sure. I wasnāt arguing you canāt continue to use them for now. Iāve even said so a few times in this topic. Apologies for seeming to argue against your main point. That was not my intention.