thomasloven / lovelace-auto-entities Goto Github PK

I have a Surface Go running Windows 10 S which has Edge as its only browser. When I open HA, none of the auto entity cards work. see below...

I believe that the following log entry is related as it shows up every time I refresh...

2019-11-27 16:05:16 ERROR (MainThread) [frontend.js.latest.201911196] https://xxxxxxxxxxxxxxxx.duckdns.org:8123/lovelace/all:1:1 Expected identifier, string or number

I am on version 0.102.2

I have a page with a 15 auto-entities cards to show various HA status items (e.g. battery overviews, offline devices, automations grouped by type etc).

Since the recent releases the page became extremely sluggish. On my desktop it is barely usable (scrolling very slow) now and on my phone it's even impossible to use. For instance disabling a particular automation simply doesn't work, pressing the toggle doesn't do anything anymore. Other pages in my setup work just fine, except for this particular page.

This page contains 5x entities, 4x divider and 15x auto-entities. Nothing special that would explain why this page would be so slow.

This particular uses the following configuration:
https://pastebin.com/7LhdyPZr

I did some profiling with Chrome:

After uninstalling this plugin via HACS the sluggishness on this page went away and scrolling is just fine, which leads me to believe that someting in this plugin is causing this. Or perhaps I'm asking too much of it? It worked fine in older releases, this problem started after upgrading to 1.0 and 1.1.

In the previous version of the card it was possible to show the entity when it meets the requirements of another status. Is it possible to add such functionality?

example:

         - type: custom:monster-card
            card:
              type: entities
            filter:
              include:
                - entity_id: light.ambilight
                  options:
                    type: "custom:slider-entity-row"
                    toggle: true
            when:
              entity: media_player.samsungtv
              state: 'on'

Wanted to move my last few monsters cards to auto entities, because it's marked as deprecated.

The thing is my card gets extremely slow with auto entities, it's gets stuck when scrolling it. When I switch back to monster card it works flawlessly.

This is an example:

  - type: custom:monster-card
      show_empty: false
      card:
        type: entities
        title: 'On'
      filter:
        include:
          - entity_id: "automation.*"
            state: "on"

    - type: custom:auto-entities
      show_empty: false      
      card:
        type: entities
        title: 'On'
      filter:
        include:
          - entity_id: "automation.*"
            state: "on"  

Why does it work fine with monster card?

Just updated to Home Assistant 0.98 and my auto-entities card is finding updater.updater as 'unavailable' using the following card config:

  - card:
      style: |
        ha-card {
          border: solid 2px #FF6262;
          --ha-card-background: rgba(0, 0, 0, 0);
          --primary-text-color: rgb(250,98,98);
          box-shadow: 0px 0px 10px 3px #FF6262;
        }
      title: Unavailable
      type: glance
    filter:
      exclude:
        - entity_id: '*mailbox*'
        - entity_id: '*laneway*'
        - entity_id: '*lane_gate*'
        - entity_id: binary_sensor.shed_door
      include:
        - domain: sensor
          state: unavailable
        - domain: binary_sensor
          state: unavailable
        - domain: light
          state: unavailable
        - domain: switch
          state: unavailable
    show_empty: false
    type: 'custom:auto-entities'

This sensor has been replaced with the binary_sensor.updater in v0.98 but is still showing up in my card for some reason. I've tried a cache reload (Ctrl + F5) without effect.

Hi

I am trying to display a entities card from zwave domain with attribute is_failed to true using this settings :

card:
  title: 'Z-Wave Modules Down'
  type: entities
  show_header_toggle: false
filter:
  include:
    - domain: zwave
      attributes:
        is_failed: true
      options:
        secondary_info: last-changed
show_empty: true
type: 'custom:auto-entities'

Unfortunatly it is not working, the card doesn't show up even if no entities are matching the filter. I even tries with is_failed: '= true', is_failed: '! false', nothing seams to work as expected.

I do some test with other attribute as boolean type (is_wake, is_ready) it seams that the "true" "false" value are used for testing it the attribute is present.

