(Nested) Group showing with a toggle..? (and not state Home/Away)

Configuration
1

having not used 2 groups in my Lovelace frontend before (only used them for backend logic) Ive now added them to a card, and am surprised to see them having a toggle, and not showing the state. Is this to be expected?

Schermafbeelding 2020-06-10 om 15.07.27
Schermafbeelding 2020-06-10 om 15.07.27764×980 63.4 KB

lovelace:

  - type: entities
    title: At home
    entities:
      - entity: binary_sensor.family_home
        secondary_info: last-changed
      - entity: sensor.family_home
        secondary_info: last-changed
      - type: divider
      - entity: group.family
        secondary_info: last-changed
      - entity: group.family_home
        secondary_info: last-changed
      - type: divider
      - entity: binary_sensor.daughters_home
        secondary_info: last-changed
      - entity: sensor.daughters_home
        secondary_info: last-changed
      - type: divider
      - entity: group.daughters
        secondary_info: last-changed
      - entity: group.daughters_home
        secondary_info: last-changed

the 2 groups are defined as:

  family_home:
    name: Familie Home
    icon: mdi:home-heart
    entities:
      - group.daughter_1
      - group.daughter_2
      - group.daughter_3
      - group.daughter_4
      - group.she
      - group.me

and

  daughters_home:
    name: Daughters Home
    icon: mdi:human-child
    entities:
      - group.daughter_1
      - group.daughter_2
      - group.daughter_3
      - group.daughter_4

(… edited the actual names :wink: )

of course these groups exist of yet multiple entities again)

why the toggle, because when toggling an error is displayed it cant find a service device_tracker/turn_on, which is correct of course. and, though the toggle does change position, the entity doesnt change state.

so, I am somewhat confused…

2 
  - type: entities
    title: At home
    show_header_toggle: false
    entities:
      - entity: binary_sensor.family_home
        secondary_info: last-changed
      - entity: sensor.family_home
        secondary_info: last-changed
      - type: divider
      - entity: group.family
        secondary_info: last-changed
      - entity: group.family_home
        secondary_info: last-changed
      - type: divider
      - entity: binary_sensor.daughters_home
        secondary_info: last-changed
      - entity: sensor.daughters_home
        secondary_info: last-changed
      - type: divider
      - entity: group.daughters
        secondary_info: last-changed
      - entity: group.daughters_home
        secondary_info: last-changed
3

ha yes, I know that’s for the group toggle in the title of the card. I meant the 2 individual toggles for group.family_home and group.daughters_home though. They are groups, and I can not toggle them…

4

I think it depends on what the group contains. All of these are groups:

Screenshot_2020-06-10 Administration - Home Assistant

The middle one is a group of binary sensors, so no toggle.

I can toggle the ones that have them.

5

yes, that’s what I thought. Standard behavior.

These groups only contain device_trackers though… as is reflected in the error I get when trying to toggle.

as you can see the entities just above the toggled ones, show Home just as I would expect them to, these also are groups, but with individual device_trackers. (btw, these device_trackers are of the composite integration, so contain several trackers themselves …;=)

6

still experiencing this without a hunch of an idea where to find a solution…

7

Actually from what you posted those groups contain groups.

Did you open an issue?

8

I was referring to the groups within the groups. The group with the toggles indeed contain only groups.

No, I didn’t yet file an issue

9

That’s how you get it looked at. You know that buddy.

10

ok. if have now: group with nested groups shows toggle instead of state home/not_home · Issue #6599 · home-assistant/frontend · GitHub