Filter by label in template

Configuration
1

Hi,

I am new to using templating, right now I have this template that I found and am using, which returns a list of scenes for my “Office” room (domain). It’s helped me understand a lot about how templates work.

I’ve poked around for a while, but I am having trouble figuring out how (if possible) I can take that list and add another filter to narrow it down to only the scenes that have the “color_scene” tag.

Can someone show me how this would be done?

>
      {{ expand(area_entities("Office"))
      | selectattr('domain', 'eq', 'scene')
      | map(attribute='name')
      | list }}
2

Not sure exactly what you mean by tag, but if is a label then this ought to do it:

 {{ expand(area_entities("Office"))
      | selectattr('domain', 'eq', 'scene')
      | select('in', label_entities('color_scene'))
      | map(attribute='name')
      | list }}
3

No you’re right, label is what I meant.

Unfortunately, it looks like it doesn’t work the way you wrote it. The template tester in dev tools returns a blank list. I think I’m having trouble understanding what values are valid when I try to use selectattr() or select().

Where is it documented that “in” is a valid keyword that invokes a test for select()?
Likewise, is there similar documentation for selectattr() that indicates how to use ‘domain’ and ‘eq’?

4

Did it work at all before? I didn’t really look over the rest of your syntax at all, but now that I do it does not look right… Try this much simplified version instead:

{{ area_entities('Office') | select('match', 'scene\.') | select('in', label_entities('color_scene')) | list }}

Also, assuming the label color_scene is only ever used to label scenes, you could get rid of the preceding filter that selects only scenes.

5

The previous one works as expected (except when I try and filter by label), but yours works better :slight_smile:

THANKS!

6

Ahh, now I see what expand does. Never had a reason to use it yet and when passed over in the documentation seemed like its only function was to expand groups, but rather than return a list of entity ids it actually returns a list of entity objects… But in this case you don’t really need that, the entity ids themselves are enough for at least this filtering required so far.

7

Last thing (for future viewers), since the new and simplified template that Magnus gave me returns the entity_id instead of the name, I had to edit the other section of the .yaml block to refer to the entity_id as well.