All core configuration options moved to UI - Moderators please remove this post in its entirety

It would be really great in an upcoming release if all the core configuration options were added to the UI.

I believe this will drive a greater uptake of the non-technical public.

It’s a small development team and will take some time but the plan is to have everything doable from the GUI.

Everything is relative.
I’m not sure it would be som much easier if everything was done in GUI.
That will probably open up more places where you make changes, at the start you got one place configuration.yaml I don’t know if that is so hard.

It always takes time to learn something new.
If I was to sit down with a new video editing software which is all GUI based then I will still struggle in the beginning.

HA is not for everyone.
You need to have an interest for tech and some development.
Just like game of thrones is not for everyone.

If someone gets so lost that they have no clue how to proceed then I’m sure it’s more interest than actually knowing what to do.

1 Like

I already knew it was in the plan there is an article about it https://www.home-assistant.io/blog/2020/04/14/the-future-of-yaml/

I didn’t throw a tantrum, I am sick of being denounced on this forum when I ask for something that will make HA better and more importantly more accessible to people.

I am a solution architect, my whole life is about making technology more accessible to people.

Why did apple go from nothing to a USD$1T company? They made technology more accessible to people. No I don’t want to get into a discussion about Apple.

The point is I made a request to have look at pausing on all the integrations, which what everyone else in this sub-thread seems to be asking, and make the base platform more accessible to people. You decided that made me self entitled even though I pointed out it wasn’t an issue for me.

I just don’t get it what is so wrong about asking to improve the base platform.

It is a feature request sub-thread. The operative word being Request, personally I think it is you throwing the tantrum because some dared to suggest something that you think is trivial to others.

I see your point, but what you are asking is that all the current users just have to be fine with how it is, and put all energy on (possibly) new users who could just go the same-ish route that everyone else have.

This has the possible effect that current users may switch to something else because there is no “meaningful” development going on in HA in their perspective.
And off course we don’t know for sure that the easier implementation will generate more users in the first place.

Yes I do understand the dichotomy of the request and if I was a programmer I would be putting my hand up to help.

From my experience the groans I get when I mention HA to people and the questions I see on forums I believe the effort is worth it.

Especially as I pointed out this is what HA is all about. There are a lot of open source things I have tried out over the years and left behind because the community wanted to keep it exclusive to tech heads.

I love what has been happening in the last few major releases just think it could be better if the basics are focussed on for a major release.

I get people asking to do home automation for them. If there was a product like HA whIch I could do a basic setup and then let them free to configure their options be UI instead of YAML, I Would do it in my spare time.

You all need to chill out.

This feature request is the end goal. The unfortunate truth is this request would take way more than a single release. There are roughly ~200 config flow (UI config) integrations. Currently, there are 1632 integrations. First order would be to get the remaining 1400 into config flow, then add the extra attributes to all 1600 of those.

Lets do some pretending here. Let’s say that it takes 2 hours (an under estimate) to convert 1 integration to config flow. With 4 back end developers that would mean that they could get 4 done a day and essentially 20 a week. This would ammount to a total of 80 a week. The current release cycle is 3 weeks (240 per release). This means we would be done in roughly 6 major releases (4 months). And we haven’t even gotten to a point to add the ‘extra’ variables.

1 Like

Hi Petrochemical

How many of them are core items as opposed to integrations?

that depends on your definition of ‘core’. If we are going by home assistant core standards, they are already complete. Including all the options.

EDIT: Well not 100% complete, I guess it’s missing whitelisted external dirs. But everything else under the homeassistant: configuration has been placed in the UI.

Understand thanks.

I was referring to everything in documentation with an HA icon next to it, I thought they ere “owned” by the HA development team.

Those are just basic icons to give it a nice look instead of a blank card. All integrations listed in the documents are ‘owned’ by the development team.

Ahhh, explains everything thanks, gives me a much better understanding of the scope involved.

I was thinking that something like IntesisHome, which I use was a third party integration whereas something like template sensors or Integration was core.

Thanks again.