Anyway thanks for your custom card !

Hi,

as the title says custom_updater is depricated. The developer startet a new project called:
Home Assistant Community Store (HACS).

https://custom-components.github.io/hacs/#hacs-home-assistant-community-store

Could you please add this component to HACS?

thanks,
h4nc

Now you have adopted templating on the -mod cards, please consider adding this to the auto-entities-card:

    filter:
      include:
        - state: >
            {{in ['playing', 'idle', 'paused']}}
          domain: media_player

thanks!

Thanks for this update to the Monster Card, moved most of mine over to AutoE.

The one thing I am missing from the MC is the way it 'sorts' as explained at the bottom of the docs on MC:

Entities are displayed in the card in the order they are matched by the include filters. I.e. to get >a specific order, detailed filters must precede more general ones.

The following example will display sensor.my_sensor followed by all other sensors in alphabetical order:

- type: custom:monster-card
  card:
    type: entities
  filter:
    include:
      - entity_id: sensor.my_sensor
      - entity_id: sensor.*

What Im finding is the sensor.* would ignore the set entities above it and only display the rest.

AutoE displays the top three then the rest in alphabetical order including the top three again.

MC Example:

card:
  show_header_toggle: false
  title: Container - Switch Off
  type: entities
filter:
  include:
    - entity_id: switch.ha_docker_homeassistant
      state: 'on'
    - entity_id: switch.ha_docker_node_red
      state: 'on'
    - entity_id: switch.ha_docker_mosquitto
      state: 'on'
    - entity_id: switch.ha_docker_*
      state: 'on'
type: 'custom:monster-card'

This would display the top three and only the remaining switches, not including the top three.

I have a second MC as the above that filters on 'off' so the ones I have set are always at the top rather than alphabetical.

If you could implement that it would be brill :)

Thanks again (and hope that all makes sense)

Is the show_empty option currently working? At least in my config it makes no difference, if it's set to true or false or not at all. The card is always hidden, if no entities match the filter:

card:
  show_header_toggle: false
  title: Offene Fenster und Türen
  type: entities
filter:
  exclude:
    - state: closed
    - state: locked
  include:
    - entity_id: /sensor\..*_fenster_status/
    - entity_id: /sensor\..*tur_status/
show_empty: true
type: 'custom:auto-entities'

I'm running HA version 0.87.0.

The following example will sort all entities by name. This makes sense given that the sort option is a global flag.
With monster cards however I had the ability to explicitly position entities while the ones determined by pattern where sorted alphabetically.

It'd be nice to have this option again.

  - type: custom:auto-entities
    sort: 'name'
    card:
      title: Configuration
      type: entities
    filter:
      include:
        - entity_id: input_datetime.living_room_config_start_morning
        - entity_id: input_datetime.living_room_config_start_day
        - entity_id: input_datetime.living_room_config_start_evening
        - entity_id: '*living_room_config_*'

Hi,

I have two entities with an attribute named days_till with a number of days. I want to have the least amount of days sorted to be on the top of my entity list. But it seems that my configuration is not working, because if I set reverse: true then the order does not change.

How can I debug this? Is my card config incorrect?

Thanks

One of the entities' state:

Card config:

card:
  type: entities
filter:
  include:
    - entity_id: sensor.datum_*_bak_t
sort:
  attribute: days_till
  method: attribute
  numeric: true
type: 'custom:auto-entities'

I have just setup auto-entities to show the battery level of all my battery powered devices (using a custom:bar-card). Initially it displays fine, but then some time later it will draw a number of additional "empty card outlines". If I hover over one of the empty cards, it actually contains the same contents as the original card, just everything is invisible. The below screenshot tries to show what I am seeing. If you look closely you can see the outline of the additional cards.

Can this card be used to filter based on a state attribute that is a JSON string? Even a "substring" filter would be sufficient.

