Paste this into the template editor under the dev tools and copy the output.
{{ states | map(attribute='entity_id') | list }}
1 Like
It would nice to have a device column where we can filter in dev-tools
1 Like
Quick question, why are themes and add ons considered a device? At least they show up in setting > drives and integrations> then clicking on the devices tab. I understand that possibly everything that is installed has to exist in HA has to be an entity or device. Just seems odd that you have custom themes installed in HACs listed as devices. On the other hand there are always more entities than devices so putting them there adds to that. Just curious.
Also, about the android shortcut. Simply press the “>” with no quotes to switch to the non entity filter. Not sure how I missed that when originally posting above.
They aren’t. That page only contains integrations. Integrations create devices, entities, and services.
1 Like
I meant when clicking the devices tab (at the bottom of the android app) .It’s at the top in a desktop browser, along with entities and helpers. It clearly has add-ons, custom cards and custom themes from HAC’s listed when no filter is applied in the Devices tab. Not the main integration page you go to after clicking on devices and services (I guess technically actions now) from the main settings menu.
Ah, yes. So what’s going on there is that Hacks creates a device per extension and that device is used to host the update entity that lets you update that extension.
1 Like
Awesome!!! Thank you!
1 Like
This is way overly complicated than what it needs to be
Please do tell us how you could do it simpler than clicking Developer Tools → States or Settings → Devices & Services → Entities?
I am referring more to, when you start building automations in the gui and go back later to review you often see things like this:
device_id: 75887b41474e0a17ef4c7a528d3c6b11
entity_id: fdf1f4f6c68df0f6cbad0e32aed127b3
Going to “Developer Tools → States or Settings → Devices & Services → Entities” and looking at the device, there is no device or entity id that matches this. All I see is the entity id for the name I set, not the alphanumerical identification ids.
To make it easier, first would be to understand what these *_ids: really mean. I would love to be able to search for the ID (using e in the developer tools section) and paste in either and the system tell me which device it is.
There is absolutely no way we could have interpreted that meaning from your post.
Those ids are there to enable easier replacing of devices, but yes I avoid them as they are meaningless to me. I use entity ids and if I need to replace a device I do this: Adding new devices and replacing devices
2 Likes
So back to my question then @tom_l, if they are meaningless why does 1) the gui use them when you try to setup automation and 2) why are they not listed in “Developer Tools → States or Settings → Devices & Services → Entities”, you question was how do you make it simpler? my answer is 3) make it so any ID the system automatically uses is listed in the section you described as well as have it searchable.
The gui uses them so you can change the entity id without needing to update your automation.
You’re not meant to use these outside the UI. If you want to use yaml, use yaml with entity based actions, not device based actions
You can find the device if in the url for the device.
So the system is making it more complicated than it needs to be, makes sense
I think you are by not using the ui. Just use entity actions, triggers, and conditions if you’re using yaml. They are much easier to manage
1 Like
So I ask again, why not make IDs used by any method searchable? The IDs are not searchable in the methods provided? It should be universal
Look, the feature doesn’t exist. So at this point you should just adapt to the current system. Complaining here isn’t going to go anywhere. We don’t add the features.
So you dont want to develop / add the feature - all I was looking for. The system knows what the ID is, dont understand why improving the search functionality would make it more difficult. That was all
No, I do not want to develop the feature. That’s why it’s pointless to complain to tom (not a developer) and myself about it. I’m a volunteer, and when I do add features, I only add to the backend. I don’t know the frontend.
The are not meaninless they are used
The are meaningless to me.
As I use YAML and can easily replace devices myself as I do not use device ids (or entry ids) in my automations.