I feel the need to jump in here (don’t I always…)…
But I feel for all of the new people coming in. And vertigo’s situation is kind of the example of the issues.
Back in the day when many of us started HA was kind of “in the groove” of configuring everything thru yaml (with Jinja thrown in for templates, of course). Not that yaml was necessarily “easy” and not that there wasn’t a learning curve involved but it was kind of standardized at least where yaml was involved.
Then there came the concept of “making it easy for new people” by moving everything to a GUI point-and-click interface. I believe that is kind of where things started actually getting harder for new people and experienced people alike.
Those that have been around for a long time generally for the most part already knew the backend and yaml. They already know how the stuff that happens “behind the scenes” mostly worked at least on the configuration side of things.
Then the GUI configuration elements started to be introduced and offered the promise of it being “so easy a caveman can do it”. And the people who already knew how things generally worked could then relate the things they already knew to the shiny new way of doing things and mostly got it. But that also meant that there was a whole new set of things to learn but everybody kind of “oohed and aahed” over it and tried to start using the new stuff and could hack away at it until it worked. New people don’t have that prior experience.
And to make it even worse the GUI config has been introduced bit by bit over many many months so it increases the confusion on what is now configured thru the GUI/integration/entity registry/device registry/automation editor/script editor/scene editor and what can’t be done thru those avenues and you have to revert to the “old ways” of doing things. Let’s face it, how many people who’ve been around since before all of the new GUI stuff has been introduced now exclusively use that to configure their HA instance? I would bet there’s not one. Everybody uses some form of hybrid between the GUI and hand coding everything. I know for a fact that most of my configuration is done thru coding things by hand. Not all but most - a hybrid approach. And the reason for that is because the GUI stuff kind of sucks right now. But new people don’t know that.
Now, as a new person just getting started, who’s seen all the hype about “making it easier”, how are they supposed to know why when they try to do something using the GUI and it doesn’t work for them that it’s just because the GUI doesn’t support that yet as opposed to it being just their screwing something up?
And to top it all off the documentation hasn’t ever kept up with the rapid pace of development but it’s now even worse since there are so many ways of doing things that you never know which docs are good and which ones haven’t been updated yet.
That also goes for the “google/youtube” route of learning things. If something doesn’t work for you and you have no idea if it’s you or if it’s the documentation being incomplete (or even worse when the documentation leaves stuff out because it just assumes you already know things because they’ve been doing it so long they forget what isn’t common knowledge for the average person) you do what any tech savvy person would do in that situation and go to google. How would they know which resources still work and which are outdated? Because they aren’t all outdated but a lot are. I admit I’ve been there before.
The best and most useful thing that anyone can suggest (as has been done in this thread already) and should be right in the intro to the getting started docs (if it’s not already there) is to point out that going to Google/Youtube isn’t the recommended way of getting help and people should use this forum as the go-to resource. Not that the other stuff can’t be useful as stated above, just that you can’t rely on it being current.
Ha has always been and will continue to be a “tinkerer’s toy” for a long time to come. TBH, I don’t know if it can ever get to the point where the average joe-blow user will feel comfortable using it.
There’s a reason why the commercially available products are so basic and barely make home automation slightly less dumb. It’s because average people won’t want to take the time to dig in and learn this stuff. And the reason HA is still a tinkerers toy is because being open source and having limited resources to throw at it the development of switching everything over to point-and-click (which will be absolutely necessary to get out of that “toy” phase to where average people might want to use it) is a long time off.
Using the automation editor as an example, yes, you can point-and-click a bunch of basic things in there and it will work for the basic stuff. But what happens when you want to move past basic. You will still need to learn templates and their associated languages. That right there makes HA both better than other commercial products for its versatility and worse than commercial products because there is the promise of “doing more but easier” and it can’t deliver. Not because of anything wrong with HA but the average abilities of people who might use it.
I’ve been with HA for years and I still rely on a few “Gurus” here to help with the more complex stuff.
That said,
I Love HA and find it extremely interesting and fun!