Automatic backups are a work in progress, and it will continue to be improved according to feedback and usage over the releases. Please be patient.
As for any software products, the best practice is to release early and get feedback first, rather than developing behind close doors for months without user feedback in the dark. This is what āMVPā is about. Itās not just a jargon. Releasing it now also allows contributors to build integrations to integrate HA with more backup locations.
And I mean, youāve been around long enough and you should know that the contributor team does listen to feedback and continue to improve the product over the months and years. Itās never an āus vs themā situation, and itās not a black box either - encrypted backups have been on the roadmap since April. And 2025.1 is not going to be the only update on backups in upcoming months.
Also, the beta was done over the holidays. Contributors have families and friends, too. Even though these features arenāt implemented for this release, they are being prioritized, and if features canāt make into this release, there will always be another one to fix whatās missing. These are not mandatory upgrades. Please understand and be considerate that contributors are people, too.
With that said, hereās something that all of you can help!
To make this a productive conversation, it will help guide the development of the backup feature, if those of you who prefers unencrypted backups can help describe your use cases and reasons behind the need. For example:
- how often do you open your backup archives?
- What do you open it up for?
- How often do you need to restore your backups?
The more details the better! This will help guide the UX and help the team prioritize and develop the features correctly! Thank you.