#Expanding Entities / Group Card

1 messages · Page 1 of 1 (latest)

rigid mason
#

I have a few lighting groups set up that I used to have created in YAML. When I would long press on a button, it would bring up a pop up that I could then see each light and switch in the group. I recreated all my groups and automations using UI yesterday and now that functionality is gone. Is there some form of expanding entities card that would allow me to only see the main group and then when long pressed, open up to show all the entities in the group? Thank you!

wind flicker
#

Changing from a configuration-based light group to a UI-made light group shouldn't have changed any functionality, especially if you re-used the entity_id from the original group. From what you describe, there is no functionality built in to HA that does that (at least not that I can think of) so you're more than likely dealing with something custom.
Going back to the light group, what changed with these new groups? Did you give them new entity_ids? Are the old groups still enabled? Did you make a new dashboard and, if so, what's the status of the old dashboard? There has to be something else somewhere that has changed.
In terms of pop-ups, two main methods are browser_mod (not easy to set up but pretty powerful) and Bubble card (easy to set up, powerful, and colorful). Browser_mod probably would take some work to make it look right unless you put together a template in an auto entities card.

rigid mason
#

So I created the groups via YAML and they were groups.family_room_lights for example.

I recreated my groups via the UI and they are now light groups after changing switches to lights. This group is now light.family_room_lights.

Via helpers, there is no way to keep the group suffix from what I can tell. So when I create a light button or similar, i now use light.family_room_lights and when long pressing the button, it brings up the color options, not individual light toggles for the group.

#

Yaml group long press

image.png
#

light group long press

image.png
#

bubble might be a solid solution, I still would love to know how to get group.family_room_lights to work in the above case. @wind flicker

rustic orbit
#

You've been using "old style groups" they're not favored anymore and you're supposed to use the "new style" like you are now since they slot in as a single entity into whatever domain you choose (light, cover, etc.) They appear as a single entity and therefore do not support the multiple switch feature.

#

I'm currently experimenting with "custom features for tile cards" from HACS to solve my multiple light switch issue on my dashboard

inland hearth
#

I've seen there's a PR in the works to add some kind of group state expansion into more-info, but it doesn't look like it got too far yet.

rigid mason
#

yeah it seems like the bubble card pop up will work really well and it gives me some more options to play with but more set up. i'll play around but good to know there are some features in the works.

wind flicker
# rigid mason Yaml group long press

This screenshot kind of tripped me out at first. I thought to myself: that's an entities card, but... there's a header with configuration buttons. How was that possible?
Next, I noticed the entity_id: groups.family_room_lights. I was not aware of a groups domain. So, I did some research and, sure enough, it is a legacy option that still works but is not recommended. Old style groups

We don’t recommend using these old-style groups anymore. They are still supported, but we recommend using the groups as described above.
I can see the potential havoc running an old-school groups entity with modern services (light.turn_on, etc) since you can't send a light.turn_on command to a group that contains switch entities (which I'm assuming you already figured out.)
...Damn. I just read @rustic orbit 's comment... Guess that's what I get for not reading over everything before trying to figure things out. 🤦‍♂️

#

I have an idea that might be able to replicate to legacy feature on a dashboard. I'll have to tinker with it later but I'm thinking a browser_mod pop, with an auto entities card using a template to expand the current group into an entities card via templated options. (It makes sense in my head; I just need to make it all come together.)
But, for the time being, the Bubble Card pop-up is a viable option.

wind flicker
#

This actually turned out to be easier than I thought. Turns out, I didn't need to use a template; the auto entities card can automatically handle groups. This example uses a custom:button-card because I wanted to use a variables, an auto entities card to expand the group, browser_mod for the pop-up, and card_mod to hide the border of the entities card because it looked silly in the popup.

# 
type: custom:button-card
variables:
  entity: light.bedroom_lights
entity: "[[[ return variables.entity ]]]"
hold_action:
  action: fire-dom-event
  browser_mod:
    service: browser_mod.popup
    data:
      timeout: 5000
      content:
        type: custom:auto-entities
        filter:
          include:
            - group: "[[[ return variables.entity ]]]"
        card:
          type: entities
          title: "[[[ return states[variables.entity].attributes.friendly_name ]]]"
          show_header_toggle: false
          card_mod:
            style: |
              ha-card {
                border: none;
              }
20250712-0525.gif