I think the recent YAML-gate discussion is focusing too much on YAML
My issue with the move from YAML config to GUI configuration has nothing to do with YAML … or GUI.
It is lack of control. I am fine with the new way integrations implement configuration. I have no problem with not doing it in YAML.
I have a problem with not being able to control how the integration is configured. It is hidden in JSON file now and there is no UI to alter it.
Example, my Brother printer. It gets discovered and I can see in the JSON that it is configured with a mDNS entry. This sometimes fails. I do not know why. But when I restart HA I often get an error message and then some minutes later the Printer is discovered and works.
I have fixed IP addresses on everything I can because I am a geek and because I like things to be stable and predictable. So my printer has a fixed IP.
So I hacked JSON and replaced the mDNS with IP address. Problem gone! Printer always found.
A lot of my integrations used to be defined in YAML with its IP address. I did this with MQTT. I did it with Deconz. Before that Philips Hue. And I have been living without a lot of the connectivity issue many are discussing on the forum. It is not for normal people. This is geek territory.
You can do the configuration manually when you add most integrations. But once added you cannot edit them from the UI. And that is what I miss from the YAML. Not the darn YAML. I miss being able to reconfigure if I decide to move my Deconz or Mosquitto to another machine.
I can do it. I hack yet another JSON file.
But I would prefer an expert UI where I can edit the configuration. I think the process of adding the integrations are fine and most normal people will want no more. But us geeks that have many computers in the house (I juts passed 100 manually configured IP addresses) an access changing the discovered config and changing an mDNS address to a fixed IP is what I miss. Not the YAML.