Lots of integrations seem to add special characters like brackets in their device names. This is well and good EXCEPT for the fact that if you then try to change the device name, the entitiy names won’t change because they’re different.
Take for example the HomeWizard integration (this is just an example, there are others as well):
They create devices like “KWh meter 3-phase (5c21zsr9eh6)” which then has entities like:
Is there a question in here somehow? Friendly names can have all the special characters you like, entity id’s cannot. All special characters are replaced by _ but that shouldn’t matter because the ids don’t show up in the user interface.
Hadn’t noticed. As a workaround you could try change the name to the _ version first, and then to the name you actually want. That might get around it quicker than naming all entities by hand.
ok. so I had tried that. and it didn’t work. now i tried it again and now it worked it again…
But yeah. It’s still a bad UX that I hope they fix.
The reason why I made this thread was cause I was wondering: is this on the HomeWizard integration devs for making a default name that doesn’t (can’t, because of the brackets) match the entity id’s.
Or is this on HA themselves?
You aren’t getting that if your entities do not have the device name in the accompanied entities. The system only changes entity_id’s that contain the device name in them. This is true for all integrations created & managed by the UI. So if you manually changed entity_id’s in that device to not include the device name, then that message will not appear.
It’s built this way so you don’t mess up your automations accidentally.