Most help threads and tutorials I read have large .yaml files. Mine is mostly empty (see below). Is this normal for just getting started?
Q: Will a feature I add using the hassio UI show up in the yaml file? Or if I add to the yaml for that feature, will it conflict with that which was set up via the UI?
# Configure a default setup of Home Assistant (frontend, api, etc)
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# base_url: example.duckdns.org:8123
# Text to speech
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
That’s fine. Homeassistant is moving away from text configuration. That’s basically all you need until you want to do something ‘advanced’
In answer to your question, no, if you set something up with the ui it won’t change the content of that file, but if you want to use advanced options or components that are not available via the ui then you will add them there.
I want to say OpenHab went this way also, but I only looked at that, then chose Hass.
I wonder what is pushing these systems away from such text based configuration files.
One-click set-up is nice, but not having the text to inspect reduces clarity.
There was a step to add MQTT integration earlier in the setup process.
When I go to configurations:integrations and choose MQTT, there is text that states ‘This integration has no devices’. Do you have a link on how to add manually?