Case in point, my supervisor just now updated to 162 in the middle of the day meaning HASS restarted. At the very least, it would be nice if the update happened at a specific time of day.
Also leads to issues such as this one where an error shows up in the logs that is totally harmless and due to the Supervisor update but is treated like a problem when we don’t realize it’s because Supervisor is updating automatically:
Block these and there will be no updates for anything because it won’t be able to check for them:
Stable:
https://s3.amazonaws.com/hassio-version/stable.json
Beta:
https://s3.amazonaws.com/hassio-version/beta.json
You would also want to turn off auto-update for each addon.
You may find yourself in a situation where an update for an addon depends on an update to the supervisor or HA, or an HA update breaks because the supervisor wasn’t updated…there are several possible combinations here, so be mindful.
1 Like
Just chiming in after the recent 180 / DNS issues.
All of the add-ons have the ability to turn off automatic updates, so IMHO this feature request is just making the supervisor updates follow the same concept.
I want to control my home - that includes the software too 
Perhaps the idea is to ensure that users don’t start raising tickets on conflicts with outdated components, but that can be managed… and would possibly cause less trauma to the Devs when sudden updates cause chaos 
As others have implied, I think most users would perform updates, but when it suits them to have scheduled downtime.
2 Likes
I would add that as well that as hassio addons can have the ability to check the minimum required HA version, it wouldn’t be so hard that a HA upgrade checked the minimum supervisor version…
2 Likes
I didn’t see this original request and created another one ([supervisor] option for disabling auto-updates - #9 by frenck). Now that it’s closed I’m voicing my concern here instead.
The concern is that if you’re relying on HomeAssistant for important tasks or alerts when you’re not at home you’ll potentially loose control without being able to act/fix it. For instance if you’re on vacation or just left for work when the update starts.
I suggest adding an option in the GUI for disabling automatic updates just like for hassio-addons. That way you could safely update when you’re in a position to fix it if any problems arise.
Here’s some examples of problems causing headache for a lot of people after the 207 update:
The suggestion to just block the URLs used for checking for updates is not ideal in the long run. Would like to hear the codeowners thoughts on the predicament, but I’m not sure if it’s ok to tag them here. This seems to be a reoccurring situation, so hopefully we’ll find a solution that works in the end.
2 Likes
Same here, my installation just broke because of the auto update. I didnt update anything for the past 6 months because it was working smoothly and I was not planning updates because I had all the functionality I wanted for my house…
yes please
Make this please, some updates broke my setup…
now we should block version.home-assistant.io since https://github.com/home-assistant/supervisor/pull/1161/files
You can. It’s a bad idea.
I dont think so
Since my HA isnt updating anymore i am very pleased and stress free.
I keep smiling whenever i see something like such Topics " [Home Assistant wanting to downgrade from]"
Remember dont fix ut till its broken.
Whenever i want to try an update i can - whenever i dont want it i can aswell.
2 Likes
Please implement this feature! 
Adding my agreement for needing this feature. My home is rock solid except for on a few recent occassions such as this morning when I wake up and nothing is working. Sure enough, an auto supervisor upgrade didn’t finish smoothly and broke my node-red integration. A reboot of the system worked, but this wouldn’t be necessary if supervisor was manually upgraded just like HASS itself. We do addon dependency checks for HA version, couldn’t the same be true for Supervisor version? @frenck
I’d really like to know why the development is reluctant to do this? I dont want to block URLs either becuase I’d prefer to see that updates are available and decide for myself if it’s worthwhile to upgrade or not.
Thanks!
1 Like
This will be more important now that they’ve dropped support for generic linux install. I want to freeze my supervisor and system on this version now.
1 Like
I posted some new information on this topic: https://community.home-assistant.io/t/how-to-stop-supervisor-auto-update/132271/18
Can’t paste the same information here because of the spamfilter.
Auto updates need to turned off. When you’re using HA as part of an alarm system the last thing you need is to walk out the door only to find out you’re alarm system has been dead for days because of some auto update. I left my house today and everything was fine. Came back two hour later and my system had crashed. On reboot none of the containers restarted. I had some docker error about overlay2 issue and failure to mount. Looking at syslog the last message that was stored prior to the system rebooting:
May 29 08:27:09 odroid hassio-supervisor[8681]: #033[32m20-05-29 12:27:09 INFO (SyncWorker_19) [supervisor.docker.interface] Pull image homeassistant/aarch64-hassio-supervisor tag 225.#033[0m
So an auto update killed things. The only way I could fine to fix things was to remove all the containers and re-install them, along with all the addons I’d installed. I’m running the supervisor version on Ubuntu 18.04 on an odriod N2. It’s great platform for HA. Please move this up on the feature list. I took rockyou’s suggestion and hopefully his suggestion will fix things. On my system the tasks.py was down another layer under the misc directory. Please do not force auto updates.
1 Like
I understand why people having this issue.
But, also please don’t forget the other side of the coin:
Homeassistant is still in active development. It isn’t at the “stable” 1.0 target version yet so you’d have to keep in mind that any nabucasa cloud backend could be updated and no longer work with local installs that are lower than 0.xx.
Saying that though, I do also think it’s should be an option where you can opt out (on by default), but with an “on your head be it” kind of warning.
My system was killed by the auto updates for a second time this year, after hard reboot I cant even SSH into it anymore…