Pretty new here, but experienced linux and systems person.
I keep running into things that say "well you need to edit the configuration.yaml to do that, or add this into the configuration.yaml".
But when I log into root, I can only find this:
There is hardly any yaml in there other than including the other *.yaml files.
Where do I find the yaml from a MQTT Cover device and entities I created?
Conversely, If I edit
that configuraiton.yaml and paste this example into it, and do a full restart of HA, it doesn't seem to have created anything.
If it matters, I am running HAOS on a VirtualBox VM.
I'm probably missing something simple... ?
John
If you edited the configuration.yaml, 4th-file in your list, then this is where it is (it's the "real" And Only configuration.yaml ), if it was mend to create i.e entities, your find them in UI under entities.
If you edited something in mqtt, i guess you'll find in your mqtt-integration
Side-Note , the APP File-Editor is a simple but valuable editor, for small edits
Hi,
You're understandably thinking like a *nix sysadmin, rather than a Home Assistant user. HAOS is an appliance which is designed to be locked-down, with limited access to specific containers for security.
The last few years have specifically REMOVED items from configuration.yaml (the 4th line down on you screen-shot) into the databases to make config more approachable for users. Documentation referencing YAML may well be old and inaccurate.
To get access to HAOS, the more usual way is to use specific tools like the file editor and SSH server top-down, rather than going in bottom-up from a VM host :
The move from YAML to GUI+databases annoyed sysadmins years ago on openHAB, and HA is undergoing the same changes. Just adding MQTT auto-configuration caused a "stern discussion" in openHAB about control, but we all now take the lack of configuration needed for granted (HINT: config the DEVICE via discovery, not the MQTT binding in YAML).
I've got loads of MQTT devices (custom code, Python, Tasmota, etc), but only a single entry that needed YAML. HA moved away from HASS Discovery to Tasmota Discovery as the alternative significantly reduces memory usage, but HA Discovery is still good for your own custom client kit.
If this helps, 
this post!
