In the UI, when you click on a group and go to the Related tab it shows the group under the Integrations section which then just navigates to the default integrations page. The only way to see the members is to go to the Settings tab and click on Group Options but itās still not possible to open a group member from there.
Add the ability to open a member from within the group. 
My WTH issue was Closed and pointed to here.
My issue is related to controlling entities within a group.
Old method allowed the individual control of entities from the More Info action.
Helper method for two lights doesnāt have this ability.
+1 from me
from my point of view this is the biggest drawback of the helper-created groups and where the yaml-created groups still shine.
From my point of view this is a classic āWTH?!?ā because both group styles bring their individual problems which only their respective counter-parts solve! 
There are already so many topics around about this and some of them are years old. Most of them ask to change the group icon of the old-style groups depending on the overall group state. This is what the new groups can do. But youāll loses the access to the individual group members. WTH?!
The new groups are nothing more but a sum of logic signals. While on the other hand the old groups are really āgroupsā with a much more versatile and complex structure - they just suffer from not being able to represent a device class!
I was about to open an issue/topic asking why my group in yaml looks like this:
Where I can see the individual states of each member, while the one generated with the UI only shows this:
With this information, I canāt even know if both sensors are working or if only one does. Why the hell did the old useful UI has been dropped??
Same question here!
How see or change the group members from the created (helper) group?
Really looking forward for this to be fixed.
Iāve worked my way around this issue. Iām working a lot with auto-entities as I want it to be scalable and found the solution today (after I did some careful reading).
Iāve created light groups through the UI and have those filtered with GitHub - thomasloven/lovelace-auto-entities: š¹Automatically populate the entities-list of lovelace cards. On top of this Iām using a pop -up card with browser_mod GitHub - thomasloven/hass-browser_mod: š¹ A Home Assistant integration to turn your browser into a controllable entity and media player. On a tap/hold action I open up the pop-up card which is populated with the lights from the group which is clicked from the auto-entity group, this is made possible by the functionality this.entity_id. Up till now I didnāt know about this functionality and this has made me to solve this, as it is fully scalable now.
On top of the above Iāve used GitHub - piitaya/lovelace-mushroom: Mushroom Cards - Build a beautiful dashboard easily š to make the layout nice and shiny and the added value of this is that you can fully customize the look and feel together with the interaction as youāre not tied to the āmore-infoā menu.
The code Iāve used in my card, the trick is to use the right filters for your situation.
type: custom:auto-entities
card:
type: grid
columns: 2
square: false
card_param: cards
filter:
include:
- domain: light
entity_id: /group/
options:
type: custom:mushroom-light-card
use_light_color: true
show_brightness_control: true
show_color_control: false
collapsible_controls: false
show_color_temp_control: true
fill_container: true
layout: horizontal
hold_action:
action: fire-dom-event
browser_mod:
service: browser_mod.popup
data:
title: ' '
content:
type: custom:auto-entities
card:
square: false
columns: 1
type: grid
filter:
include:
- group: this.entity_id
options:
type: custom:mushroom-light-card
use_light_color: true
show_brightness_control: true
show_color_control: true
collapsible_controls: false
show_color_temp_control: true
fill_container: false
layout: horizontal
hold_action:
action: more-info
sort:
method: name
show_empty: true
card_param: cards
exclude: []
show_empty: true