Today my Home Assistant supervisor decided to update itself. Without any interaction. It just did, I saw it in the logs. It was 15:28:something. While it was restarting, my Mosquitto Add-on was not responding to its port, and therefore my MQTT broker missed values.
How is it possible avoid this from happening?
I wasn’t aware there are parts of Home assistant updating itself without my control or knowledge. I would have expected to see an update message resp. thought this would be installed with HAOS or core. Which always is being notified so that I can choose when to start the update myself - why is this different for the supervisor? I’d like to KNOW when updates are being made, and I’d like to control them myself.
Supervisor is the only part of HA which updates automatically.
I’m surprised you realised that just now, given you’ve been a member of these forums for 4 years.
Edit: To answer your question, you can run your mqtt broker standalone on a different machine or a virtual environment if you don’t want it to be affected by HA restarts.
I’d like at least to be informed that something gets updated. Why is this happening without further notice to anyone?
Until now I never came across this. I had the insight that Home assistant unnecessarily relies on Internet for ntp server, that it unnecessarily relies on cloudflare for the Editor Add-on - but as written I thought as a user of Home Assistant I would by default always have the control which component is allowed to update when, and trigger or schedule it myself. Or at least a notice if some component which could makes services (like the Mosquitto Add-On) unavailable for some time gets an update.
I do not want to do some “special” stuff where I get told later after having problems “would you have allowed the update, everything would have been working - why do you do such things? If you manage it yourself, you are responsible for it”. Doing this myself I would need to implement a mechanism which detects the update, informs me, let me do it. Home Assistant has all these things and does it for many components. If it’d be necessary, I could and probably would do it - but does it really make sense?
Does there exist an explanation why it is not possible to let the user manage the update for the supervisor?
Show Notification “supervisor update exists” - should hopefully be not a big deal.
Disable Auto-Update per default - exists, could be done.
Allow Auto-update once/trigger update after user confirmed Supervisor update - should also be just a signal or semaphore.
How often does the supervisor update? Is the reason this is managed differently from any other component in HA the frequency of updates?
This is a wonderful example why it really makes sense to show these updates to the user via notification. I’d have recognized the ntp setting for sure in this release history (will have a look where to configure it - to have a default somewhere in the internet is just evil - no matter if ntp server, cloudflare or whatever) if I’d been presented the updates including the link to the version history - like it is being done for every other component in Home Assistant.