Use case: I have sensors to monitor wireless signal strength for all my TASMOTA devices based on their "STATE" MQTT topic. The JSON gets broken out, but only one level deep. The Wifi node is broken out as
a state attribute, but remains as JSON. I was hoping to filter these based on the BSSId attribute so I can list them according to the access point they're connected to.

I've tried the following with no success:

attributes:
  Wifi.BSSId: 'AP:MA:CA:DD:RE:SS'
  Wifi: '*"BSSId": "AP:MA:CA:DD:RE:SS"*'

Trying to replace monster-card with this one, and all but one card works as I hoped.

cards:
  - entity: sensor.electricity_price
    max: 1.6
    min: 0
    name: Strømpris
    severity:
      green: 0
      red: 1
      yellow: 0.65
    type: gauge
    unit: kr
  - card:
      show_header_toggle: false
      type: entities
    filter:
      include:
        - entity_id: sensor.*power*
          state: '> 0'
    type: 'custom:auto-entities'
title: Strømforbruk
type: 'custom:vertical-stack-in-card'

If I remove the include->state line, all the entities shows up, but I only want the entities with values greater than 0.0 to show up. Could it be related to the UoM? Not sure, it works with MonsterCard.

When using this custom card, the logs are filled with the following error (seems to be every few seconds):

Received invalid command: config/area_registry/list

It doesn't appear to be affecting the functionality, but it is hiding genuine errors.

I upgraded to v2, refreshed, and the cards are just gone. Reverted, and they all came back.

In some scenarios is also good to limit the amount of devices listed, is there a way to do this.

Hey, this project doesn't seem to have a LICENSE file. Is it supposed to be MIT like your other Home Assistant projects?

Is it possible to create a card with this that always shows some entities, along with filtering other entities?

I tried with this (and a few variations) but didn't work

  - type: custom:auto-entities
    show_empty: false
    card:
      type: entities
      title: "Office"
    - filter:
        include:
          - entity_id: scene.office_off
          - entity_id: switch.imac_power
          - entity_id: switch.synology_power
          - entity_id: script.reboot_ubuntu_server
    - filter:
        include:
          - entity: light.office_ceiling_light
          - entity: light.office_wall_lights
          - entity: light.office_lamp
          - type: divider  
          - entity: switch.office_fan
      exclude:
      - state: "off"
      - state: "unavailable"

Ideally I'd like to show cards for each room, and always show certain scenes, scripts etc. but hide other lights and switches. I could then activate scenes from that card, or activate a popup card from displayed scenes or scripts to turn on lights individually.

If not possible please consider adding it as a feature request in the future :)

Is there some way to use this with a card that does not have entities but a entity?
plant-status is my main problem.

First, thanks for this amazing card, I think I am using 10 of them in my layouts.

Anyway when a group entity is shown an expand toggle can be shown?
(clicking it would show items in the group). Similar to how your fold-entity works with groups.

Thanks again!

Any chance we can get this awesome plugin included in HACS? -- https://custom-components.github.io/hacs/

I don't think the auto-entities card is properly passing through the entity ID for tap_actions. But works fine for 'toggle's. Config is below - works for the lights (basic tap_action) but not for the scenes (complex tap_action). When I tap the scenes, every scene I have defined triggers.

      - type: vertical-stack
        title: Study
        cards:
          - type: custom:auto-entities
            card: 
              type: glance
              show_state: false
            filter: 
              include: 
                - domain: scene
                  entity_id: "scene.study*"
                  options:
                    tap_action: 
                      action: call-service
                      service: scene.turn_on
          - type: custom:auto-entities
            card: 
              type: glance
            filter: 
              include: 
                - area: "Study"
                  domain: light
                  options:
                    tap_action:
                      action: toggle
                - area: "Study"
                  domain: switch

Hi,

I have the following card set up and it does not work:

https://hastebin.com/qubaveqalo.cs

This doesn't work. It only works if the last row (battery_level: <=100) is indented by 4 (realtive to the - in the line above, e.g, like this:
https://hastebin.com/imasikacov.cs

