Many thanks for keeping Home Assistant Supervised. It’s a big relief for me to not have to learn Proxmox.
Also, +1 for ‘Home Assistant Complete’ for the full version.
2 Likes
Just wanted to also express my thanks for the reconsideration and taking the extra time to make this post clarifying things a bit more. I have gone from “Truly disappointed” to “Truly appreciative”.
4 Likes
Thank you.
Keep listening to the community.
1 Like
I also like the sound of Home Assistant Complete.
Or at least something to describe it as an all in one package/system.
Thanks to the HA team for all your hard work and for listening. New to the program, have it up and running on my RPi, and loving it. I have a bunch of sensors and other components coming that I’ll be trying to integrate and automate soon!
What has changed from the Dev teams perspective to bring on the naming change adjustment? I am genuinely interested to understand as there was extreme resistance some months ago in the re-branding blog post.
I made these comments in the original thread and was told, “It’s the current mess”. Largely, what has been presented now is very similar to the suggestion put forward, names are different, but the idea is largely the same.
I think now though that we have 5 installation methods, not 4.
This is just my way of thinking about it, feel free to disagree though. (taken from this post)
- Home Assistant using the Home Assistant OS disk-image on an SBC
This covers all SBC installs “As an image for your device” from here - Home Assistant using the Home Assistant OS disk-image in a VM
This covers installs “As a virtual appliance” from here - Home Assistant Core in python virtual environment on generic OS.
This covers Venv installs listed here and here on a generic OS, or in a VM. - Home Assistant
CoreContainer in docker container on generic OS.
This covers docker installs listed here on a generic OS, or in a VM. - Home Assistant Supervised on generic linux.
This covers any type of generic install of Home Assistant Supervised, whether that be in a VM, or generic OS - no longer listed to link.
The VM and SBC methods are substantially different methods and should be documented in that way.
1 Like
Are they really substantially different though? Not once installed they are not.
Considering the title of this thread is “Installation Methods…”, I would say, yes. One installation method is completely different to the other.
Thanks. That is good news.
and now an official place for your awesome install guide exists on the forum 
Hhaahaha I highly doubt that. I have sent some info to Frank about exactly that though, so will see if I get a reply.
the community guides section doesnt appear locked at all, I’d say go create a new thread with it
I’d prefer to see a really good official guide for Supervised, which is what I have asked to contribute too.
3 Likes
Excellent job Nabu Casa guys. You failed, learned, adapted and conquered.
My faith is being renewed.
3 Likes
Perhaps home assistant with hassos should become “Home Assistant - Appliance”
1 Like
So Supervised install on Linux is now still supported. Thank you!
But where are the documentation for this?
The repository has been archived and still marked as depreciated.
1 Like
As written in the blog post; details are currently worked on and will follow soon.
8 Likes
Great guys! Keeping Supervised is great news, but even more so is having the feeling that home assistant listens to users, not everyone does that nowadays, and it is highly appreciated.
Also missing docs structure for having in-depth documentation for integrations, such as example ZHA.
Zigbee Home Automation integration component has basic setup but no way for in-depth documenting.
Not simply many “Community Guides” but more a structured user-manual of an integration component.
There is a fantastic guide created by @kanga_who which I know has been used by A LOT of users with perfect success, myself included.
My system has been running flawlessly since installing via that guide sometime last year. Follow the steps and you can’t go wrong
5 Likes