This is about naming, you are now entering some other discussion, which is already covered in the ADR. If you don’t know how Docker works, the last installation method to use would be a Supervised installation type. It requires extensive knowledge of Linux, Docker, but also networking in general. It is not just an installation script, as it requires additional maintenance to your OS after that.
Some examples include: configuring and picking Docker storage and logging drivers and keeping up with software and kernel requirements for the future.
The amount of knowledge needed and strict requirements is highly underestimated in general for Supervised. Sure, it works right after running an installation script. But if anything changes or comes up after that, one needs to be able to maintain it as well.
Tutorials/scripts are easy… after that… that is what counts.
Noted. I added Docker as a prerequisite skill for the second installation method.
I understand the reasoning here. If one doesn’t choose the first method, one is expected to have experience with managing the underlying operating system, docker environment, and networking.
Although that requirement hasn’t dissuaded thousands of users over the past 6+ years, going forward it’ll be far easier to attract new users if they aren’t obliged to learn new IT skills before they can begin using Home Assistant. Lowering the bar to entry is a good strategy.
exactly my point.
That’s why I mentioned we should maybe use a different perspective.
Either Homeassistant Suite is used, or any of the other install methods. Depending on one hardware, the homeassistant.io website should point the user to the correct installation method…
Hub and Hubian, well, no disrespect, but this really sounds like you are joking. The former table might have been best, lest not get lost in even wilder fantastic names… Coretainer is already over the edge for that matter, what not simply call it docker. That s what it is.
Secondly, I wouldn’t set the skill level like that. The fact anyone would use Homeassistant Suite doesn’t have anything to do with his/her skill level.
It might have more to do with the fact one likes the system to do (most) the work for, and enjoy the comfort of that… An inclination for ease has nothing to do with the ability to tweak and fiddle about.
No not joking. Nor I imagine are the other people who have suggested “Hub”.
As for “Hubian”, that’s simply a contraction of “Hub” and “Debian”. It’s the same technique that was used when “hassbian” was available. It’s also how openHAB refers to its installation method: “openhabian”. Until recently, it was also how the Raspberry Pi Foundation called their flavor of Debian OS: “Raspbian”. So, no, not a joke but a common practice.
I don’t know what metric you’re using that has this so-called “edge”. I’ve suggested Coretainer to replace Container simply to emphasize its relation to Core. If we apply your standard that it must be a literal representation, like “Docker” , then “Core” ought to be “Python”. I’m not suggesting we do that; I’m mentioning it only to show there’s room for 'theme" naming and not simply literal naming.
As for Skill Level, if one has extensive linux and docker skills, you are free to choose any of the four methods, including the first one. The fact it indicates “Novice” simply means you don’t need to know how to manage linux and docker to install, use, and administer it.
In contrast, if you choose one of the other three methods and have no knowledge of linux and docker, it will, if not immediately then eventually, cause administration problems.
EDIT
I used the word “Novice” to represent the minimal skills needed to follow instructions to burn an SD card and access the SBC via a browser. If there’s a better word to describe that minimal skill-set, please let me know.
Marius, I would agree as I think these names are not ideal, they just don’t speak to me, I’ve seen Taras’s explanation of hubian and I’m thankful for that as it meant nothing to me until then and just leaves me nonplussed since.
Somebody up thread likened this to naming a car and I like that. Though the Volvo 480 GLS leaves me shrugging, pretty much as do similar offerings from BMW, Mercedes and Audi. (I think that basically leaves us with Ford and GM as exemplars). I think the name (whatever it is) should be able to be placed on a banner, either speaking for itself or at least peak interest like the ‘Mango’ suggestion.
Going to do a handful of polls in this post in order to get a better idea of where things stand.
These polls are all multiple choice, so you can vote for more than one option in each. Voting does not necessarily mean it’s your first pick or favorite choice, simply that you find that name acceptable/OK.
We are not trying to crown a winner just yet with these polls, simply trimming the list of suggestions down and getting a better idea of the types of names people prefer.
If you do not like a certain category of naming, please vote for that in the poll, so the community knows where to better focus their naming efforts. Hopefully this is not too confusing
Names that indicate this method provides the whole solution:
Multiple choice allowed
Home Assistant One
Home Assistant All-In-One
Home Assistant Suite
Home Assistant Hub
Home Assistant Complete
Home Assistant Full
Home Assistant Full Experience
I like this category, but not these choices
We should not use this category of naming
0voters
Names that indicate it’s the easiest method for beginners:
Multiple choice allowed
Home Assistant Easy
Home Assistant Snap
Home Assistant Appliance
I like this category, but not these choices
We should not use this category of naming
0voters
Names that indicate this contains the operating system:
Multiple choice allowed
Home Assistant OS
Home Assistant Supervised OS
Home Assistant Image
Home Assistant JeOS
I like this category, but not these choices
We should not use this category of naming
0voters
Familiar “streaming service” type names:
Multiple choice allowed
Home Assistant Prime
Home Assistant Plus
Home Assistant Max
I like this category, but not these choices
We should not use this category of naming
0voters
Other names:
Multiple choice allowed
Note: I intentionally left out the explanations here, to see if you can figure out the meaning on your own.
Home Assistant Platinum
Home Assistant Gold
Home Assistant Genesis
Home Assistant Unity
Home Assistant Fuse
Home Assistant Environment
Home Assistant Source
Home Assistant Essential
I like this category, but not these choices
We should not use this category of naming
0voters
Obviously some suggestions weren’t covered by these polls, there were simply too many. These are by no means final choices, so please continue to suggest new names.
Again, we are not trying to pick a winner here, but trying to eliminate some suggestions and trim the list down to something more manageable and start getting some frontrunner choices.
Klogg, rather than belittle people by saying skill-level - novice (I’m not accusing anyone of this)
We should say - suitable for : - ‘everyone’
It just sounds more ‘inclusive’ than ‘exclusive’ .
@123
I would comment additionally that I run supervised under debian (cough ! Well Raspbian on my production machine actually) and I’m comfortable doing that but would not describe myself as a linux or container expert. So I think the terms should be softened to be more gradated showing an increase in skill level across at least the first three if not four. Most idiots (me) can follow instructions as required by option 2 and my Linux skills are gradually improving.
It’s been a long time (~30 years) since I last used del *. * on an old (brand new to me) dos 3.1 machine, then spent the next 7 hours rebuilding the whole machine from the accompanying floppies. (edit: I had to take the company PLC programming laptop onto site the next DAY )
It’s why I originally suggested Supervised OS and Supervised but feedback was that the word “supervised” sounded technical and didn’t convey any understanding of the technology employed. Although I don’t feel it’s a technical term, I do understand how it may fail to convey the desired meaning.
As a result, I chose a different route which also attracted negative feedback. All this to say, it’s unlikely there’s one name that will please everyone.
Check, then I misinterpreted your post. I thought you meant you wished the devs would ask the community with decision making… Sorry about the confusion.
Yeah I purposely didn’t use that word whilst going with the suggested heading, I agree with you, not for the first time in this thread… and like your alternative (‘suitable for everyone’)
I’m less inclined to continue refining that table since I’ve been informed that all of the information is in the ADRs and inclusion of it here is off-topic. Anyone who wants to know the relative differences between the installation methods, can read the aforementioned ADRs.
Yeah, I agree, I personally have no problem with ‘supervised’
To be honest ‘supervisor’ was just the name given to the ‘layer’ that appears in so many HA Documents. Having read them and understanding its function it is fundamental. I don’t think we should apologise for that, it’s simply a small hurdle on the way to understanding ‘other’ installations. The price of moving on.
It is completely transparent on hass.io so what’s the problem and at least familiarises them with the term.
They are described individually, as this is currently the technical writeup, it will be extracted later to documentation. The form of how it is presented is not the current focus. Table, story, questionary, all kinds of things could be done. However, the focus now is setting a baseline to work from.
)