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.
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.
Workaround: How to stop supervisor auto-update?
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.
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: #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.
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…
My ‘supervised’ system also experienced issues (HA core wasn’t available) after yesterday’s auto-update. Fortunately, I was able to SSH to the OS and perform a reboot and then everything started up normally. I didn’t have time to investigate and troubleshoot, I just know that Supervisor is now on version 227 and believe that the auto-update was the root-cause of the downtime, since that was the only change.
I think I will be migrating to HA Core Docker because my apartment heavily relies on HA availability and I need to plan the downtime. The convenience of add-ons is great and a killer feature of the platform, but the trade-off of system stability due to the lack of control of Supervisor updates is a deal breaker for me at this time. I want a stable system and I want/need to schedule downtime on my own terms.
I think that auto-updating of Supervisor is in direct contradiction with the goals of most people who chose the generic Linux install method of HA (more local control)… This installation method is unfortunately the least stable option right now. With user-configurable updates of Supervisor, it wouldn’t be… Power-user / enthusiast crowd opinions, who are most passionate about the platform and spread the word of it’s excellence far and wide, are too easily being dismissed.
IMHO, generic Linux install should be left deprecated if Supervisor updates remain unconfigurable for the user.
Btw, this is my first post on this forum and I would like to use this opportunity to thank every single person who sacrified their free time to contribute to this wonderful project to make it the best homeautomation platform ever, I am extremely grateful. Thank you!
Is there a way to stop of supervisor an hassio auto update? It just breaks everything…
Short of blocking the update URLs at your DNS, nope.
There is a WTH for it though.
This would be a fabulous feature to have.
It’s tremendously frustrating to have a completely working system start (seemly randomly) having issues and not knowing why, only to find out that it’s because someone forced an update on your system.
I don’t see how Home Assistant could be trusted in any type of important situation until this is added.
That’s why I’m on this thread. I am spending the morning trying to track down issues with a system that was previously working fine. It led me to the supervisor, and to auto-updating and now to this. (The auto update happened sometime in the last few months, but I didn’t have physical access to trouble shoot the system until now)
The auto-update put my system in a situation where I couldn’t fix it as an end user without physically pulling the plug on my raspberry pi. (I was getting the error: Post http://supervisor/host/reboot: dial tcp 172.30.32.2:80: connect: connection refused)
I want to have an install of Home Assistant that I can use as an end user because I need it to be reliable. So I followed that path for my install and setup. I used one of the install images with Home Assistant OS and Home Assistant Core for Raspberry Pi. But now I understand that if I want to use it without having to worry that it might break on it’s own, I need to block version.home-assistant.io at my router. That seems weird to me.
Adding this feature would be a significant step toward making Home Assistant more end-user friendly, just like the GUI setup.
Do we have any news regarding the disabling auto update for Supervisor?
Any news on this? Yesterday it tried to update and failed I couldn’t get in Home Assistant anymore at all. Very frustrating!
I want to chose myself when I update.
Agree that we need the ability to prevent auto updates.
What is the issue in the development? Is it so hard to implement a switch to enable or disable auto update? It is not very funny, if I am not at home for a long time, Hass is not available because of restart issues after some supervisor issues. I should be able to control the smart home and not the smart home should control me.
In General I have no idea how to make the supervisor available again, because I am not a Linux or docker specialist.
To setup a very new Hass every time and to try to restore an old backup could work. But it is also time consuming and not the best way.
Seems no one cares