Bugs and edge case problems will occur from time to time with a system as diverse as Home Assistant. While Ludeeus was able to quickly get a fixed version out that avoids the issue, that doesn’t always happen and workarounds may be necessary.
Users who possess the necessary skills shouldn’t be forced to revert to a previous backup and lose data if a workaround exists.
Note: This isn’t a case that would be covered by version control over user configurable data.
Agree T… I work in IT services and have for the last 10+ years.
I have literally yelled at an architect because they threw MVP at me as the answer. It went something like this…
MVP / Agile / Devops wordsalad is not license to run fast with scissors and doesn’t help the end user. You just beta tested a feature with your user base without telling them you did. Full stop.
If you’re going to MVP something be very thorough and clear in the messaging BEFORE you do so. Because now we have to fix your botched feature AND regain the user trust we just lost.
I swear I can just copy paste that here. And ha did it with BACKUP of all things… *Face-palm
I’ve been on HA for a lot of years now and this looks like the most problematic release I’ve ever seen. That is both in terms of solidity of the function and design choices. I have confidence this mess will get cleaned up but I also hope the core team takes a beat to do some self analysis on why. I’ve been in software design for nearly 60 years and I have seen this movie before. My advice to the team - stop being defensive, drop any notion of arrogance, and just figure out why this happened. Then perhaps revisit you architecture and release decision processes. These things happen - but the wrong response to them can only compound issues and lose trust.
Even with everything new, we’ve made sure to keep everything backward compatible
My expectation of backwards compatibility is that backup features where extended , not a MVP that breaks existing features ( a deja vue with the new badges last year. Weeks of tender and care to style badges where lost.)
I stay on 2024.12 for now and hope mandatory fixes come in quickly.
Some big overhauls like backups just need more beta testing flight time than can be done in one month cycle.
Seems to be a common issue. Speculation is that having all users upload at the same time might not be the best idea
However I find it more irritating that it will only try again on the next scheduled update (which could be a week away). In my opinion it should try continuously with some (of course randomized) backoff time.
It should be noted that the mobile app does not present the “set up backups” dialog nor give you the encrypted backup dialog when making a backup from the button in the lower right.
instead it brings you directly to all backups on your system and still presents the “password” backup dialog and not the new dialog. I imagine this is coming in an updating version of the mobile app.
edit: I stand corrected, for any that are also seeing this. Force close the app and reload it, even though I left the page and it reloaded everything it didn’t pull the new dialogs until I forced closed.
I agree with you 100%. I am an Architect and if I never hear DevOps, Agile, MVP, and such again I will be happy. What people don’t admit is all of these things are admissions that we do not know what we are doing. Let’s try something and see if it works. I am OK with Agile/MVP for UI. But core functionality has to be right and complete. If I design an MVP database and let developers go at it, I can never change it again. This is because even a simple data structure change will require extensive regression testing and probably code changes.
I will get off my soapbox now. I really do appreciate all that the Nabu Casa team and volunteers do. If I ever get some free time, I will pitch in to help.
I have no dog in this fight because I’m way back on 2024.10 and never used the backup feature. However, I do want to point out the irony of the recent Community Survey, followed up by this backup situation which partially stems from not listening to the community
Still using my old backup strategy with services calls instead of the new automatic backup until the ssl and local addon folders get included in the backup too.
Please consider making encryption as an option that can be turned off…
Really this shouldnt be pushed like this…
I always copied tar.gz files to my windows/desktop, extract (!!) it, to have also local backups on my pc, and for developing etc etc. compare with winmerge etc…
Also dont get it why needs to be ecrypted, ok maybe until uploading to cloud or whatever… but local backups, come on…
Nice! I haven’t tried it (since I reverted back to 2024), but does this action prompt for a Name, or is it set to random by HA (like the actual disk file names)?
It does not prompt, set a static name that is used in the db for the UI. The file does actually have the system generated file of 8 characters plus the .tar extension
Edited for more clarity.
OMG, Agile… I began programming on the Apple II doing “Poke” commands to alter RAM one byte at a time, and everything since from Asm, to C, to C++, even Ada. We sat down and thought about what we wanted/needed to do and actually designed SW, often creating an entire document describing it in detail. When I first ran into Agile I recognized that the paradigm had drastically changed from thoughtful, purposeful SW design and development to lazy-trial-and-error-see-what-sticks-let’s-get-this-out-the-door-and-let-the-user-as-tester-tell-us-what’s-broken approach. I’m truly glad I no longer have to code for a living, with the scores of “hey-use-my-new-language” syntax options that add zero value and the multitude of frameworks in use today. I’d pull my remaining hair out. It’s a wonder anybody can get a job anymore! But I digress.
If this is the case, then clearly not much critical thought went into this whole new backup thingy. Solution: increase Nabu Casa dues to $300/mo to pay for more Amazon Cloud bandwidth!
There was a survey? Not listening is not a new fault, IMO. I backed away from active involvement in the HA community & beta testing some time ago for that reason, and hoped it would improve over time. Although there have been lots of not-so-obvious system-level improvements over the years (yay!), I’ve seen little in the way of new features added that benefit my particular needs or set up, so it has remained basically unchanged for 2 years. Many new features seemed unnecessary and very specialized to me, or even a step backwards in a few cases. I still support Nabu Casa (for now) but am just an end user at this point. But I still do all of my automations in YAML!
I began programming on the Apple II doing “Poke” commands to alter RAM one byte at a time, and everything since from Asm, to C, to C++, even Ada. We sat down and thought about what we wanted/needed to do and actually designed SW, often creating an entire document describing it in detail. When I first ran into Agile I recognized that the paradigm had drastically changed from thoughtful, purposeful SW design and development to lazy-trial-and-error-see-what-sticks-let’s-get-this-out-the-door-and-let-the-user-as-tester-tell-us-what’s-broken approach. I’m truly glad I no longer have to code for a living, with the scores of “hey-use-my-new-language” syntax options that add zero value and the multitude of frameworks in use today. I’d pull my remaining hair out. It’s a wonder anybody can get a job anymore! But I digress.
If this is the case, then clearly not much critical thought went into this whole new backup thingy. Solution: increase Nabu Casa dues to $300/mo to pay for more Amazon Cloud bandwidth!