Home Assistant Labels: Organize and Target the Right Devices

Use labels for a purpose that crosses rooms

Home Assistant labels let you select things by purpose without moving them out of their rooms. Keep each device in its real area, then add a label to the particular controls that should share an action. For a first setup, label two lamps “Evening lamps” and target that label with a light-on action.

An entity is one named control or reading, such as a lamp’s on/off control. A physical device may expose several entities. That distinction matters: labeling a two-channel device is broader than labeling just one of its light controls. Home Assistant’s organization guide explains the relationship between devices, entities and areas.

Use a category when you only want to tidy a settings list, such as putting lighting automations under one heading. Use a Light Group when you want one combined light control. Labels are useful when you want selected items to share an action while keeping their separate controls and room assignments.

Start by writing down the intended members, apply a new label directly to those entities, inspect its membership, and only then run an action. You do not need to rename or re-pair working devices for this exercise.

Researched from current Home Assistant documentation and the Core 2026.10.1 target-resolution code on October 14, 2026. The household below is an illustrative configuration, not a tested Tara installation. The cover is an AI-generated illustration.

Choose the organization tool that fits the job

On a phone, swipe the table sideways to read all columns.

An entity can have multiple labels, but only one area. Categories belong to their particular settings table: a category on the automation list does not become a collection of lights. See categories. If your goal is one shared dimmer, follow the Light Group versus area guide instead of expecting a label to create a new light entity.

1. Write a small membership plan

Imagine this home. The owner wants the reading lamp and hall lamp on together in the evening, while the ceiling light stays independently controlled. These entity IDs are examples; use the IDs shown in your own installation.

Swipe the table sideways to read all columns.

Check each lamp’s individual on/off control first. Use lamps that nobody depends on for a stairway, exit or other safety task, and keep their physical controls accessible. This walkthrough assumes both are already working, enabled, visible light. entities, with no other routine changing them during the test.

A lamp on a smart plug may appear as switch. instead. A light action will not switch it just because you gave it the same label. The light-group guide explains the optional Switch as X helper for a plug dedicated to a lamp; it does not give an ordinary plug dimming capability.

2. Create the label and apply it to the two entities

1. Open Settings → Areas, labels & zones → Labels. Choose Create label, name it Evening lamps, and save. Use a new, unused name for this exercise.
2. Open Settings → Devices & services → Entities. Find the two lamp controls from your plan.
3. Enter selection mode, select those two rows, and choose Add label → Evening lamps. Keep their existing area assignments.
4. Leave this new label off the devices themselves, their areas, and any other entities. You are deliberately making a small collection of individual controls.

The official label instructions show the selection controls. Menu placement can vary with the installed release. The important choice is the Entities tab, not the similarly named device list.

3. Preview the membership without changing a device

Open Settings → Tools → Template; older releases place Template under Developer tools. Paste this read-only check. A template is an expression that looks up information; these expressions do not send commands.

Label ID: {{ label_id('Evening lamps') }}
Entities: {{ label_entities('Evening lamps') | sort | list }}
Devices: {{ label_devices('Evening lamps') }}
Areas: {{ label_areas('Evening lamps') }}

For the example, the entity list should contain exactly light.hall_lamp and light.reading_lamp. Both Devices and Areas should show an empty list, []. Your label ID may be evening_lamps; copy the actual value rather than guessing it from the display name. If no ID appears, check the label name before continuing.

The functions have deliberately different jobs: label_id finds the internal identifier, label_devices lists directly labeled devices, and label_areas lists directly labeled areas.

An empty entity list does not prove a label action has no targets. label_entities lists only entities labeled directly. A label placed on a device or area can still reach its eligible entities when used as an action target. That is why this preview checks all three lists.

If Devices or Areas is not empty, remove the practice label from those entries and check again. If Entities contains an unexpected control, remove the label from that entity. These changes remove the label assignment, not the device. A listed entity may still be unavailable or excluded from indirect targeting; the preview is a membership audit, not proof that a command will succeed.

4. Test a label-only action on the two lamps

Once the lists match, create a new script under Settings → Automations & scenes → Scripts. A script is a saved sequence you can run yourself, so no schedule needs to start it during setup.

1. Add a Turn on light action, whose YAML name is light.turn_on.
2. Under Targets, select only the Evening lamps label. Remove any extra room, device or entity targets.
3. Leave brightness and color options unset. Save the script as Evening lamps on.
4. With both practice lamps off, run the script once. Both should turn on; the ceiling light should stay as it was. Observe the real lamps as well as their displayed states.

This is a real light command. Run it at a convenient time with the household aware. Return each lamp to its previous state using its individual control after the test. The action documentation explains targets and immediate execution.

If you prefer the script’s YAML editor, this is the equivalent. Replace evening_lamps with the ID from the preview. YAML is the text form of the same settings.

alias: Evening lamps on
mode: single
sequence:
  - action: light.turn_on
    target:
      label_id: evening_lamps

Only add this script to an existing evening routine after the supervised test. If you want different brightness levels for different lamps, a scene may fit better; the scenes versus scripts guide explains that next decision.

5. Avoid the “room plus label” trap

In an action target, selecting an area and a label combines their members. It does not restrict the label to that area. For our three-light example, here is what a light-on action selects:

Swipe the table sideways to compare all three outcomes.

This follows the additive target resolution in Home Assistant Core 2026.10.1. Multiple selected labels also collect members of either label. For “evening lamps in the living room only,” choose the reading-lamp entity directly in this small example. A dedicated narrower label is another option if that subset will be reused.

Similarly, labeling an entire multi-channel device can reach more than one eligible light control. Use an entity label for the single channel you intend. An action still applies only to supported entity types; a shared label does not turn a temperature reading into a switch.

If the result is different from your plan

Swipe sideways to read every column.

Treat an action label like a list of things you have authorized a routine to control. Adding another member can change the next run without editing the script. If replacing a failed lamp, check the replacement’s entity type and label deliberately; the device replacement guide covers preserving other references.

Common questions

Does a label automatically add a dashboard button?

No. It provides organization and a target for compatible actions. Add a control for the saved script if you want a button, or use a Light Group if you need a combined light entity.

Can the same lamp have more than one label?

Yes. A lamp could have both Evening lamps and Decorative lights. Review every action that uses either collection before adding it; one label does not cancel another.

Does labeling a cloud device make it local?

No. Labels change how Home Assistant organizes and selects controls. The device still uses its existing integration and connection, including any internet dependency.

Our recommendation is to keep rooms accurate and add one purposeful label at a time. If you are planning a larger installation, Tara’s configured Home Assistant setup is the relevant starting point for agreeing on device names and everyday routines.