Filter template in version 1.16.1 breaks history-graph in 2025.6

[BorisVolkovyski]

Before update to 1.16.1 my card worked perfectly
On 1.16.1 it only shows "Configuration error" and no messages in browser DevTools Console
Chrome Version 137.0.7151.120 (Official Build) (64-bit)
HAOS 15.2
Supervisor 2025.05.5
HA Core 2025.6.1

type: custom:auto-entities
card:
  title: Running
  type: history-graph
  hours_to_show: 24
filter:
  template: |-
    {% set STATES = states 
        | selectattr('entity_id', 'in', integration_entities('hassio')) -%}
    {%- for STATE in STATES -%}
      {%- if(STATE.entity_id.endswith('_running'))  -%}
        {%- set short_name = state_attr(STATE.entity_id, 'friendly_name')
             .replace('Home Assistant', '')
             .replace('& Web Terminal', '') -%}
        {{ { 'entity': STATE.entity_id, 
             'name': short_name } }},
      {%- endif -%}
    {%- endfor %}
  exclude:
    - name: Home Assistant Core*
    - name: Home Assistant Supervisor*
    - name: Home Assistant Operating System*
sort:
  method: name
layout_options:
  grid_columns: 8
  grid_rows: auto

[Mariusthvdb]

this is not really the place for those user errors (which it is, just try that in the dev tools template and you'll see why it breaks), and hence no issue, but a question for the community.

but you are probably looking for something like:

    {% for s in integration_entities('hassio')|expand %}
    {%- set short_name = state_attr(s.entity_id,'friendly_name')
             .replace('Home Assistant', '')
             .replace('& Web Terminal', '') -%}
    {{ { 'entity': s.entity_id, 'name': short_name } }},
    {%- endfor %}

your template is really incorrect, and cant have been working before as is.

I've had a quick look at it, not completely replaced your initial selector, but I guess you can make that yourself now.

had to modify the ends with to my own entities:

    {% for s in integration_entities('hassio')|expand 
      if s.entity_id.endswith('version') %}
    {%- set short_name = state_attr(s.entity_id,'friendly_name')
             .replace('Home Assistant', '')
             .replace('& Web Terminal', '') -%}
    {{ { 'entity': s.entity_id, 'name': short_name } }},
    {%- endfor %}

or, use:

    {% for s in integration_entities('hassio')|expand 
      if s.entity_id.endswith('version') %}
    {{ { 'entity': s.entity_id, 'name': s.name } }},
    {%- endfor %}

with uses the shortened names automatically

Note: I only checked your Jinja template not the card config. I doubt it will work like that, as you'd probably need a namespace, a bit like:

        filter:
          template: |
            {% set hue_group = states('input_select.hue_group') %}
            {% set ns = namespace(scenes=[]) %}
            {%- for s in integration_entities('hue')
                          |select('search','scene.')|expand
                          |selectattr('attributes.group_name','eq',hue_group)
                          |selectattr('attributes.is_dynamic','ne',true) %}
            {% set ns.scenes = ns.scenes + [{'entity':s.entity_id, 'name': s.attributes.name }] %}
            {%- endfor %}
            {{ns.scenes}}

edit

can see the Configuration Error like you say in the UI btw, when entering the 'history-graph' without a functional config.
testing

type: custom:auto-entities
card:
  title: Running
  type: history-graph
filter:
  include:
    - entity_id: '*_temperature'

works as should be though.
so definitely a config error

unless....

this works:

type: custom:auto-entities
card:
  title: Running
  type: entities
filter:
  template: >
    {{integration_entities('person')}}

same for type: glance, all good.
and one would expect the same entities to work in the history-graph card too...?

hmm, might be an auto-entities card issue then relaying that list of entities specifically from a template filter to the history-graph card... how odd

fwiw, I went all the way down to 1.15.0, and none of these make the card work, all show the same Configuration error..
even though the history-graph requires the same entities as an entities card. so no card_param would be required, nor anything else

[BorisVolkovyski]

@Mariusthvdb thank you for your answer
Really, I've missed one bracket in code, now it's fixed in original issue description and template works great in the dev tools template.
But your idea with integration_entities('hassio') instead of states | selectattr is brilliant!

So the optimised template is

    {%- for STATE in integration_entities('hassio') | expand -%}
      {%- if(STATE.entity_id.endswith('_running'))  -%}
        {%- set short_name = state_attr(STATE.entity_id, 'friendly_name')
             .replace('Home Assistant', '')
             .replace('& Web Terminal', '') -%}
        {{ { 'entity': STATE.entity_id, 'name': short_name } }},
      {%- endif -%}
    {%- endfor %}

But the problem still the same - current version of custom:auto-entities is not compatible with history-graph in 2025.6.1 anymore

Proof: You can try to replace the card type in the code from original issue description from history-graph to entities and it works perfectly

And two weeks ago (before update to 2025.6 and 1.16.1) original card worked for me too

[ildar170975]

A simple case:

type: custom:auto-entities
card:
  type: history-graph
filter:
  template: |-
    {{
      { 'entity': 'sun.sun' },
      { 'entity': 'zone.home' }
    }}

Sometimes after F5:

But:

[Mariusthvdb]

To be more complete:
This also happens on statistics-graph and map, as I found in the 2nd post here. When using filter template.

[BorisVolkovyski]

F5 doesn't work for me in your example.
I see "Configuration error" every time.
I'm afraid it is a bug.

[BorisVolkovyski]

This one works correctly, but I want to shorten the names
It seems problem in template filter

type: custom:auto-entities
card:
  title: Running
  type: history-graph
  hours_to_show: 24
filter:
  include:
    - options: {}
      integration: hassio
      entity_id: "*_running"

[Mariusthvdb]

F5 doesn't work for me in your example. I see "Configuration error" every time. I'm afraid it is a bug.

Yes it’s a bug. The template in auto entities for these type of cards is the bug.

Then there is a separate ‘issue’ of the useless error which now is used in Ha.

Which is not auto-entities fault but core Ha Frontend.
Ildar opened a discussion for that in Frontend repo.

We hope both can be fixed… ;-)

