My Home Assistant Light Group Disappeared

I had three RGB bulbs in my office and one YAML group that stopped existing after a Home Assistant update. No warning in the dashboard. No useful error in the logs. The entity was simply gone.

The replacement lives under Helpers. One group now gives me a single toggle, brightness slider, and color picker for all three bulbs.

I originally blamed Home Assistant 2026.5. That diagnosis was too neat. Home Assistant’s current Group documentation still supports YAML light groups. What I can say is narrower: my old entity stopped loading, recreating it as a Helper worked, and I preferred the result enough not to move it back.

What I could actually prove

The original way to create a light group was a platform: group entry in configuration.yaml:

light:
  - platform: group
    name: Office Colors
    entities:
      - light.office_color_1
      - light.office_color_2
      - light.office_color_3

The YAML was valid according to the documentation, but the entity did not appear in my instance. I checked the dashboard and logs, then removed the block and recreated the same membership through the UI. The Helper appeared immediately.

I did not isolate whether the failure came from the update, another configuration change, or something specific to my instance. Saying the platform had been removed turned an unresolved local failure into a product claim. It had not been removed.

Helpers replaced it

The Group Helper gave me the management path I wanted: I can change members, rename the group, and adjust its options from the UI. Home Assistant documents both the Helper and YAML paths; the Helper is a choice, not a forced migration.

The YAML approach couldn’t do any of that without a file edit and a restart.

Helpers also handle live reloads. Create a group, and it appears immediately. Delete it, and it disappears immediately. No restart cycle.

Creating the group

Go to Settings → Devices & Services → Helpers → Create Helper → Group → Light Group.

Name the group, select the member entities, and save. Home Assistant creates the group entity immediately.

I also enabled the option to hide the member entities. The group stays visible while the three bulbs stop filling the dashboard with duplicate controls. The underlying entities remain available to automations and scripts.

Color control

With my three RGB bulbs, the group exposes one color picker. Setting a color on the group sends the same hue, saturation, and brightness to every member.

Color temperature works the same way — one slider controls all members.

Mixed capabilities need testing. Home Assistant computes group behavior from its members, and not every combination produces an obvious control surface. I keep the three bulbs in this group the same type so I do not have to reason about the weakest member every time I change a scene.

Keep bulb types consistent within a group if you want full color control.

What HomeKit sees

My HomeKit bridge exposes the group as one accessory with color control.

Check HomeKit separately after saving the group. Inspect its accessory list for the group and any duplicate bulb controls. Bridge filters and entity visibility can change the result; hiding members in the Home Assistant dashboard is not enough to verify what HomeKit exposes.

The useful result was not that YAML became obsolete. It was that the Helper made this small piece of the house easier for me to inspect and change. That is enough reason to keep it.