My goal is pretty straightforward: I created a label called to_matter_bridge that I would like to add to the devices I want in my Matter bridge, like my ESPhome smart plugs (I’m using Home-Assistant-Matter-Hub). So, it would be nice to be able to label the device, like my smart plug in this case, and applies to all its entities, like switch, sensors, etc.
A toggle “Apply label to all entities of this device” would be a good solution.
There is a similar topic here, but I’m doing a proper feature request and adding a use case for the feature.
Here’s your workaround.
Go to Settings > Entities
Then Filters:
Then pick your device
Now the entity table is ONLY that device.
Then hit the selection mode button:
Check boxes will be exposed - click the one at the top to select all:
Then on the top right - Add label Dropdown:
THen pick the label to add
It will be applied to everything checked, which was everything in that device.
1 Like
That should work, but don’t you think the suggested option is valid or there is any problem with implementing it?
I don’t need it.
First I don’t operate on ‘devices’ never have never will. Device triggers are evil.
Second I have literally hundreds of labels now. It’s the centerpiece of what I’m doing with my LLM work I literally live in the sorting table and why I knew immediately this was possible. I’ve simply no need when the table is that powerful.
Now if you ask me what I want I want insersection search on those labels in the table
And, or, not, XOR.
1 Like
But do you see this as a valid suggestion that other people can use it?
This would be not a feature for me and/or for you, but for all folks who use Home Assistant.
I am not here to argue for or against. This is your request. BUT I will point out a valid (and quite elegant) workaround exists. Like I said I won’t use it. The workaround is there, if others see merit they can vote. That’s how this works.
In dev, you have to have:
- A need
- A solution
- and someone who wants to use it
for a valid business case before you start writing code.
You have 1 and 2. Go poll for 3 
That is not a workaround.
The need have already been seen by the devs and that is their solution.
A solution that is flexible and can do lots of other stuff.
To me this request was fine, if the way to do it was not known, but once the way is known and the feature request is still uphold, then it is just another “lazyness” feature request, where the devs is asked to make the few clicks needed to do the action with the already available methods.
Here the request is to find all entities of a device, then the next user wants all update entities of devices, then the next one wants all availability sensors and so on.
If the devs did all those possible versions of the mouse clicks then there would quickly be so many that users would complain about the amount making it hard to find the right one and yet there would probably still be some complaining over their special way was not automated yet.
1 Like
Closed as already available.