Btw: editing auto entities in the UI: where is the Template filter option ? I can’t find it, other than using the yaml editor?

[BorisVolkovyski]

I've done it manually in YAML for the first time, and then template filter appears in UI

[erkr]

I reported the same issue before: #553

[dcapslock]

I can confirm that the issue is with using filter template for any card type where it would previously return an error which stated that entities were required. Specifically, when the error started with either "Entities" or "Either entities", or ended with "entity", auto-entities would not load the card and then try again when filters returned entities. Now with Home Assistant > 2025.6, the error is "Configuration error" so it will not match, and auto-entities will show the hui-error-card which is returned from card load, rather than the configured card.

Not sure of the best way to fix. It may be to patch the setConfig on the card to catch the error that is thrown, and if it matches what we know, then handle. Alternatively would be to not load card whenever hui-error-card is returned as the error is now always 'Configuration error'. To note, Home Assistant > 2025.6, a card loaded by card helpers never has the original error message, where a card loaded by Lovelace GUI editor will have the original error message as part of its config so it can be displayed if in preview mode. Frontend should be updated to include the message for card loaded by card helpers, which will mean that the message can show in preview, and that auto-entities can check against the message. I will test this and perhaps submit a Frontend PR.

EDIT: Noted the below. Will check the thread.

Ildar opened a discussion for that in Frontend repo.

[dcapslock]

This one works correctly, but I want to shorten the names

@BorisVolkovyski you an use the experimental eval_js option (not documented) to assist.

type: custom:auto-entities
card:
  title: Running
  type: history-graph
  hours_to_show: 24
filter:
  include:
    - options:
        eval_js: true
        name: ${ state.attributes.friendly_name.replace('Home Assistant', '').replace('& Web Terminal','') }
      integration: hassio
      entity_id: "*_running"

[dcapslock]

If you want to make a patch of auto-entities.js you can do so as per below. This will mean that auto-entities will not load the configured card on all errors, so may be harder to debug in UI, but works around the template filter error.

1. Using yoour favourite file edit method, delete auto-entities.js.gz if it exists.
2. In auto-entities.js find the code below. Tip: search for hui-error-card as that string only exists twice.

if(this.card=t.sent,"hui-error-card"!==this.card.localName){t.next=35;break}return _=this.card,t.next=22,customElements.whenDefined("hui-error-card");case 22:w=10;case 23:if(_._config||!w){t.next=29;break}return t.next=26,new Promise((function(t){return window.setTimeout(t,100)}));case 26:w--,t.next=23;break;case 29:if(!((null===(s=null===(a=null===(o=_._config)||void 0===o?void 0:o.error)||void 0===a?void 0:a.startsWith)||void 0===s?void 0:s.call(a,"Entities"))||(null===(l=null===(c=null===(u=_._config)||void 0===u?void 0:u.error)||void 0===c?void 0:c.startsWith)

3. Replace with o.error wiith o.type and "Entities" with "error", resulting in...

if(this.card=t.sent,"hui-error-card"!==this.card.localName){t.next=35;break}return _=this.card,t.next=22,customElements.whenDefined("hui-error-card");case 22:w=10;case 23:if(_._config||!w){t.next=29;break}return t.next=26,new Promise((function(t){return window.setTimeout(t,100)}));case 26:w--,t.next=23;break;case 29:if(!((null===(s=null===(a=null===(o=_._config)||void 0===o?void 0:o.type)||void 0===a?void 0:a.startsWith)||void 0===s?void 0:s.call(a,"error"))||(null===(l=null===(c=null===(u=_._config)||void 0===u?void 0:u.error)||void 0===c?void 0:c.startsWith)

4. Refresh cache and test.

[Mariusthvdb]

you an use the experimental eval_js option (not documented) to assist.

type: custom:auto-entities
card:
title: Running
type: history-graph
hours_to_show: 24
filter:
include:
- options:
eval_js: true
name: ${ state.attributes.friendly_name.replace('Home Assistant', '').replace('& Web Terminal','') }
integration: hassio
entity_id: "*_running"

well that was truly undocumented ;-)
in all these years......

for reference:

lovelace-auto-entities/src/process_entity.ts

Line 22 in 360722d

// Experimental

[Mariusthvdb]

@dcapslock your proposed edit only touches the error message does it?

not the fact auto-entities is borked when using template filter in history-graph, statistics-graph and map cards?

I feel it would be best if this thread focusses on that matter, as the Errror message we see now is a HA thing, and occurring for all cards, not just auto-entities.