No need to tag, you can just reply to me (the reply button in the lower right corner of any post)
Time was when everyone started with just the configuration.yaml
This got unwieldy for most people so the use of yaml anchors allows them to split things up. (it still reads as one file from the yaml point of view)
This has now been adopted as standard so all new installations come with an automation.yaml and a script.yaml for the gui to write those items to, same with costomisations etc.
You can add sensor.yaml and binary_sensor.yaml if you so desire (look it up in the docs)
There is no single best way and many people change their approach as their needs change.
Packages are quite advanced but due to the fact that all my indentation is the same wherever it is (eg an action indentation from an automation is the same (for me at least) the same as a sequence indentation in a script) I can cut and paste with impunity across many different areas (then just change the names of the usual suspects).
Many new users prefer to use the gui so don’t get their hands dirty with yaml.
But the editors are not perfect and like the time date sensor mentioned previously will require a little yaml work.
Read the docs on “splitting up your configuration” take it in small steps, backup before you do anything major and go at your own pace.
1 Like