It is very unfortunate that there are still a lot of entities (mostly yaml made) that cannot be assigned to area’s, and cannot be hidden, and maybe more things, now or in the future. These properties cannot be set in yaml but also not in the gui because this needs a unique_id that cannot always be assigned. Being able to do these things is vital to keeping things organised.
I do not much care if this is solved by adding unique_id’s to all platforms, or by linking customizations to something other than unique_id, or by allowing us to set these properties in yaml directly, but I guess that the first option is the easiest way to solve the customization gaps once and for all. For templates this is possible, but e.g. not for all sensor types.
Please vote for this if you like to keep HA organised as well.