Might I remind you that often the official sources, or lack thereof, don’t get the job done.
When I was doing my setup, if it weren’t for other people/sites, combined with my tech background I’d give up.
2 Likes
I would add the following:
Cloud
Code name: hass-nabucasa
Repo: GitHub - NabuCasa/hass-nabucasa: Issues related to the cloud integration in Nabu Casa
The brand is a mess regarding the cloud services offered by nabucasa. The current branding is a bad one for latin languages, as it ressembles “somebody’s home that is a dumb guy”. It would be much better re-branded as a direct reference for its services or classes of, as the other ones: OS, supervisor, etc.
Home Assistant Cloud
or
Home Assistant Cloud Services
Depending if the father-branding results on a single word for its dependants or else.
Just my 2 cents.
1 Like
I know, and I’m generally one of the people helping others here in the forum 
Believe me, there are countless requests here on the forum, from people having watched a video on youtube or followed a guide somewhere on the internet or read a discussion on reddit and then they come here, complaining that it doesn’t work.
The official documentation is very good and the most up-to-date resource for information for non-coders and if the docs are not sufficient, people should come here on the forum and ask for help and not read a guide somewhere, that a guy wrote 3 months ago.
3 Likes
I totally support the plan
Home Assistant is the strong brand. The Hass.io and many names have washed out the brand and caused so much confusion - also to me when I started. The change may be painful but the current state is painful too.
You cannot practically reach out for a consensus decision. In these matters there will always be 100s of oppinions and no consensus. At the end you will have fractions of the community discussing this for years. If you vote for 10 proposals the largest minority winds and the majority will always be negative
This type of decision is best taken by the leader who is also the single person that will face the largest consequences of the decision.
I have been leading two open source projects (Open2300 and Motion) and I was part of the fork of TWiki that became Foswiki. I know where Paulus is coming from and he does this one the only way to do it.
We now get a clearer branding and naming of things and in the long term (2-3 months from now) we will find the daily life as community members easier when we do what is the most important role we all have - helping the new users in a friendly and welcoming way
9 Likes
I do appreciate the fact that the word “hass” was retired. It always had this problem:
Plus, in English, three-quarters of the word is “ass” which is rarely a good choice unless the product truly has something to do with it.
So the new normal is hass.io> Home Assistant. What was once just a way to install and run Home Assistant is now known as Home Assistant. Meanwhile, what was once Home Assistant is now Home Assistant Core.
It’s not my preferred branding solution but, as seen in this lengthy thread, it was presented as a fait accompli and opposing opinions get no traction. It is what it is.
2 Likes
You’ve expressed a thought I’ve had but in a different way. I agree things will be better in the future. However, between now and then, the consequences of this decision won’t, as you had stated, be borne by the project leader, they will fall on the collective shoulders of dedicated community members.
It now becomes the responsibility of all those friendly and welcoming members to disambiguate the old terminology from the new for newcomers. What was once a conversation about the differences between hass.io and venv and docker and etc will change to:
- Explaining how reference materials pre-January 2020 use outdated terminology. What was once called Home Assistant is now something more multi-faceted.
- Explaining the different ways you can install Home Assistant Core (venv, docker).
- Explaining the different ways you can install Home Assistant (RPi platform running Home Assistant OS or on Intel platform running a flavor of Linux).
- Explaining Home Assistant has an ecosystem of add-ons whereas Home Assistant Core does not (sort of).
If anyone says that sounds like the same things to explain as in the past (plus a little more), they’re right. For the next 2-3 months (and hopefully not much longer) community members will bear the consequences of the re-branding. To be clear, I state that as an observation and not a complaint.
4 Likes
So we have HAC:
Home assistant community store
Home assistant companion
Home assistant core
Am I missing any more?
[Edit] Home assistant cloud!
1 Like
Team surely worked this for a long time.
I’ll find useful a single simple doc page What is Home Assistant? explaining all names and main components, where all components link to and explain where they fit. Something like the graphic in the Hass.io github readme.
May be shortcuts should be like HA-Core, HA-Companion, etc. It’d be nice the shortcut had an official, consistent form too, so we all speak the same language
Most delightful will be us no longer writing hass.io and Discourse creating links to http://hass.io and for some reason they always get click counts.
1 Like
As a newcomer, I am so happy to read about initiatives to clear confusions
It took me so much time to understand Home Assistant vs Hass.io
BUT
Generally speaking: Renaming A to B and renaming B to C with the purpose of avoiding confusion is the worst decision ever 
Starting from now, you will have people speaking about B because they are aware of the rebranding and are actually speaking about A … mixed with people talking about B, not knowing it is named C now…
This is why the most famous rebrandings are pretty “all-in”
4 Likes
Was just thinking today that a rename of the products would be helpful. This is going to help new users get on board, I think. Nice one, team!
Comment Removed.
2 Likes
Please don’t change X to Home Assistant!!!
I tell people I am a fan of Home Assistant!! Home Assistant is the brand . You can put many names under the brand, but please don’t change Hass.io to Home Assistant.
1 Like
I’m really not sure where I stand on all this. It’s a mess now that’s for sure…
But a worry that occurs to me is that some of the many ‘expert helpers’ here might get a bit fed up with all the preamble they need to go through in order to get to the bottom of a question before they can even attempt to answer.
I don’t think I am exaggerating when I say that a good deal of the success of HA is down to this forum which as I tell anyone who has an interest is one of the friendliest and most generous places I have been to on the internet.
2 Likes
While the name probably didn’t come from this, I would describe my current setup as just that a lot of the time, simply from the way it was described to install it.
Which now points to:
Not sure if the description changed, but it is how I viewed my system for the longest time. Hass.io on docker. Even looking at my info in system health would make me think I would be OK saying this.
System Health
| arch | x86_64 |
|---|---|
| dev | false |
| docker | true |
| hassio | true |
| os_name | Linux |
| python_version | 3.7.6 |
| version | 0.104.3 |
| virtualenv | false |
Lovelace
| mode | storage |
|---|---|
| resources | 9 |
| views | 8 |
Either way, I do welcome any name changes that help clarify everything. For me it did take quite some time to grasp the differences in the names, let alone the install methods that go along with them.
I agree to others sentiment, whatever is decided in the end, a nice big welcome sticky post with the options and names should clarify things in the future for new users.
Home Assistant is definitely a brand name to keep for obvious reasons. It started as a “monolithic” Python application and incorporated hundreds (maybe thousands) devices and technologies. This all happened before containerization. After Docker become a de facto standard, it was necessary to split the monolith into some kind of Core HA plus several add-ons. This was a great idea but it was necessary to manage some kind of orchestration. Then Hass.io was created as an operating system that brought all pieces (Core HA and add-ons) together, managing separate containers and integrating them as a single system. Changing their names will not modify that. Now I presume that this orchestration will go very fast to another level because Kubernetes is becoming another standard. Obviously not the full package but Rancher K3S is already running on Raspberry Pi and it would be great to see HA fitting into clusters in order to distribute add-ons through pods. Looks like to me as a discussion about architecture, more than just name changing!
1 Like
What exactly was split away into add-ons?
Okay thanks, as I stated I’m a newbie and I find it all a bit too confusing, I have managed to set mine up to do what I want it to do for my needs for now, I could of chosen the easier route and just gone with something like hubitat but this seemed like more fun. 
These are add-ons and HA itself as separate containers in Hass.io environment.
pi@lava:~ $ docker ps --format "table {{.ID}}\t{{.Image}}\t{{.Status}}"
CONTAINER ID IMAGE STATUS
4f058070fb47 homeassistant/raspberrypi3-homeassistant Up 3 days
bff95bb5169c homeassistant/armhf-addon-samba Up 4 days
ce8ab55c04ef homeassistant/armv7-addon-mosquitto Up 4 days
d3ae6c4ceeff homeassistant/armhf-hassio-supervisor Up 4 days
You’ve listed companion software created by other open-source projects. They were never part of the so-called “monolith” that became “necessary” to “split” out it into “add-ons”.
Hass.io was created to simplify the installation of Home Assistant (Core) and its related software (nginx, MQTT, samba, wireguard, etc). It’s goal was to make an end-user’s life easier. It was never due to there being a “monolith” requiring to be split apart.
It can be said that the new Home Assistant now presents itself as a monolith. A comprehensive home automation solution that incorporates the HA Core with related companion services. The end-user doesn’t have to understand nginx as being some “other software” but simply more functionality that neatly integrates with the Core.