The devs decided to essentially eliminate yaml config files in favor of GUI configs. The reasoning being less braking changes (no need to individually update your yaml files when an update requires it) and easier adoption for new, less technical users.
I don't know about op, but I very much prefer config files. Using tools like sed or grep to make changes is much faster than mouse clicks - but I understand the devs point of view.
I'm not a big fan of that either. I like my workflow of using git to version control integrations, dashboards, scripts, etc. Not sure how I would do that with dynamic configs.
> the .storage folder contains all Home Assistant managed configuration files in JSON format, which in those cases, can be stored and versioned in a git repository
Sounds like I can still do what I need. The only difference being, those configuration files can also be changed via UI which is fine. Thanks for the link.
I don't know about op, but I very much prefer config files. Using tools like sed or grep to make changes is much faster than mouse clicks - but I understand the devs point of view.