This year I bought some devices that I was planning on using for christmas decorations, as well as other decorations throughout the year. I was hoping that there was a way to create the friendly name using a template (like if my is_christmas_time boolean was on, change a switch to be named “Tree Lights”) as well as a template for the icon.
Allowing this functionality would be super useful for people that use smart devices for holiday decorations and then change them to be part of their normal decorations, plus if will help with the UAT if the UI can accurately display what it is actually controlling (especially in an auto-entities card)
Looks like someone did do some work on just switches, but I’m not sure if these changes will still work (since it was done over a year ago) Friendly_name_template for switches
Anyways, you can probably steal the code from the template sensor’s friendly name template field and put up a PR pretty quickly against template switches.
So am I missing something here? Isn’t friendly_name a front end thing? It’s not the entity_id or anything. His comment “The motivation of this issue is to have the frontend represent data differently.”, yes that is true… because that is what friendly_name is for, is it not?
