Which means you were already running unsupported.
It’s still open source and Supervised can still be supported by the community.
Curious, I run Supervised on an older all-in-one PC. If I convert that machine to HA OS, what happens with the screen? Is it usable? Is it always on and lit up?
I went from Docker on an another PC but moved to Supervised after that machine died a terrible death thanks to a power surge. Honestly, I didn’t like using Docker that much.
Based on what I have read it will auto-log in and show a ha cli prompt.
I’d be fine with that if the screen eventually goes dark.
It does not.
You can get an addon that shows a dashboard though.
1 Like
I recently switched from a supervised install to HAOS running in KVM and after using it for a while now I was actually planning on switching back to supervised so this is a bit disappointing news, but I’ll manage. But I was also one of those who was running a supervised install with the analytics always off.
In my opinion, Supervised installation method should be supported again, docker installation method is insufficient. Supervised is more important for the development of Homeassistant.
3 Likes
It’s still open source and Supervised can still be supported by the community.
Will there still be a Supervised installer script? How will I maintain my supervised installation? If there is still a way to do Supervised installs, why is there an announcement that it is going away?
They did not say they are deprecating support, they said installation methods.
I believe they did in the second paragraph of the first post.
Beginning with Home Assistant 2025.6, affected systems will display a notification after updating, indicating that support will end in six months (with release 2025.12) and include a recommendation to migrate to a supported system.
If you have Home Assistant installed using either of the two deprecated methods, starting next year you will no longer get official support (from the development team) only unofficial support (from other users).
That’s why they recommend migrating to a supported system.
3 Likes
And supervised will still exist for developers, so you can still run it, but documentation will probably be more technical and the normal forum will be less able to help (it is not that helpful today anyway).
Probably not, but supervised is used for development, so it will still be available.
That means you will have to do some more steps and you might have to set up a environment to compile parts of it.
I am hoping that’s unlikely. For example, the supervisor deb to install the supervisor I would imagine stays around. In my mind it makes packaging easy.
1 Like
That’s not unlikely, your initial setup will require you to set up the environment.
That would be lame. I guess I need to fork the repo to preserve it. It costs them almost nothing to have GitHub actions release a deb (that is already working today). I’ll copy it I guess.
2 Likes
I have forked into my GitHub the only two required installer components for a supervised install.
- os-agent
- supervised-installer
3 Likes
Well bit the bullet.
Ordered a mini-PC with Home Assistant installed.
Backed up current installation on Core.
Downloaded the backup.
Shutdown that machine.
Booted up new device.
Change the IP address to match the old machine running core.
Uploaded that backup I downloaded,
One error …; my config file on old machine referred to local directories that did not exist on new machine.
Fixed that. Rebooted new device.
Plugged in (my one and only) USB device (my music controller).
Rebooted.
Everything works perfect — 5 TVs, 8 zones of stereo, Insteon controlling 70+ lights, roborock, groups, etc.
Painless really. One hour total time. Whole new system running perfect.
Should have done this a year ago.
16 Likes
We need a fork 
1 Like
AND, HAOS also natively supports the Studio Code Server Addon which HA Supervised does not
It can be added from add on store, no problem.
Still don’t know why people like Studio Code Server so much.