I get that a lot of this is because of how the integration authors choose to generate entity names and I understand why the generate names like this. The need it to be unique so the user can find it, and explain what it does.
You know you can rename these things right? You also know that if you rename the device, it carries that name to the entity name and entity_id’s as well?
I don’t get the reference. When you add a device, the first thing you’d do is identify it and name it and you wouldn’t need to update the references. Yes updating references is needed, but it really doesn’t have any relationship to long unusable names default names that can be changed with 1 stroke.
select.ikea_of_sweden_tradfribulbe14wscandleopal470lm_e2cc66fe_basic_iqi
Then I renamed the device ikea of sweden tradfribulbe14wscandleopal470lm to Spare Big Bulb and it became sensor.spare_big_bulb_e2cc66fe_basic_lqi better but not perfect
Some integrations add some “unique” id to the device name but even then I think you can still rename them when you open the entity settings, can’t you? Another thing is how easy or hard it is to change it everywhere but then this referred topic is the right place to discuss it.
yes because the engine replaces the devices name, not the portion at the end which is a description of the entity. You can also rename that if you want as well on each entity.
As an N.B:
That something can be solved by user intervention is not a reason it can’t be a ‘WTH’ - my understanding about WTH is that it is stuff that frustrates you. Renaming ugly entity names frustrates me and takes time. I wish I didn’t have/want to do it… But It doesn’t stop me loving HomeAssistant
I think you should take this up with the ikea integration then. Many integrations don’t have this problem with any of their devices. Everything is pretty self explanatory, even zwave at this point doesn’t really raise questions on entity_id names nor what the entities do.
This is how it looks like when I click the “devices” under the integration