And stoping your contributions will help the developers support more type of installations in the future? No, it will have the exact opposite effect, so doing so will in theory actually make things worse 
2 Likes
Stupid resolution, but you canāt win with these guys. They use yaml for configuration which is dumb. They do not support core which is what advanced users like us use. I need to use docker which suck or buy their devicesā¦ This is the reason, why they will lose on the long run. I never understood why you canāt simply install a binary on UNIX in this case Debian image. I do not want layers upon layers of crap to get to HA. Yes it is bad decision but it is yourā¦ And they do care about users and customers, right!
If they didnāt then how come they went through so much trouble to make sure that nobody can ever buy them out to take over and control the source code?
2 Likes
HAOS uses docker too. Whatās your issue with it?
Why? HAOS runs on a lot of different hardware such as cheap used office PCs from eBay. You can also run it as a virtual machine which I recommend.
3 Likes
Youāre welcome to leave if itās that bad.
Note: Iām a Core user too. It is what it is.
2 Likes
Please maintain the supervised installation method. Otherwise using virtual machines is mandatory in case you want to keep using your hardware for something else than HA which is unaceptable in most cases where you have more services running on the same system.
1 Like
That is not supported anyways. Whatās so bad about running a VM?
4 Likes
Per feedback given in the original feedback thread before dropping supervised was announced: basically all aarch64 hardware that isnāt raspberry pi is dropped. e.g. OrangePi.
All hardware which requires additional drivers (kernel modules) is also dropped since modifying HAOS in this way makes it unsupported (the current stance). An example of an unsupported x86 eBay machine would be one where wifi requires drivers.
HAOS cannot be run in a lot of configurations and the purpose of dropping support is to avoid the support conversations in these scenarios.
I understand youāre sharing thereās alternatives for operating HAOS and I appreciate that. But generally, if supervised is your only means of operating HA besides a VM, then one would need to acquire alternate hardware.
3 Likes
It is same in my installation, supervised working very well in my Orangepi Cm4, but i am thinking how can we update supervised in 2026.
Or you could run HA Container which will allow what youāre looking for and doesnāt require VMs
1 Like
What part of āthis will still work, it just wonāt be documentedā is hard to understand?
1 Like
I believe the doubts are not sourced at whether existing supervisor installions will cease to work but whether new installations based on the supervisor method will still be possible after the depreciation.
Will:
dpkg -i homeassistant-supervised.deb
and:
dpkg -i os-agent_x.x.x_linux_xxxxxx.deb
still exist, being updated and stay usable?
Not from HA side. The code is open source, so the community can continue to publish & support those and there already have been community members in this thread who announced they will.
2 Likes
Ik. I was clarifying Muhamed83ās question.
Sure. Iām one of them.
1 Like
Good to hear this and Thank you in advance for your future efforts. I hope these packages will be updated by community and maybe also i can support. Supervised method should live.
Well supervised is used by developers (as has been pointed out) so developers are not going to be frozen out.
I followed the suggestion and made many tests like deleting the docker and recreate using the tag aarch64 or not but I cannot update to 64bit the docker.
If I do not add the aarch64, the docker created is at 32bits, if I use the aarch64, I get the following error: āThe requested imageās platform (linux/arm64) does not match the detected host platform (linux/arm/v8) and no specific platform was requestedā and googling I found it shall mean that I have a 32bit raspi OS on a 64bit capable HW (e.g. RPI4). But the OS is at 64-bit as running the command āuname -mā I get aarch64 and running the command ālscpuā I get again āArchitecture: aarch64ā.
If you have any idea/suggestion, please provide
thanks
I suggest opening a separate post in the Installation section of the forum to receive help rather than post in this thread.
3 Likes
Check out portainer - itās not that hard to manage containers 
I appreciate the early heads-up, but I have to say Iām disappointed. Deprecating Supervised really hurts small home-lab setups. I run my Home Assistant instance on a Debian server that handles multiple services, including security systems, and I simply canāt dedicate an entire machine just for HASS OS. Without Supervised, thereās no practical way to run add-ons in this kind of setup, and HASS OS feels too locked down for people who need flexibility.
For people like me, HA OS feels appliance-ish. Itās great for plug-and-play smart homes, but for home-labbers who already run containers, VMs, security systems, and custom services on the same box, Supervised was the only officially supported method that made sense. Running HA OS in a VM is technically possible, but itās resource-hungry and still not as integrated as a single supervised stack on bare metal.
Edit: I will also be cancelling my cloud subscription. Removing Supervised from the documentation is a step too far. You couldnāt just leave it available and let people accept the risks? At least give us the choice instead of leaving it to the forums to maintain unofficial instructions.
1 Like