I have no idea why, and it seems to be contrary to the example, such as "Show all gps device_trackers with battery level less than 50:", which has the attributes offset by 2 as per normal yaml.

Hi, I have made a small change so that I can use an "entities" card but use a custom card to represent each separate entity being rendered,
For example, I am using it with custom:slider-entity-row so that I can have a slider on my list of Lights that are currently on.
Happy to submit a PR, but I currently don;t have permission to create a branch, Cheers

I noticed monster card was deprecated in favor of the auto-entities card so I began migrating over. However it seems to have broken a couple of my cards around task management. For example here is one that used to work when the type was 'custom:monster-card':

- card:
    columns: 2
    show_state: true
    type: glance
   filter:
    include:
    - attributes:
        repeat: '> 0'
       entity_id: input_datetime.recurring_task_*
       options:
        format: relative
        secondary_info: last_updated
        tap_action:
         action: call-service
         service: script.set_datetime_to_now
         service_data:
          id: this.entity_id
   type: 'custom:monster-card'

When i change the type of this one to 'custom:auto-entities' the card itself renders the same but the tap action does not work. My script is no longer passed in the ID of what was clicked, instead of it is just passed in the text "this.entity_id".

Is there new syntax for using the ID in things in auto-entities vs. monster-card that I have to use now? Or do I have to stick with monster-card until this use case can be supported by auto-entities?

Is it possible to use this with Custom Updater?

Would it be possible and if yes, would you consider to add an option to change the title when the card is empty.

Specifically, I use it to display the status of the London Underground Lines with problems. If there are no problems I'd like to change the title to reflect that.

This is how it looks now but Id like to say something like "No reported problems" when all lines have a good service.

Hi, this is a double feature request, as there's two improvements to sorting I would like to see:

Firstly I would like to be able to sort by area.

Secondly I would like to be able to provide a list of sorting methods, so that entities that compares equally with the first method are sorted by the second method, and so on.

Combined, this will let me have entities appear room by room with each room sorted alphabetically.

I have some battery state entities. So this entites have the battery value as state. They also have this value as an attribute (json_attributes_topic, zigbee2mqtt autodiscover devices)

This works fine:

        filter:
          include:
            - entity_id: "sensor.zigbee_*_battery"
              attributes:
                battery: "< 20"  

But why can't I use the state instead of attributes? Like this?

        filter:
          include:
            - entity_id: "sensor.zigbee_*_battery"
              state: "< 20"  

What am I doing wrong? I also testet

        filter:
          include:
            - entity_id: "sensor.zigbee_*_battery"
            - state: "< 20"  

without luck.

I've implemented HA MQTT auto discovery in another device but fairly new to HA. Within 'integrations' in HA the entities get created grouped under a parent 'device' - this is working well.. e.g. parent device BackDoor in this screenshot.

So - can I access this 'BackDoor' device name as some parameter/attribute in auto-entities, to create a card that contains all the devices entities ? Not all entities necessarily have 'BackDoor' in their name

Following on from that if I chose to name my devices accordingly e.g 'BackDoor _#' could I set up auto-entities to find all devices matching '*_#*' and auto create separate cards in Lovelace for each device as it gets added via MQTT auto discovery ?

More of a feature request than an issue - was hoping sorting by attributes would allow this (maybe I'm doing something wrong?).

I have a use-case for this where I'm monitoring lots of equipment through home assistant and have an auto-entities card which shows anything that's fallen offline. I'd like to be able to sort this based on how long its been offline (i.e. lastest state-changed) to suit the way fixing things is prioritised.

This would also be useful for some motion sensor cards to be able to see more of a live 'feed' of active motion sensors throughout a house :)

looks as though i can't set my card type to anything like 'media-control' or 'custom:mini-media-player' because

