Not saying it isn’t
Murphys law: what can happen will happen
Not saying it isn’t
Murphys law: what can happen will happen
To someone at the absolutely worst possible point in thier use of something…
Remember that part I said about black eyes? That.
Way too much risk. I used to think it should have been held. THAT needs patched. Immediately.
To make backups feel easy here is a visual suggestion below for a one click quick backup. Add one or more buttons which will always save to local storage.
I actually opened an issue during beta, thinking that it could not be intentional but a simple bug.
Paulus answer was that it was meant to reduce the risk of running out of space…
I mean… what can I say ?
It’s like someone lost touch with reality and best practice.
Now we have to remember to manually backup our add-ons before every update !
I thought HA’s purpose was to actually automate things.
Oh well…
Yes. I it was a hint and proposal before and everyone had the choice to unselect before. Best implementation.
The solution to OpenRGB integration is on this PR. Just follow this description on how to update the code.
Indeed a very strange choice, because at what time is the risk of something going horribly wrong at it’s peak?
A full backup includes a copy of /config
Unless your custom_components directory is somewhere other than /config, then it would be backed up. HACs is a custom_component.
If you are missing that then something else has happened.
You can create an automation right now using the hassio.backup_full action, schedule it how you like or triggered by whatever you can come up with, and choose not to encrypt it by not adding a password. Nothing has changed there.
It has always required a script or third-party tool to decrypt outside of HA so that is not new:
Like this:
Or this:
When one chooses to follow a particular practice, I guess it’s fair to say that one is adhering to an “ideology”.
“MVP” seems to be the one that is often mentioned when the community asks “Why is this new feature half-baked?”
Seems to me that if customers often find the result to be disappointingly under-cooked, the chef ought to adjust the cooking technique.
Apologies, forgot everything encrypted, so shows 0 byte length when diving into the tar files.
So we have a custom encryption, that:
Hmmm, strange things happening.
@madelena The recent problem with HACS: After HA update to Version 2025.1.0 HACS is not starting: “custom integration ‘hacs’ sets option flow config_entry explicitly, which is deprecated at custom_components/hacs/config_flow.py” #4314 points out one of the use cases for being able to access and restore individual files.
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.
It’s coming from cache, refresh your page.
thank you, took a force close to get it up. I have edited OP.