husjonMar 7

#homeassistant has been phasing out the `configuration.yaml` file, which I really do not understand and strongly dislike.
It is an advanced feature for advanced users which makes it easy to set up an instance quickly for testing.
There are as far as I know of, no way of doing this today other than manually sitting there and clicking through menus.

Here is a perfect example of an integration that is now phasing out the configuration file while retaining no way of changing it.

#enshittification

Show threadhusjon

Created an issue for this and I really hope this gets some kind of traction.
The #InfluxDB #homeassistant integration is used by over 6% of all instances so I would assume quite a few people would find this extremely annoying once they need to change any of the parameters.

Removing and setting up the integration to adjust a single parameter is not a solution.

https://github.com/home-assistant/core/issues/165712

home-assistant/core

:house_with_garden: Open source home automation that puts local control and privacy first. - home-assistant/core

GitHub
Mar 16 at 6:23pmWeb
Show threadhusjon1d ago

So after a little back and forth with the maintainers, I realized that I misunderstood the warning and the good news is that the warning only talks about the host setup of the integration (as in the connection details) and configuring it after the initial setup will be available from the next release of #HomeAssistant.

As I mentioned in the issue, I find the message ambiguous.

https://github.com/home-assistant/core/issues/165712#issuecomment-4074023994

home-assistant/core

:house_with_garden: Open source home automation that puts local control and privacy first. - home-assistant/core

GitHub
Show threadhusjon1d ago

I've been thinking about this the last few days and I still think having the configuration file should still be an option. Like in the scenario where I'd like to do some quick testing on another instance, I could have exported my configuration file to another instance and spun it up, but now I have to literally sit there multiple minutes setting up each integration manually.

Does anyone remember when this #homeassistant `configuration.yaml` shift started and got a link to the blog post?

Show threadfarmio / Matthias Alphart1d ago
@husjon About 6 years ago iirc. https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md
architecture/adr/0010-integration-configuration.md at master · home-assistant/architecture

Repo to discuss Home Assistant architecture. Contribute to home-assistant/architecture development by creating an account on GitHub.

GitHub
Show threadhusjon1d ago
@farmous Perfect, thank you. <3
I remember seeing this ADR back then but I had completely forgotten if it was a blog post or ADR.
Show threadfarmio / Matthias Alphart1d ago
@husjon I guess there has been a blog post about introducing ConfigFlow too, but on the HA website those are a pita to search...
Show threadhusjon1d ago
Another thing with this integration repair fiasco is that it shouldn't even have required the user to remove the entries from the `configuration.yaml` file, instead a repair should involve a message from #homeassistant similar to the one seen today, it then tells that the following keys have been migrated and by clicking repair, the keys are automatically removed from the configuration file.
It is a YAML file, #homeassistant already knows the format, it should be able to do this automatically.
Show threadJuan Jesús1d ago

@husjon To be honest, things "aren't so simple"...

My `configuration.yaml` file is generated from jinja2 templates, because I have a number of "smart light switched by wall-mounted smart switch" that I have a particular pattern of "template lights" and automations to integrate so I can still use the wall switch normally when Home Assistant is down, but it looks like a single smart light in HA.

Show threadJuan Jesús1d ago

@husjon

While the move to non-YAML configuration makes this more difficult (I'm not sure if blueprints would work; didn't try to shoehorn my workflow there), Home Assistant automatically editing the generated YAML file won't work for my case...

Show threadhusjon1d ago
@skandalfo
Just to make sure I don't misunderstand, are you saying you have one or more templates that outputs a finalized configuration.yaml file?
Or, that you're using templates within the configuration yaml file? :)
Show threadJuan Jesús1d ago
@husjon Both! jinja2 templates (invoked from a Makefile) generate config.yaml, and inside the output they write one template light and one automation for each instance of "smart light behind smart switch" I have at home.
Show threadhusjon1d ago
@skandalfo aah, yeah in your case (semi-)automatic repairs for migrating configuration parameters would be a wee bit more difficult if not an impossibility for homeassistant given your setup, you would need to update templates manually anyways. :)