No - there is a need for an option to continue to backup unencrypted. Many of us have use cases where encryption does not make any sense, and only adds net negative value.
So I am adding my voice to those asking for unencrypted backup options.
No - there is a need for an option to continue to backup unencrypted. Many of us have use cases where encryption does not make any sense, and only adds net negative value.
So I am adding my voice to those asking for unencrypted backup options.
I am also adding my voice to those asking for unencrypted backup options.
just use the Action
action: hassio.backup_full
this creates unencrypted backups
This is not available in every installation type.
I’m experiencing an issue with the new backup system in 2025.1 for the second night in a row. While the local backup is created successfully, the upload to Nabu Casa fails consistently. Manual backups works and uploads to Nabu Casa.
From what I can tell, the issue seems to be specific to the upload process to Nabu Casa. My internet connection is stable, and other cloud integrations in Home Assistant are functioning correctly.
Is anyone else experiencing this problem with Nabu Casa uploads in 2025.1?
The customer is always right…
I’m still amazed there isn’t a decent/advanced scheduler like schedy included in core.
You will if you can’t find the encryption key next time…
They will appear in the HA Log at startup. Always worth checking the log on a regular basis.
Agree - 400 comments are a lot.
All the devs have to do to stop the bitching is to say - don’t worry we will offer a local unencrypted option
Having said that - HA is for free, so I am in no position to demand anything from the devs - they built this fantastic piece of software - and I will be thankfull to them either way.
I know. But for this and many other, there aren’t such pre-infos. That is, what I wanted to say.
Free - yes and no - not if you subscribe to support the project, you expect a little back. Yes I’m thankful as well for HA, but this isn’t the first instance of the Devs being a little deaf to their user base.
What you get back is a simple and easy way to setup remote access, and now also cloud storage.
Man, the changes to graphs and being able to set category and label upon creation looks amazing (!), but going to stick to 2024.12 until the backups are sorted out.
I don’t want forced encryption for locally stored backups.
Happy Nabu subscriber for years but my backups are 5.1GB so as it is now the cloud storage options doesn’t even allow for a single backup…
Backup is absolutely key, and I also (so far) relied on 3rd party integrations.
Key is of course to back up to a totally different medium. It does not help to backup onto the same harddisk where the original system is on, when the disk itself might be subject to failure. Also, I’d like to avoid using another disk (SSD, whatever) attached to the same HA server when e.g. there is a flooding or other damage to the system itself, thus I am always doing backups to a physically different location.
I use so far Nextcloud as a potential target, i.e. having geo-redundant backup storage.
Key is also the Restore function - I hope that future releases also look at this, so an easy way of restoring an encrypted backup is part of an initial, maiden system startup…
Thx for the precious work on a highly-relevant topic - and a Happy New Year to you all!
Why would you skip this version based on a new feature that you don’t have to use?
To me it seems a bit risky updating. Will my current scheduled automatic backups to GDrive (the Add-on) continue to work as they do now if I don’t touch the new normal backups-system? If I can continue to use that without bothering with the new system then I might upgrade. Unrelated to backups, there are some users reporting issues with modbus, climate/smartir and HACS which also makes me a bit nervous.
That was indeed a bug. It was noted during beta testing, but as HA does not control 3rd party resources it was not mentioned in the release notes.
There is now a fix available. Check your updates.
This thread doesn’t need yet another ‘vote’ for unencrypted backups so I have held off.
What really staggers me though is despite this being just about the hottest topic I can remember over the last seven years, except perhaps a few years ago with the fears of yaml configuration going away or if I recall correctly MQTT being broken by an upgrade, is the complete lack of any communication from Nabu Casa except a slightly ridiculous, after the fact, request for information.
On the other hand I shouldn’t be staggerred, it is fairly par for the course with NC, one of the reasons I very reluctantly stopped my subscription. Everything that comes out of NC in the form of product/brand communication is exactly right and exactly what I want to hear and what I want to support.
It is some of what isn’t said and some of the actions that can be questionable.
But Petro is right, if you are commenting here the least you can do is give answers to the quetsions.
And for the record I have a timed automation that calls hassio.backup_full
.
So from what I’ve read I am going to be ok if I can pluck up the courage to upgrade - the card-mod
issue is another big one for me though.
(EDIT: tom_l posted while I was posting. Seems I should be ok with that one too!)
(EDIT2: Maybe not…)
The entire HA backup folder on my PC is included in my scheduled backup to NAS job
This way I have 8 days of full backups as well as two days of plain text backups of all my yaml for much easier and quicker access.
On three different machines and off site too if I choose to include the backup folder as part of my OneDrive
except that fix introduces many more issues… also because of unannounced changes in several core frontend cards (that needed to be incorporated in the custom card-mod apparently).
We can now mod badges easily but have a lot of other things to fix……
fwiw, and awaiting true debugging time, there is also a small edit we can to to get card_mod up and running again.
this could have been communicated so much better, and would have, if the team truly felt it needed to known its user base, or whatever the title of that query was.
btw Tom, I’ve stopped using the word ‘Bug/issue’ here, because the stance of the team is this (custom stuff) is not supported anyway, and they see no need to inform their user base.
All open source and out in the open, so you can follow along in the GitHub, that is just about it.
Which ultimately is what makes using HA such a problematic thing if you need more than the basic options of unmodded core/frontend, and blindly update