Currently the utility_meter’s are treated “like” sensors, yet they do not support the friendly_name attribute…
This is very frustrating when you try to set up things that auto fill (monster cards for eg)… because they report a horrid looking name …
I have monthly power consumed for certain things set up here … and I want them to have the same friendly name as their name…
This way I can have a graph of current power draw, and a glance of month to date, automatically populated and items will have the same name, without having to add each entity individually specifying a friendly_name on the glance!
The interface doesn’t let you override the name (as you can with other sensors) - so I assumed that this wouldn’t work … it does…
But I still think that this is not ideal … now I have to create entries in 2 separate places just to alias it… would be better if you could do this with the utility_meter like you can do for most other sensors.
If you add it to customization UI you only do it once.
That is why customization UI and customize.yaml is available to customize where things don’t have all the options
The entity registry also allows you to override an entity name if needed
Well … I mean I have to add an entry in utility_meter, and another corresponding entry to then further customize it in the homeassistant: customize… doesn’t seem right
Another vote here. However, would it be correct to say that HA is moving away from name/friendly_name use within sensors in general and moving all of that to customizations?