Yes it is that simple if you are on one of the supported hardware devices. If you aren’t on one of those devices, you will have to install the OS and supervised homeassistant yourself. Which isn’t really that hard, but harder than just dumping the image to disk and booting from it.
Other option is installing in a VM of course. Then you don’t need to worry about the OS of the host. But you will lose some performance and have a tougher time with some hardware devices (people have really been struggling to get Google Coral and HGI80 working in VM).
I understand, thank you.
I currently run Supervised on an Intel Nuc. Before installing I quickly tried flashing my SSD with the OS image, but my computer didn’t find anything to boot. So I moved on to Ubuntu. Perhaps I’ll try again. I like the idea of running OS as it’s supported and future proof, and don’t deal with Ubuntu.
An excellent summary. The only comment I’d make is that the big red crosses make Core look like a stupid option; whereas in my opinion, not having to deal with Supervisor or Docker is a big advantage. I’m free to run other stuff on my Pi yet interact with HA without having complications from Docker interfaces. HA is just another application running on my hardware, alongside, for example, AppDaemon in another virtualenv.
I’d highly recommend it to anyone who is familiar with Linux and virtualenvs. Perhaps neutrally-coloured “yes/no” for Supervisor and Docker (and perhaps the OS) would be fairer?
MUCH LATER UPDATE: I’m now running Docker on a Synology NAS, and hereby declare that it’s awesome.
Literally, check-marks and crosses simply indicate what is included/excluded, respectively. This convention is widely enployed when comparing features.
Originally, I used Yes/No and the table failed to make a strong visual statement that the first two installation methods include more than the last two. Given that some new users fail to understand why their Docker/Core installation lacks Supervisor, I felt it was necessary to make the distinction abundantly clear.
I don’t want to start another argument here but this comment is totally unfounded. I run a Supervised install and the ‘Supervisor’ for me is literally just another menu item where LOTS of handy functions are found (snapshots, add-ons etc.) Far from being something I have ‘to deal with’. Likewise with Docker. As far as I as the user see it, I’m basically unaware that Docker is used in the background. I don’t have to do ANYTHING Docker related, ever (apart from a single line of text during the install process). Again, nothing ‘to deal with’. That comment could potentially put people off for no reason. Surely running virtual environments is more hard work in terms of setup and maintenance. End rant. Lets leave it at that.
As someone who is about to rebuild his Hassio install I found this table invaluable. I actually relate to @Troon’s post, and getting out of the docker paradigm for pretty much the same reasons is why I’m personally looking to rebuild in the first place so that specific column makes it very clear what my options are.
I do understand the sentiment against using a “warning red cross” but it’s probably correct as those who actively want to move away from using docker probably won’t mind too much and for everyone else having a supervised set up is probably a net positive.
The one thing I’m still missing in the overall picture is what “supervised” actually means, feature wise. There’s a scattering of features listed in various places (add-ons, snapshots, etc) but not a definitive list that I could find. If there is one I’d love to be pointed to it?
One thing that I am always struggling to find is where the config files are in the different install types. If you see the benefit for the community could you also add the path of the config files to the table?
Really helpful collection!
Thanks
B
Is this supposed to happen?
I am running Supervised on Ubuntu.
Trying to update two addons and getting the following:
20-12-03 16:44:57 WARNING (MainThread) [supervisor.jobs] 'AddonManager.update' blocked from execution, system is not healthy
20-12-03 16:46:10 WARNING (MainThread) [supervisor.jobs] 'AddonManager.update' blocked from execution, system is not healthy
Can I no longer update addons because I am running on Ubuntu?
No, your system is unhealthy, which is not the same as unsupported. There are currently lots of people facing this issue, can’t find the github issue at the moment.
Check if your docker version is up-to-date and that you have all the latest updates for your ububtu OS.
When your machine comes back online, re-run the upgrade through the supervisor section.
I just did this on my Ubuntu virtual guest in my house and it worked fine. I noticed during the Ubuntu upgrade that the docker packages were getting upgraded, so that might be the problem.
Version supervisor-2021.01.4
Newest Version supervisor-2021.01.4
Question: What is the easiest way to go from Ubuntu + Home Assistant Core (installed through apt) to Supervised? Is the shell script mentioned above included in the Core package? (I’m not a fan of containers.)
Why is there no ISO option to install Home Assistant OS to standard x86 machines?
