core: The new concept of working with names has broken "customize" and I ask you to analyze and correct the work of friendly_name.

The problem

After the update to Home Assistant 2022.8.0, the concept of working with names was adopted https://developers.home-assistant.io/blog/2022/07/10/entity_naming/ I ask you to review it and return the ability to set custom device names using the friendly_name props. For unification, you can add and add other ui_name props and implement the ideas of the concept with names through it. Please leave the option of using “customize” and specifying custom friendly_name as described in https://www.home-assistant.io/docs/configuration/customizing-devices/ The integration of Taya has already suffered, in which it is unclear what and what has become relevant and has created confusion in the naming of devices. I want to see a Kettle and a Dishwasher in the list of devices and objects, not Socket 1…Socket584 and Socket 2…Socket 32. I ask you to restore compatibility with the naming model to 2022.8.0. Now many remain or roll back to 2022.7.7 that’s why, in the hope that everything will return to normal in a couple of releases.

What version of Home Assistant Core has the issue?

Home Assistant 2022.8.3

What was the last working version of Home Assistant Core?

Home Assistant 2022.7.7

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Home Assistant Customize; New way to name entities; Tuya

Link to integration documentation on our website

https://developers.home-assistant.io/blog/2022/07/10/entity_naming/

Diagnostics information

No response

Example YAML snippet

switch.smart_socket_socket_1:
  friendly_name: Kettle # But it is displayed as Socket 1, Why???
  icon: mdi:power-socket-eu
  room: Kitchen
  
switch.smart_socket_socket_2:
  friendly_name: Dishwasher # But it is displayed as Socket 2, Why???
  icon: mdi:power-socket-eu
  room: Kitchen

Anything in the logs that might be useful for us?

No response

Additional information

No response

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 17 (7 by maintainers)

Most upvoted comments

Partly because customize is mostly going away. It’s a legacy method of adjusting names. It will only be maintained to a small extent, and mostly only for custom components that lack the modern way of adjusting these fields.

elupus on Aug 21, 2022

So a small heads up. The likely change we are going to do is not allow customize.yaml for things that are fully controllable from gui (name, icon, …). There is no good way to combine the two since we inherit part of the entity (switch) names from the device they belong to, some places mainly pull its name from the database of entities, which is likely what we want.

I will leave this open until we have concluded this, but i suggest you rename the devices from the GUI since that is the likely course of action needed.

elupus on Aug 18, 2022