That is always a distinct possibility…
1 Like
Interestingly there is a brand new thread that highlights the issue with some of the things we are discussing here.
For those who think that the UI editor is the way to go I suggest you go to this thread:
and help that user solve their problem without using any of the yaml that they have provided in their post.
Do it completely using examples from the UI editors and screenshots. But even then it will be easier since they already provided a yaml version for you to better understand what they are actually somewhat trying to do.
I’ll watch the thread to see how it works out.
2 Likes
There’s actually been a couple of those today. With no replies.
1 Like
the automation editor is not the same thing as config flow, they are completely separate in this respect and many of the power users that like config flow do not use those editors. They have their own issues. That level of complexity is not there for configuring an integration.
3 Likes
Literally said umpteen times in this thread that yaml for automations scripts etc is staying. The option for yaml is only for new configurations.
5 Likes
I don’t believe for one moment that neither you nor the poster above you understood the point he was making. 
3 Likes
Apples and oranges. Adding an IP address and a port via the UI verses yaml is the same. Automations is another story. Using the automation editor as a baseline is unfair and you know it.
5 Likes
Not at all - the question is ‘how do we support people when they dump screenshots instead of posting code?’
The answer, apparently, is to create an animated gif. Seeing as I spend most of my time on my phone it’ll be unlikely I’ll be able to provide such support.
Your responses won’t be code… you’ll say things like “next click ok, then click in the upper left corner”.
I can see it now.
1 Like
I said clock, with an L 
9 Likes
Hah, sometimes you need to walk away from support when that happens
2 Likes
I agree with Brian here.
I find Home Assistant to be unacceptably fragile. I agree with the couple of posters I’ve seen who commented that HA is not reliable across upgrades, or even reboots. Moving more eggs into that basket, and eroding our ability to sidestep it when necessary is not a step in the right direction, in this user’s opinion.
When an open-source developer tells you that the project is run by volunteers, and implies that you, the user, should be grateful and to hold your criticisms of the project’s direction, they are doing you the unintended favor of revealing their opinion of users’ place in “their” community. Take notice.
So I guess I’ll take the condescendingly-offered advice to move on to some other solution.
1 Like
Do you have a link to a dev saying that?
Check twitter 
Tried right now to create a new input_boolean in yaml and it didn’t reload with any of the reloading services on the server control. so, only the ones created in the UI and handled by the storage will be created without restarting HA.
Update: Like dshokouhi point me out, yes, it’s possible to reload input_* entities written in YAML with the reload service in the developers tools panel, Learnt something new today. 
Note that I´m not against YAML, instead, I love it, and it is the only way I can do many of the thing my system have, it is very powerful and all the integrations that can only be done in yaml should no be touched, like all template* integrations, shell command integration and many many others.
But looking to Input_* entities for example, they are much better and conveniently handled in UI.
The ADR0010 only states that integrations that communicate with devices and/or services (with some exceptions) will be configured in config flow, integrations that include authentication info, personal identifiable info, etc. Like ESPHome is and may other that are implemented on the integrations panel for some time now.
You can still share the ESPHome yaml config, the integrations that you are using, they are listed on the info panel, and all the things that you did your way and mai inspire people like me to do the same or tweak it for my needs.
Don’t think things will change for the worst, YAML will be part of HA like has it been.
I’m only an user of HA, not programer, contributing by being NabuCasa subscriber, reporting one or two issues on Github, and giving my user opinion. so take my opinion for what it is worth.
you need to call the service call input_boolean.reload its not in the UI yet.
1 Like
Until the day packages will work in HA, i can live with integrations setup in UI.
But i have the fear that day will come. 
Oh, I see, thank you.
Is always great to learning something new 
1 Like