mini-media-player Error: Specify an entity from within the media_player domain.
    at HTMLElement.setConfig (mini-media-player-bundle.js?v=1.0.2:1)
    at _createThing (card-tools.js?track=true&v=0:82)
    at Function.createThing (card-tools.js?track=true&v=0:112)
    at Function.createCard (card-tools.js?track=true&v=0:133)
    at HTMLElement.setConfig (auto-entities.js?v=be1323:12)
    at create_card_element_createElement (401352253e833b70a294.chunk.js:4823)
    at createCardElement (401352253e833b70a294.chunk.js:4823)
    at HTMLElement.createCardElement (401352253e833b70a294.chunk.js:5614)
    at config.cards.forEach (401352253e833b70a294.chunk.js:5693)
    at Array.forEach (<anonymous>)

or

hui-media-control-card Error: No entity specified
    at HTMLElement.setConfig (401352253e833b70a294.chunk.js:3896)
    at _createThing (card-tools.js?track=true&v=0:82)
    at Function.createThing (card-tools.js?track=true&v=0:112)
    at Function.createCard (card-tools.js?track=true&v=0:133)
    at HTMLElement.setConfig (auto-entities.js?v=be1323:12)
    at create_card_element_createElement (401352253e833b70a294.chunk.js:4823)
    at createCardElement (401352253e833b70a294.chunk.js:4823)
    at HTMLElement.createCardElement (401352253e833b70a294.chunk.js:5614)
    at config.cards.forEach (401352253e833b70a294.chunk.js:5693)
    at Array.forEach (<anonymous>)

I know that the error associates itself with card-tools but i think it just may be returning zero results from the filter in auto-entries. thus... opening the issue on this repo and not on card-tools.

Thanks for your help! love all the work you've put into lovelace.

btw here is my lovelace card:

type: 'custom:auto-entities'
card:
  type: media-control
filter:
  include:
    - domain: media_player

Had a go at moving to auto-entities (from monster card) a few weeks ago and had this same issue, just gave it another go and I'm having the same problem.

The Lovelace card layout when using auto-entities doesn't seem to shuffle things correctly, it seems to treat all cards as having a height of something small, regardless of if they have lots of entities.

As an example:
Using Monster Card:

Using Auto-Entities:

This example doesn't seem too bad/unusable, however, it's doing the same behaviour with an auto-entities card with twice the entities (which makes the page long unnecessarily long and require scrolling).

Tried the usual clearing cache, etc.

Can i use this with a cart that does not have a entities attribute?
In my case i want to use it with plant status but as it does not have a entities attribute i don't think i can?

Show empty functions correctly for a glance card:

type: 'custom:auto-entities'
show_empty: true
card:
  type: glance
  title: Doors Open
filter:
  include:
    - entity_id: "binary_sensor.*door"
      state: 'on'

But not for an entities card:

type: 'custom:auto-entities'
show_empty: true
card:
  type: entities
  title: Doors Open
filter:
  include:
    - entity_id: "binary_sensor.*door"
      state: 'on'

Note that binary_sensor.*door was quoted but the UI editor strips out the quotes when the card is saved and then opened again for editing.

All working on v87.1, but upgrading to v88.1 the custom card seems to be broken, have updated to the latest version of the custom-card, without any joy!

Hello and thanks for this great module!

I'm using auto-entities in many cards, including a card that shows all battery-powered devices. I recently set up sorting based on state, but the sort was strange:

I realized that it's doing a straight string comparison (comparing the first digit first, then the second, etc), which doesn't work very well when dealing with numbers.

It would be awesome if the sorting method took numbers into account. I see a few ways this could be added:

1. A separate numeric_state sort method to use instead of state.
2. A new option to sort numerically (similar to ignore_case).
3. In sort.js, the compare() method could always check if both states can be converted to numbers with Number(), and if so, they could be compared numerically.

I'd be happy to submit a PR with my attempt at adding one of these options, but I wanted to check and see if any of these seem like good solutions to you. What do you think?

I'm trying to filter a group of alexa audio players that are in a playing or paused state, but when I run the following, I see ALL devices in that group AND other media player devices in a play/paused state.

How do I do filtering where a device has to be in a particular group AND is in state playing OR state paused?

