Template to filter certain update entities (ignoring ones with not met requirements)

e-raser · February 7, 2024, 7:29pm

I’d like to filter all update entities from HACS integration which do NOT contain something like <ha-alert alert-type='warning'>Requires Home Assistant.

What I have so far:

  {{ integration_entities('hacs')
      | select('match', 'update')
      | select('is_state','on')
      | selectattr('release_summary','defined')
      | selectattr('release_summary','ne','<ha-alert alert-type=\'warning\'>Requires Home Assistant')
      | list
      | length
  }}

This gives 0 at /developer-tools/template, without length I get [].

Because of annoying

github.com/home-assistant/core

Template error in Template Editor while it works fine as custom template sensor

opened 05:35PM - 05 May 22 UTC

smarthomejunkie

integration: template

### The problem I hope this is the right place to report this. I use this …code in a template sensor which works fine in that template sensor. However, when I use this code in the Developer Tools->Template Editor I get an error. The code is: {% set sensors = states.sensor | selectattr('attributes.device_class', '==', 'battery') | selectattr('attributes.state_class', '==', 'measurement') | rejectattr('state', 'in', ['unavailable', 'unknown']) | list %} The error is: UndefinedError: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'device_class' ### What version of Home Assistant Core has the issue? Core 2022.5.0 ### What was the last working version of Home Assistant Core? core-2022.4.6 ### What type of installation are you running? Home Assistant Supervised ### Integration causing the issue _No response_ ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml {% set sensors = states.sensor | selectattr('attributes.device_class', '==', 'battery') | selectattr('attributes.state_class', '==', 'measurement') | rejectattr('state', 'in', ['unavailable', 'unknown']) | list %} ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

one still needs to use | selectattr('release_summary','defined') before accessing the attribute, otherwise the dev tools section gives

How can I check this template now? Will it work?

Same is sooooo easy using custom:auto-entities with

                    filter:
                      include:
                        - domain: update
                          integration: hacs
                          state: 'on'
                          not:
                            attributes:
                              release_summary: <ha-alert alert-type='warning'>Requires Home Assistant *

e-raser · February 8, 2024, 6:44pm

According to the Studio Code Server “Generate Template” function, the | selectattr('release_summary','ne','<ha-alert alert-type=\'warning\'>Requires Home Assistant') is not respected.

Is this template part wrong?

michaelblight · February 9, 2024, 1:44am

The result of integration_entities('hacs') is an array of entity_id strings. While “select” supports this, I don’t believe “selectattr” does. Therefore you need to first use “expand”.

Then the HA attributes are under an attribute called “attributes”. Confusing, but it means you need “attributes.release_summary” instead of just “release_summary”.

And you’re “ne” match will not match anything, because it’s going to compare the whole string, not just the first part - so better to use “match” instead with “rejectattr” (assuming I following what you’re wanting to achieve).

{{
  integration_entities('hacs') 
    | select('match', 'update')
    | select('is_state','on')
    | expand
    | selectattr('attributes.release_summary','defined')
    | rejectattr('attributes.release_summary','match', 'Requires Home Assistant')
    | map(attribute='entity_id')
    | list
}}

e-raser · February 10, 2024, 1:30pm

Oh wow! I’ll give that a try immediately to see if it works. Many thanks in advance

Update: Gave it a try. Basically works great. It’s just the rejectattr part which needs a bit of tweaking (adding * wildcard to match all strings containing that search string, usually it’s a lot more text around that). In the end I used this:

{{
  integration_entities('hacs') 
    | select('match', 'update')
    | select('is_state','on')
    | expand
    | selectattr('attributes.release_summary','defined')
    | rejectattr('attributes.release_summary','match', '.*Requires Home Assistant.*')
    | map(attribute='entity_id')
    | list
    | length
}}

With this template I now get the number of available updates from HACS integration (experimental features enabled), which are actually installed (no HA dependency issues).

@michaelblight I’ll therefore of course mark your post as (ultimate) solution - thanks a lot!

Would you mind taking a look at this too maybe? It seems like you’re a pretty skilled Jinja template pro …and this one is causing me headache for quite some time: