There’s an add-on that checks the config against the next version of HA, called Breaking changes or similar. One way of making this less fragile would be to make use of that to refuse to update HA if there were any issues with the config.
Obviously you can’t do anything about HAOS or the Supervisor that way, or any other add-on really, but it’s better than nothing, and covers the most likely reason people would wake up to a dark and cold (or hot) house.
This is the link for the add-on mentioned by @Tinkerer: GitHub - custom-components/breaking_changes: Component to show potential breaking_changes in the current published version based on your loaded components
There is also this one:
FYI - Here is a thread that has a solution for this:
So, there is my Auto-update Blueprint: Auto-update Home Assistant - Blueprints Exchange - Home Assistant Community (home-assistant.io)
Please give your feedback.
I can’t speak for others on here but I would never do auto updates because I enjoy the ability to continue tinkering at all. If everything broke regularly due auto updates with breaking changes I would’ve exhausted my supply of PAF a long time ago and my system would’ve mysteriously found itself in the garbage.
I do auto update other things that only affect me even if they sometimes break. But not something like ha which I want others in my house to adopt and enjoy.
Kind of weird logic here? Seems like the best way to achieve this is to never update. Not that I’m encouraging that but auto updates is a surefire way to ensure you have to think about your home automations regularly.
Not updating a static system that works is by far the best solution….
But for tinkerer’s like myself that is not really an option 
But i did notice that there are nowadays a lot less breaking changes then 2 years ago, however there was one now with node-red 
No. I’m running HA on the Home Assistant Operating System. It’s a specialized operating system that runs HA and nothing else.
For example, if you go to the Raspberry Pi installation instructions here https://www.home-assistant.io/installation/raspberrypi/- you can see how to download and install the OS.
Then you are in fact running HA in a Docker environment.
Every version of HA that includes a Supervisor runs in Docker. Unless you know how to look for it you won’t see it but it’s definitely there.
In fact, the Supervisor itself, every add-on you install and all of the other various assorted HA support functions (hass audio, cli, dns, etc) are all running in their own associated docker containers.
so yes, you have the ability to run Watchtower (as an add-on I think) and that will keep you up to date automatically.
Which is likely to be an even more terrible idea than normal and should result in a broken install in record time 
Yup.
I never said I recommended it. I just said it was possible for those die-hard ‘I want to auto update everything’ folks. 
I personally wouldn’t touch it with a 10 foot pole.
that sounds like home assistant regularly breaks with upgrades o.o
Thats not a good system 
Not if you bother to read the release notes…
to be honest i don’t.
it is not 1999 anymore … i expect my it systems to auto update and be on the newest version without the need of spending 15 minutes to log in to everything each day just to click the upgrade button -…-
And you figure that works with 1990 supported integrations (and a lot more if you include HACS).
There is no developer who has al those devices to test…
I myself wrote one integration on HACS, and as long as I have the device, I will support it…
But if it breaks down (or stop using it for whatever reason)…it’ll be the end of it, unless someone else pick it up…
I’m afraid that is the reality of an open source project that supports so many devices…
yeah i try to kiss - and therefor i am update stable.
and even if in 10 years there would be a break i can disaster recover in minutes by going back to the last snapshot of the vm.
i get your point and it would be ok to have the auto update off by default. But at least offer this option for advanced users.
But advanced users won’t be the ones to typically use any auto-update feature since they know what the pitfalls are to such a system for at least HA.
the ones more likely to use it are the ones most likely to not know how to recover from a broken system.
than make it an option you can only enable via ssh or what ever…
but not building this option in and force ppl who whish to be updated to waste time every day to manually upgrade if there is one is not nice
And the ppl you describe fall in the pits no matter what.
no one is being forced to update.
and if you do want to update then I’m pretty sure that the “Watchtower” option will work for every install type except the Core only install.
so if you want to auto update then install Watchtower.
that method also falls into your “that you can only enable via ssh or what ever…” request.
I think you are way overstating how much effort it takes to update.
usually the updates take a few minutes and I only update once a month.
there is absolutely no need to update “every day” even if there is one available.
that assumes of course that there are no breaking changes (intentional or not). If that’s case then it takes a bit longer to mitigate those.
But there again, those are the times I wouldn’t want to auto update anyway so the comparison fails immediately at that point.
Not if they read the release notes and take the breaking changes into account first.
of course there will be (and are) those that don’t do that before updating anyway. Nothing anyone can do can fix that.
An auto-update schema would just give those in the middle the false sense of security that updates are no big deal. until they are…
And again, even well tested software like Windows no longer forces you to auto-update and likely for the same reasons as stated in this thread - people were tired of waking up to a dead computer due to a failed update.
