Like almost all FOSS software there’s a way to contribute revenue. Nabu Casa gets paid (by me) to provide a link to google that saved me the trouble of setting it up. I could have done it myself (well, it’s recently changed, so not 100% sure is still true) and paid nothing.
When any of you decided to use haos you decided to give someone else executive decision. And that is exactly what nabu casa did. They decided that doing backups in other way is better for end user.
No one forced any of you to use haos. You could also use docker and set everything up, including backup, the way you want it.
Look man I just gave my opinion. As i said, in docker you can set everything up the way you want, like, including backups, updates and everything else.
If this is to hard, to complex, to time cosnumimg, then let somone else do it for you.
But then dont cry around when that someone decide to do some things different.
It doesn’t matter which installation method one has chosen, 2025.1 removed backups before updates (and 2025.1.1 removed an additional frontend option that was missed in 2025.1), and added a new automatic backup system that has mandatory encryption. Using HAOS, one can still, (with more effort than versions <2025.1) manage backups using a variety of methods. That’s also true of Docker, venv, and supervised installs.
And just by the way… No, it’s not that complex. I used Docker in the beginning, but the advantages of VMM outweigh the disadvantages for me. If it’s too complex for you, then seek technical help to switch
It does matter because i wasnt affected by those backup changes as i never was using built in backup solution. Nor i have to. I wasnt affected with lates z2m changes.
You keep using that word, free. I do not think it means what you think it means. And calling it “contributing”, does not negate that you are, in fact, paying for HA. A rose by any other name and all
Your original implication was that people should be thankful for whatever the devs provide because it is free. The devs, who are employees of NC, get paid. You can qualify all you want, but your thesis is incorrect.
I’m genuinely glad you were not affected because you had a backup solution in place that works for you. No reason to be defensive. My point was that a person’s chosen installation method (HAOS, Docker, supervised, venv) was what didn’t matter (you had stated that it was the choice to use HAOS that gave someone else executive decision). With any installation method, one could have used the built-in backups, or rolled your own backups using a variety of methods. And with all of them, 2025.1 introduced changes that do affect many people, if not you.
Ok, but I just wanted to point out that everyone is choosing their path.
It was not easy for me to start up with docker that I was never used before nor im it pro.
But I invested my time in learing how to do things around.
With a recent changes that proved to be a very good decision.
In my point of view, if I could do it then any man next to me can do it.
And I can suggest to everyone here to invest in them selfs and became the one that will make decission for themself. And than there will be no problems like this.
What I wanted to say is that with Docker I have zero advantages in terms of data backup compared to a VM, but there are glaring disadvantages in itself. Of course, external backup options are available to me and others.
But it doesn’t matter, because this thread/issue is about the integrated backup solution.
This is not true. It’s it is obviously that you never used docker and you don’t understand the possibilities that docker solution give it to it’s users.
I wish I could see the feature work, but the backups screen is entirely gone as soon as I upgrade to 2025.1.* ; I can still restore the backup through the CLI, but there is no visual interface available.