The yaml configuration is good for small setups. With more complex configuration, the configuration becomes large and hard to read. Modularization can only be done on a per-type base (e.g. all sensors in one file, all friendly_names in a different file).
Idea: Allow duplicate keys and merge them. Allow “include” on top level.
This allows to have e.g. all garden sensors, switches group and friendly names on one block or file and the living room stuff in a different one.
Great, I did not know this (honestly, after reading about the 2 styles of writing config I did not expected a 3rd to be there ^^).
Seems that it can contain all except customizing
But that’s another story: Why “customizing” instead having entity_id and name as separate properties in all components? But I should create a new post for this…