There is no such thing as automatically forced updates ever. You are misinformed.
I use a vanilla OS install and only update when I choose to. Usually I update to the latest update three months in the past for HA Core.
For HA OS updates since those have never ever caused me an issue I tend to update more quickly.
I do the above both because most bugs get fixed by the last patch of the month and because I just don’t have time to deal with the rare case of breaking changes every single month (or multiple times a month). My HA setup is now super mature and stable and I am in the mode of “it just works” and want it that way. So a quarterly update cycle is a good risk/cost ratio for me.
The standars HA installation method in no way forces any updates on you. At all.
As far as I know, the Supervisor updates itself automatically.
This is from about one week ago:
2025-11-18 16:49:09.993 INFO (MainThread) [supervisor.misc.tasks] Found new Supervisor version 2025.11.3, updating
2025-11-18 16:49:10.169 INFO (MainThread) [supervisor.supervisor] Update Supervisor to version 2025.11.3
2025-11-18 16:49:10.170 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/amd64-hassio-supervisor with tag 2025.11.3.
2025-11-18 16:49:21.202 INFO (MainThread) [supervisor.misc.scheduler] Shutting down scheduled tasks
2025-11-18 16:49:21.202 INFO (MainThread) [supervisor.docker.monitor] Stopped docker events monitor
2025-11-18 16:49:21.203 INFO (MainThread) [supervisor.api] Stopping API on 172.30.32.2
2025-11-18 16:49:21.203 INFO (MainThread) [supervisor.hardware.monitor] Stopped Supervisor hardware monitor
2025-11-18 16:49:21.205 INFO (MainThread) [supervisor.dbus.manager] Closed conection to system D-Bus.
2025-11-18 16:49:21.207 INFO (MainThread) [supervisor.core] Supervisor is down - 0
2025-11-18 15:49:30.633 INFO (MainThread) [__main__] Initializing Supervisor setup
2025-11-18 16:49:30.663 INFO (MainThread) [supervisor.coresys] Setting up coresys for machine: qemux86-64
2025-11-18 16:49:30.666 INFO (MainThread) [supervisor.docker.supervisor] Attaching to Supervisor ghcr.io/home-assistant/amd64-hassio-supervisor with version 2025.11.3
2025-11-18 16:49:30.666 INFO (MainThread) [supervisor.docker.supervisor] Connecting Supervisor to hassio-network
2025-11-18 16:49:30.710 INFO (MainThread) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/amd64-hassio-supervisor:2025.11.2']
2025-11-18 16:49:30.859 INFO (MainThread) [__main__] Setting up Supervisor
Yeah, exactly! There was a discussion about it somewhere before (maybe github).
In the past (2-3 years ago), there were a few times when the SV caused some problems (like high CPU load, which then led to systems no longer responding). It’s just great when the update runs at 4 a.m. and then nothing works anymore, or like in my case you start getting random alarm messages in the middel of the night.
I understand the argument about security and for 95% of installations the auto-update will be fine. I think something was recently added so that the SV and HA versions can’t drift too far apart anymore (which makes sense).
I feel a loss here. I didn’t even know that supervised on Linux was an option. It was never well presented. I fell in line with “Hassos is the only way to get supervised”. I had bad experiences running it on my own built Raspberri Pi hardware, and settled for proxmox. As it stands the rest of my home is hand architected ubuntu and docker and I would have preferred to have had the opportunity to affect these numbers and would have ran homeassistant alongside my normal stack of 40+ docker containers.
Thanks, I just updated a few minutes ago. It’s OK, but if you have a MiniPC with N100, make sure you edit the GRUB command line by adding: pcie_aspm=off libata.force=noncq ahci.mobile_lpm_policy=1 and then sudo update-grub
I want to switch the deprecatied Supervised method to container installation, are there any Dockerfiles or docker images of the native add-ons like piper, whisper or openWakeWord and Esphome?
Really sad to see such a change. I was running HA Supervised on my Raspberry Pi 5 on Arch Linux but now there is no migration path for me. I can’t migrate to HA OS because I don’t want to switch my entire OS, I want Arch Linux, it also runs services other than HA.
I don’t want to run an entire VM for HA OS on a Raspberry Pi, seems very unreasonable. This also comes with a lot of overhead that would have otherwise not been there.
So what’s left for me is to hope that there’s still some way I can update HA itself after the change
This is what I did witrh 8 gig. I used QEMU and it does work well but does not leave much room for anything else - only however because of the memory. I do have a few things running on the hostr but not much (don’t really have the need right now). If you have one of the RPI5’s with 16 Gig then this is still a very viable option for you! Per ChatGPT:
The Raspberry Pi 5 comes in four memory configurations. Here are the official options:
Raspberry Pi 5 RAM configurations
4 GB LPDDR4X
8 GB LPDDR4X
16 GB LPDDR4X
None of the storage is upgradable, because the RAM is soldered to the board.
Notes
The Pi 5 does not have a 2 GB model like the Pi 4 once did.
The 16 GB version is great for running multiple containers, VMs under KVM on Pi 5, or heavier desktop use.
All versions support the same CPU and GPU performance. The difference is workload capacity.
If you want, I can help you pick the right RAM size based on what you plan to run on your Pi 5.
I only have the 4GB variant and generally it has been enough for me. As an example at idle my current usage is 2.49 GiB / 4.00 GiB. Looking at statistics when running more intense tasks it maxes out around 75%, so ~ 3 GiB.
I don’t think there’s enough headroom for this solution and it will not work for me. Apart from that I still desperately want to avoid running an entire VM on my Pi.
