#YAML FTW
1 messages ยท Page 1 of 1 (latest)
So what can one do in YAML? I am confused as these seem to suggest that everything is still done in YAML
so i guess the better question is what can't be done in YAML?
Any integration that uses UI configuration only
There are thousands of native integrations (plus countless custom ones) - it's not like there's a simple list somewhere
https://www.home-assistant.io/integrations lists 2,371 native integrations (and that doesn't include some parts of HA's core)
such a shame that anyone ever thought that any removal of configuration as code was a good idea
You're a few years too late to argue that one
i get that I am personally late to this party, however, Continuous Delivery https://amzn.to/3GcCMAM was published in 2010 and strongly advocates for the use of a single repo to store all of the things as code.
i also get that, as a DevOps Engineer, I am slightly biased
And the developers wanted to make this accessible to more than just techies
yes, i get that too, but accessibility should not exclude the techies who want to deploy applications properly
You're a few years too late to argue that one
right, so i'm trying to understand what cannot be done in yaml so i don't waste my time
The answer is ... anything that can only be done in the UI
With many thousands of integrations it's not like there's a handy these 5 things
If the integration docs say YAML then you can use YAML... at least until the integration is changed to use the UI
what i am confused about is the documentation says that HA uses yaml for config https://www.home-assistant.io/docs/configuration/yaml/
but then everyone tells me that it does not
Yes, for all the bits that you the human will touch it uses YAML
i guess i'll just have to suck it and see
aren't most of the people that are interested in using Home Assistant already massive techies?
5 years ago, sure, but today home automation is appealing to a much wider audience
There's no benefit to gatekeeping
agreed, it just seems a shame to exclude a core demographic in an attempt to appeal to a new one. still, as you say, moot point.
There are a lot in this discord even who just want a one click solution because they don't want to be locked into any one platform
Configuring a integration is UI, but everything else can be yaml.
I personally haven't found a need for yaml, except when I was doing stuff with the Homekit controller integration (and YAML still exists there)
I still have some stuff configured in yaml, I also never touch it lol
i fully appreciate that we want to make everything as easy as possible for everyone, i just think that, in an industry where everyone is pushing for more use of "Everything as Code", it was arguably a step backwards to make some things only configurable via the GUI. If people want to use the GitOps (https://www.gitops.tech/) workflow, they should be able to do so IMO. As above, I fully appreciate that, almost 3 years later, this is a moot point now.
You're conflating your industry with home automation
when I say "the industry" i mean tech in general
Tech, in general, is not moving to everything as code
yes it is
Pick up your phone and use it... are you writing code to answer the phone?
You're looking at a very narrows slice of reality and confusing it with all of reality
Just because behind the scenes is moving to everything as code doesn't mean the world is
to answer a phone call, i am not configuring anything. to configure my phone, and my laptop, and my servers, i do have scripts that take care of that
i am referring to configuration as code
which is moving away from GUI
Home automation doesn't have to be some mystical thing hidden behind code. I'd agree that both would be nice, but that's not where we have been for the last few years, and isn't the direction of travel for many home automation platforms
That amuses me more than it should, mostly because that's very much where it all started...
Configure your mail server with a text file
life is a pendulum ๐
i think we are broadly agreeing - make it easy for everyone - i have no argument with that. all i'm saying is that for those who want to do it in text files, they should be able to. as i have said, i appreciate that this is now a moot point
i'll git what i can and document the rest
thanks for the pointers everyone ๐
It's a very good thing that HA developers try to make configuring easy to non-techies. Noone will deny that.
The question is not whether YAML or GUI. The question is: why not keep that small extra piece of code that allows YAML alongside GUI.
FWIW, I now define my MQTT sensors via autodiscovery.
I define a script that does the necessary mqtt publish actions and the script is called by a homeassistant startup trigger.
This way I have still full control (fuller control, even) over my MQTT sensors.
To make it easier, I have a small program that generates the YAML โบ.
Not my circus, not my monkeys
I have no influence on the decisions the project makes
We do not make the decisions, but we can let the decision makers know that we are not happy with their decision. It would be unwise for them not to listen to their users.
@granite pumice When using Discord's Reply feature it defaults to pinging the person you reply to, which can get frustrating for the target. Use Shift + click on the Reply option, or click @ ON to @ OFF to stop this - on the right side of the compose bar.
You have to change this every time (thank the Discord devs for that).
- What makes you think I haven't? ||I have feed back my views||
- What's stopping you from doing that? ||Nothing||
- Do you have a time machine in your pocket?