Feature request: block supervisor auto-updates

[night]

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:

Supervisor not starting after update to 207

Supervisor Won't Start

I was about to show someone my Grafana graphs in HA when I started getting the ‘Unable to load the panel source: /api/hassio/app/entrypoint.js’ error. In researching, this appears to be related to hassio-supervisor not running. I am able to SSH into my HA server and supervisor is not running. A restart will show it trying for 5 seconds over and over again until I stop it. I rebooted the whole server and none of my containers were started, presumably because supervisor can’t start. I was able to …

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.