Group in a group visible when it shouldn't with 42.2 upgrade

Configuration
1

With the recent upgrade, I am experiencing a visible group on the front end when its not in the view.

I have group A in another Group B. When I put Group B on the front end default view or other tab/view, Group A appears in Group B as expected but also Group A appear by itself which is unexpected and new.

2

I just tried setting up something similar with the same result. I was hoping to come here for an answer.
I put group A and B into C. Both appear in C but also appear as their own cards.
I tried hiding groups A and B in cuztomize.yaml but that just seems to break all three cards.

Any help for us both would be great.

3

Some problem. Example:
> group1: G11
>…G12
…G13
> group2: G21

Tab view:
> group3: group1
> …group2
>…G11
>…G12
>…G13
>…G21
Result is group3 + group1 and 2 in cards.
Any solutions? Version HA 0.44.1

4

The following is my group setup for my Den. Apparently when I include a sensor (possibly other entities too) in a view:yes group, it makes the sensor visible in any view:no groups in exists in and causes them to display on the screen as well. In the groups below, everything is expected, except for the entity_den_sensor group in the upper left corner of the screen shot below. That group should not be visible. Running 44.1

entity_den_sensor:
  view: no
  entities:
    - binary_sensor.den_sensor_sensor_14_0
    - sensor.den_sensor_alarm_type_14_0
    - sensor.den_sensor_alarm_level_14_1
    - sensor.den_sensor_sourcenodeid_14_2
    - sensor.den_sensor_luminance_14_3
    - sensor.den_sensor_relative_humidity_14_5
    - sensor.den_sensor_burglar_14_10
    - sensor.den_sensor_temperature_14_1
    - sensor.den_sensor_battery
    - input_boolean.denmotion



room_den:
  view: no
  entities:
    - light.den_fan_light
    - light.den_fan
    - switch.den_power_outlet
    - switch.front_door_light
    - media_player.den_directv
    - media_player.dentv
    - media_player.apple_tv
    - light.stairway_light_switch
    - input_boolean.partyoverride
    - sensor.den_sensor_temperature_14_1
    - group.entity_den_sensor



view_header:
  view: no 
  name: "Current Time"
  entities:
    - sensor.time
    - sensor.date


view_den:
  view: yes
  name: Den
  entities:
    - group.view_header
    - group.room_den
    - group.room_kitchen
    - group.room_breakfastroom
    - group.room_back_patio
    - group.room_landing
    - group.room_upstairs_hallway
    - light.stairway_light_switch

image.jpg1950×1267 229 KB

5

An interesting effect is described below although I don’t think it solves anything.

I have three groups

  • Kitchen light Alert group with only kitchen light in it
  • Alert group with Kitchen light Alert group
  • Switches with Kitchen light switch in it

This screen shot has alert group without switch group and without the Kitchen light Alert group

image.png1493×957 64.9 KB

but when i add the switch group, the Kitchen light Alert group appears although its not included in this view.

image.png2299×674 59.5 KB

6

It’s the same as what’s happening to me. As soon as you make a group containing an object visible, any other groups containing that object appear to become visible at least for that one object. You added switches, which has kitchen lights in it, so the kitchen light alert window showed up too.

7

I think I find something … I try today.
https://home-assistant.io/docs/configuration/group_visibility/#the-complete-example
For every group which I create, I must to add an automation like this:

- alias: hide timer
  hide_entity: false
  trigger:
    platform: state
    entity_id: group.timer1
    state: 'off'
  action:
    service: group.set_visibility
    entity_id: group.timer1
    data:
      visible: False

You must to verify because “hide timer automation” action just when it triggered. When you want to reactivate, after trigger, you must to “reload core” , not just refresh page browser.