lt;dr Can you do and/or in include filtering?

card:
  type: entities
filter:
  include:
    - group: group.audio_players
      options:
        group: true
        hide:
          controls: true
          icon: true
          power: true
          source: true
        type: 'custom:mini-media-player'
    - state: paused
    - state: playing
type: 'custom:auto-entities'

Sorting by name seems to be super broken.

  - type: custom:auto-entities
    unique: true
    sort:
      method: 'name'
    card:
      title: Gaming
      type: entities
      show_header_toggle: false
    filter:
      include:
        - entity_id: script.living_room_play_*

This gives me the following result.

I also tried the following with no difference:

    sort:
      method: 'attribute'
      attribute: 'friendly_name'

ignore_case and numeric don't change anything either.

Migrating from monster card, where it filtered duplicates by default.
I added in the unique: true parameter, but i still get duplicate media_player.plex entities.

card:
  show_header_toggle: false
  title: Media Players
  type: entities
filter:
  include:
    - entity_id: 'media_player.plex*'
      options:
        artwork: cover
        group: true
        hide:
          power_state: false
          progress: false
          runtime: false
          volume: false
        icon: 'mdi:plex'
        idle_view:
          when_idle: true
        info: scroll
        type: 'custom:mini-media-player'
    - domain: media_player
      options:
        artwork: cover
        group: true
        hide:
          power_state: false
          progress: false
          runtime: false
          volume: false
        idle_view:
          when_idle: true
        info: scroll
        type: 'custom:mini-media-player'
  exclude:
    - state: idle
    - state: 'off'
    - state: unavailable
    - entity_id: media_player.ua55c8000_samsung_dtv_rcr
show_empty: false
unique: true
type: 'custom:auto-entities'

