thanx @Edwin_D ,
that works, now i understand more what name is? it´s only for each single entity… weird that integrations can create an entity with that field name beeing empty instead of using it, then it would be more obvious. anyhow the default entity name should be stored anywhere?
and i realized in the new entity lists you cant filter by entity. so it was not as easy to find all Entities Doors, as i have many with device name outdoor`
what is the difference between friendly name and name? friendly name = device? name =entity?
The friendly name given by the integration can be overruled by setting a name by the user. That this particular integration also has a way of naming things is not known by HA, most integrations will give a name you may not like.
“Show as” picks a device class. It determines how the states are translated when shown in the UI (e.g. on= Opwn), what icons are used for states and sometimes colors for active/inactive entities.
I do not know what you mean by filtering in the entity list. The list for picking an entity uses searching, it finds loose matches. The best matches are placed first. If you name things well that might help finding things.
Really filtering entities is possible in many places, but not in the entity picker.
Filtering on the binary sensor domain will get you further, but not all the way. If Zigbee is adding the door to the name, filtering on integration will narrow it down further. Then search on top.
In templates you can filter on device_class but not in the UI. There you need to add your own labels if you want more.
But how do you expect to find doors other than by using the search field if they aren’t doors as far as Home Assistant is concerned? It is just Zigbee2Mqtt putting door in the name.
i had used the search field and i got 40 entityIDs (but have only 10 real doors) , so i thougt “easy peasy, simply filter by entity” and i was surprised that you can filter everything on the entity page, but not entity