Installation Methods & Community Guides Wiki

Blog
14

Thank you for the update, continuing generic Linux and all the great work you guys are doing.

This really is a great project with a very nice community. It almost reminds me of the early internet days.

15

Thanks HA.
Long live to supervised on Linux! :tada:

7 Likes
16

Thank you very much for HA Supervised on linux

2 Likes
17

thanks for listening to the users and keeping the Supervised install.

The naming is getting better but since there was a name change involved I still think you could have taken the opportunity to improve things even more.

Since we have a ā€œContainerā€, ā€œSupervisedā€ and ā€œCoreā€ the thing that we are now calling ā€œHome Assistantā€ should have been renamed ā€œHome Assistant OSā€ or something similar since the ā€œOSā€ part is the only obvious thing that differentiates it from the other ā€œversionsā€ of HA.

Since we all technically run Home Assistant just different versions then keeping the generic ā€œHome Assistantā€ name for the ā€œOSā€ version is still going to cause unnecessary confusion.

But at least itā€™s closer to making sense now than it was before so Itā€™s a step in the right direction.

Thanks for that.

10 Likes
18

Thanks for listening to the community and thanks for the renaming, much clear now

2 Likes
19

This is really great news, thanks a lot for the reconsideration! :tada:

Will you guys unarchive the supervised-installer repository? (this one happens to be left off in a broken state BTW, one of the last few commits introduced a syntax error, I would open an issue there but itā€™s not possible ATM)

3 Likes
20

Can the Community Guides be added to the top menu?

image
image1094Ɨ72 7.04 KB

3 Likes
21

This is wonderful news, Iā€™m so pleased that Home Assistant Supervised will continue to be a supported method of installation. Thank you to the development team who are listening to the community and are rethinking the best way forward to make this awesome project even better. Your hard work is very much appreciated!

I like the new naming for Home Assistant Container. I do think it would make sense for each of the four methods to have a descriptor in the name, instead of only three. It would help eliminate confusion when people describe their installation and ask for help. What about something like ā€œHome Assistant Completeā€ for what is currently being called Home Assistant? Thatā€™s what it is, a complete package including the OS. Just a thoughtā€¦

5 Likes
22

I like that too.

5 Likes
23

Crest-Complete-Extra-Whitening-with-Tartar-Protection-Toothpaste-1200~2
Crest-Complete-Extra-Whitening-with-Tartar-Protection-Toothpaste-1200~21210Ɨ344 370 KB

Home Assistant Complete

Extra
Automating
with privacy protection

Smarter house in
One package

12 Likes
24

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
25

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
26

Thank you.

Keep listening to the community.

1 Like
28

I also like the sound of Home Assistant Complete.
Or at least something to describe it as an all in one package/system.

29

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!

30

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.

Capture7
Capture7782Ɨ389 18.6 KB

Capture6
Capture6775Ɨ902 50.7 KB

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 Core Container 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
31

Are they really substantially different though? Not once installed they are not.

32

Considering the title of this thread is ā€œInstallation Methodsā€¦ā€, I would say, yes. One installation method is completely different to the other.

33

:+1: :+1: :+1: :+1: :+1:
Thanks. That is good news.

34

and now an official place for your awesome install guide exists on the forum :grinning: