It al works now, it was fixed!
For inovelli blue zigbee light switches, the button presses are recognized as devices rather than states. But again those entity IDs when looking at yaml code are not shown as friendly names
Button presses are events, devices make the eventās āeasier to useā for beginners. You can use event trigger if you are advanced enough to avoid using device based triggers.
The number you see next to the entity_id in a device trigger is the entity registry id. Itās a value that points to the entity, which in turn has an entity_id. Itās so that you can change the entity_id without it impacting your device based triggers. If you use yaml, you donāt need to use that number.
Seems like that defeats the purpose of a user friendly UI if the solution is to edit yaml.
Admittedly, Iām new to HA but itās overwhelming and daunting for a beginner to always be directed to yaml whenever there is an issue (which seems to be quite frequently).
If yaml doesnāt require the entity id number then the ui shouldnāt either.
There should at least be a place within the UI where I can see what these registry entities areā¦.its completely a mystery when trying to create an automation. Is there a simple table or something?
The pinned topic in configuration covers this.
No, the pinned topic does not cover my question. I understand that you can find entities and their states within developer tools, while the label for the entity is a text label, itās not the numeric label that Iām seeing that shows up when you go to the YAML code.
The yaml code shows a long number string as the entity id instead of a text label
It shows a device ID and an entity ID that is nowhere to be found in the UI.
It wonāt let me upload a pic to show the difference. These are in available blue switches that do not show up with regular friendly name entity IDs. Somewhere in the yaml code it has to be a table that lists these numeric values that represent entity IDs that are then relabeled as friendly IDs.
You shouldnāt be using yaml to alter device triggers, conditions, or actions. Those were built to be managed via the UI, the fields are filled with unique identifiers. These are in place so that you can alter the entity_id without breaking the device trigger, action, or condition.
If you must know them, they are the entry id, which can only be seen in templates at the moment.