Using with Auto Entities Card

[TScalzott]

Has anyone figured out how to get Bubble Card working with Auto-Entities (https://github.com/thomasloven/lovelace-auto-entities)?
I've tried several card_param values to no avail.

Thanks!

[s1mpleman]

This is what I do, hope it helps

  type: custom:auto-entities
  card:
    type: grid
    columns: 1
    square: false
  card_param: cards
  filter:
    include:
      - domain: light
        state: 'on'
        options:
          type: custom:bubble-card
          card_type: button
          button_type: slider
          show_attribute: false
          show_last_changed: true
          show_state: true
    exclude: []
  show_empty: true

[s1mpleman]

This is what it looks like inside a bubble pop up

[TScalzott]

This is what I do, hope it helps

  type: custom:auto-entities
  card:
    type: grid
    columns: 1
    square: false
  card_param: cards
  filter:
    include:
      - domain: light
        state: 'on'
        options:
          type: custom:bubble-card
          card_type: button
          button_type: slider
          show_attribute: false
          show_last_changed: true
          show_state: true
    exclude: []
  show_empty: true

Thanks for this. I'll give it a go.

[micahp2]

How about an example with styles included? I've tried something like this and only had failure so far:

• domain: switch
  area: Garage
  state: 'on'
  options:
  type: custom:bubble-card
  card_type: button
  button_type: slider
  show_attribute: false
  show_last_changed: true
  show_state: true
  styles: |
  .bubble-button-card-container {
  border-radius: 10px !important;
  .bubble-icon {
  opacity: 1;
  color: white !important;
  }

[lennon101]

@s1mpleman Thanks so much for that simple bit of yaml! works perfectly and I can fit and adjust it from there 👍

[HyperCriSiS]

Damn, Chatgpt and Claude could not solve this for many hours trying.
How do you put in a Popup? It still gets shown in the dashboard with this code:

type: custom:vertical-stack-in-card
cards:

• type: custom:bubble-card
  card_type: pop-up
  hash: "#clients"
  card_layout: large-2-rows
  name: Clients
  icon: mdi:devices
  scrolling_effect: false
  button_type: name
• type: custom:auto-entities
  card:
  type: grid
  columns: 1
  square: false
  card_param: cards
  filter:
  include:
  - domain: device_tracker
  options:
  type: custom:bubble-card
  card_type: button
  button_type: state
  show_attribute: false
  show_last_changed: true
  show_state: true
  exclude: []
  show_empty: true
  sort:
  method: friendly_name

Also I can't get two row sub button to work.
Are there some issues with auto entities?
Because when you click on cards in the auto entities section, none is selected.

Thanks
Hyper

[HyperCriSiS]

Problem was custom:vertical-stack-in-card
--> vertical-stack

[andyblac]

how would I use this with template ? here my current card

type: custom:auto-entities
card:
  type: entities
  show_header_toggle: false
  state_color: true
  card_mod:
    style:
      .: |
        ha-card: {
          --ha-card-background: none;
          box-shadow: none;
        }
        .card-content {
          padding-top: 0px !important;
          padding-bottom: 0px !important;
        }
      hui-toggle-entity-row:
        $: |
          hui-generic-entity-row {
            height: 25px;
          }
show_empty: false
filter:
  template: |
    {% for entity in state_attr('sensor.number_of_lights_on','entities') %}
      {{ entity.entity_id }}
    {% endfor %}
sort:
  method: friendly_name

[HyperCriSiS]

Did you try creating a sensor for the template and using this instead?

[andyblac]

Did you try creating a sensor for the template and using this instead?

it is a template sensor with a list of entities that I wants to monitor ( I don't want all lights monitored as some devices have LED indicators, etc), I want the popup to list the lights and let me turn them off etc.

[HyperCriSiS]

What I mean is, that you create the template sensor as helper, which creates a sensor entity.
And then you can use the sensor entity for auto-entities.

[andyblac]

sorry I don't think you understand what I'm after. this is what I have ATM

using this code:

type: custom:auto-entities
card:
  type: entities
  show_header_toggle: false
  state_color: true
  card_mod:
    style:
      .: |
        ha-card: {
          --ha-card-background: none;
          box-shadow: none;
        }
        .card-content {
          padding-top: 0px !important;
          padding-bottom: 0px !important;
        }
      hui-toggle-entity-row:
        $: |
          hui-generic-entity-row {
            height: 25px;
          }
show_empty: false
filter:
  template: |
    {% for entity in state_attr('sensor.number_of_lights_on','entities') %}
      {{ entity.entity_id }}
    {% endfor %}
sort:
  method: friendly_name

what I am after this same but using bubble card buttons, instead of just toggle switch. like this

with this code:

type: custom:auto-entities
card:
  type: grid
  columns: 1
  square: false
card_param: cards
filter:
  include:
    - domain: light
      state: 'on'
      options:
        type: custom:bubble-card
        card_type: button
        button_type: slider
        show_attribute: false
        show_last_changed: true
        show_state: true
sort:
  method: friendly_name
show_empty: true

But as you can see it show 2 LED light entities are from my meross socket extension led indicators, I do not want to track, this is why I can't use light domain in auto-entities, and use my own template sensor to keep track of what lights are on.

[HyperCriSiS]

Did you try with additional exclude filter?
Or you can also use include with additional filters.
That should work to get rid of the lights you do not want to track.

[andyblac]

Did you try with additional exclude filter? Or you can also use include with additional filters. That should work to get rid of the lights you do not want to track.

as I said I don't want to use domains, I want use my template sensor that already does the tracking I want, so I take it this is not possible with bubble cards and auto-entities ?, this is why I wish Bubble card would add the ability to allow the use templating....