secondaryinfo-entity-row (https://github.com/MizterB/lovelace-secondaryinfo-entity-row) provides a functionality to customize the secondary row of an entity. However the templating language provided by card-tools to secondaryinfo-entity-row requires the template to start with a fully qualified entity (with domain).
The problem in combination with auto-entities is that we don't know the entity.

- type: custom:auto-entities
  card:
    type: entities
    title: Docker
    show_header_toggle: false
  filter:
    include:
      - entity_id: "switch.ha_dockermon*"
        options:
          type: "custom:secondaryinfo-entity-row"
          secondary_info: "[[ whatever-comes-here ]]"

Is there any way auto-entities can support generating that template?

I have a card configured like this:

          - type: entities
            title: Automations & Scenes
            show_header_toggle: false
            entities: 
              - type: custom:auto-entities
                card:
                  type: custom:fold-entity-row
                  head:
                    type: section
                    label: All Automations
                  open: false
                filter:
                  include:
                    - entity_id: "automation.*"
              - type: custom:auto-entities
                card:
                  type: custom:fold-entity-row
                  head:
                    type: section
                    label: Scenes
                  open: false
                filter:
                  include:
                    - entity_id: "scene.*"

Which looks like this:

Exactly what I want.

However, it is showing
group.all_automations
group.scenes

Neither of those match the pattern......

Great work, love the card!

I have installed via HACS (latest) and my auto-entities card works well using Chrome on my PC - however, when looking at the same page via the Home Assistant Companion App or iOS Safari on a iPad 4 (iOS 10.3.3, latest available), it shows the red card stating that "Custom element doesn't exist: auto-entities" and then the configuration.

Is this perhaps a javascript problem? And if so, it seems that this is the only custom card that appears to be having issues with it.
I have tried using:

frontend:
  javascript_version: auto
AND
frontend:
  javascript_version: latest

I am using this is the lovelace-ui :

    url: /community_plugin/lovelace-auto-entities/auto-entities.js
  - type: module

What a great component to track battery states. This already works fine with battery that report a certain value.

However netatmo devices report their state in "full" and other states I don't know yet (because all are full).

Is it possible to add the possibilty to for a "not_state".

something like this

filter:
  include:
    - domain: sensor
      not_state: "full"

or is this already possible, maybe like this?

filter:
  include:
    - domain: sensor
      state: "! full"

I have this code, and works well: when the listed entity_id have power above 2 are shown in the card. Unfortunately are shown not with its icon, but with the generic FLASH icon, is it possible to change this?

      - id: power_on
        type: custom:auto-entities
        show_empty: true
        card:
          type: entities
          title: Switch consuming power
          show_header_toggle: false
        filter:
          include:
            - entity_id: "sensor.dining_room_ac_power"
              state: "> 2"
            - entity_id: "sensor.guest_room_ac_power"
              state: "> 2"

Is it possible to filter by device_class?

I just switched to this (together with bar-card) for battery levels and temperatures, and would like to get all temperature sensors by device_class instead of specifying each temperature sensor one by one. The name of my sensors doesn't help, it's Xiaomi Aqara sensors called sensor.<room>_multi_sensor and possibly a number afterwards (temperature, air pressure, humidity) which seem to vary for different sensors.

Hassio NUC image, v0.102.2
Windows 10 Pro 64 bit 1903 (build 18362.418)
Firefox 64 bit 70.0.1

With the following card configuration, view navigation stops responding or becomes very delayed if the view with this card is left open in the browser for some time (less than 15 minutes):

cards:
  - card:
      style: |
        ha-card {
          border: solid 2px #FF6262;
          --ha-card-background: rgba(0, 0, 0, 0);
          --primary-text-color: rgb(250,98,98);
          box-shadow: 0px 0px 10px 3px #FF6262;
        }
      title: Smoke Detected
      type: glance
    filter:
      include:
        - entity_id: binary_sensor.smoke*
          state: 'on'
    show_empty: false
    type: 'custom:auto-entities'
  - card:
      style: |
        ha-card {
          border: solid 2px #FF6262;
          --ha-card-background: rgba(0, 0, 0, 0);
          --primary-text-color: rgb(250,98,98);
          box-shadow: 0px 0px 10px 3px #FF6262;
        }
      title: Water Leak
      type: glance
    filter:
      include:
        - entity_id: binary_sensor.dishwasher_leak
          state: 'on'
        - entity_id: binary_sensor.laundry_leak
          state: 'on'
        - entity_id: binary_sensor.sink_leak
          state: 'on'
    show_empty: false
    type: 'custom:auto-entities'
  - card:
      style: |
        ha-card {
          border: solid 2px #FF6262;
          --ha-card-background: rgba(0, 0, 0, 0);
          --primary-text-color: rgb(250,98,98);
          box-shadow: 0px 0px 10px 3px #FF6262;
        }
      title: Unavailable
      type: glance
    filter:
      exclude:
        - entity_id: '*mailbox*'
        - entity_id: '*laneway*'
        - entity_id: '*lane_gate*'
        - entity_id: binary_sensor.shed_door
        - entity_id: binary_sensor.updater
      include:
        - domain: sensor
          state: unavailable
        - domain: binary_sensor
          state: unavailable
        - domain: light
          state: unavailable
        - domain: switch
          state: unavailable
    show_empty: false
    type: 'custom:auto-entities'
type: vertical-stack

Example gif:

(Apologies I just realised I cropped the card out in an effort to reduce the gif size, but it is the delayed navigation that is the focus).

The more auto-entities cards in the view the quicker the problem appears and the more severe it becomes - to the point that view navigation stops altogether and a page reload is required.

The really bad news is that there are no errors in the inspection console and task manager does not show excessive RAM or CPU use for the browser.

Likewise home assistant is not showing excessive CPU, network or RAM use.

This issue occurs worst in Firefox. It does occur in Chrome but takes a lot longer.

show_header_toggle: false doesn't work. The header toggle stills shows. I refreshed the page and restarted ha.

      - type: custom:auto-entities
        show_empty: false      
        show_header_toggle: false
        card:
          type: entities
          title: 'scripts'
        filter:
          include:
            - entity_id: "script.*"