Scenes: A Saved State for Several Devices at Once

Every helper built so far in this module stores exactly one value. A scene stores something genuinely different, the combined state of several devices at once, captured as a single named snapshot you can recall with one tap, no automation logic required at all.

What a scene actually is

A scene is genuinely a saved list of entities paired with the exact state each one should be in, this light at 40 percent brightness, that light off, this switch on, captured together under one name. Activating a scene simply pushes every one of those saved states out at once, restoring the exact combination you captured, regardless of whatever state those devices genuinely happened to be in a moment beforehand.

Why a scene instead of an automation

Building an automation to set five devices to five specific states would genuinely work, but it means writing out every single action by hand and then updating that list manually each time you change your mind about one device. A scene captures the current, already-correct state of every device you choose with one click, considerably faster to create and just as fast to update later, since you simply arrange things exactly the way you want and save again.

Step 1: create a "Movie Night" scene

From Settings, Automations & Scenes, Scenes, add a new scene named "Movie Night." Arrange your devices exactly how you'd genuinely want them, living room light dimmed low, hallway LED off, office LED off, then add each of those entities to the scene, capturing their current state automatically as you add them.

Recording the scene's entities in your notebook

Write down the scene's exact entity list and each one's captured state the moment you save it, so months from now you genuinely remember what "Movie Night" is actually supposed to do without needing to reopen the editor just to check. This same habit, small and quick, has paid off repeatedly throughout this module already for every helper created so far.

Activating the scene manually

Add scene.movie_night to your dashboard as a simple button, then change one of its devices, brighten the living room light, for instance, and press the button. Every entity in the scene should snap back to its captured state at once, confirming the scene genuinely activates as a single, reliable unit rather than partially or inconsistently.

Calling a scene from an automation

A scene becomes genuinely more powerful once an automation activates it automatically, a scene.turn_on action targeting scene.movie_night, triggered perhaps by a dedicated button press or a specific time of evening. This combination, an automation's trigger paired with a scene's saved combination of states, replaces what would otherwise require several separate device-turning actions listed out individually inside the automation itself.

Updating a scene after devices change

If you add a new light to the living room later and want it included in Movie Night too, simply reopen the scene, arrange the new light how you want it, add it to the scene's entity list, and save. The scene editor always captures each entity's live state at the moment of saving, so there's genuinely no separate step for updating a value, you just arrange things correctly and save again.

What can genuinely go wrong

A scene captures whatever state an entity happened to be in the moment you added it to the editor, so accidentally saving a light while it's the wrong color or brightness bakes that mistake permanently into the scene until you fix it. Always double-check every entity's state carefully right before saving, rather than assuming the editor's snapshot matches what you actually intended.

A hands-on exercise: build a second scene

Build a second scene of your own choosing, "Good Morning," perhaps, capturing whatever combination of lights genuinely suits how you like to start your day. Record its entity list in your notebook exactly as you did for Movie Night, then test both scenes back to back, confirming each one restores its own distinct combination correctly regardless of which scene ran most recently.

Scenes versus scripts, a preview

A scene is genuinely limited to setting entities to fixed, predetermined states, it can't wait, branch on a condition, or call another action first. The next lesson introduces scripts, which handle exactly that kind of sequential, conditional logic, and the two work together naturally, a script that waits five seconds and then activates a scene is a genuinely common and useful pattern you'll build shortly.

A scene does not remember what came before it

Activating a scene is genuinely a one-way action, it pushes the saved states out and forgets entirely what your devices were doing beforehand, there's no built-in "undo" or "return to previous state" waiting for you afterward. If you'd like a way back to whatever was happening before Movie Night started, you'd genuinely need a second scene capturing that earlier arrangement, saved deliberately before you ever activate the first one.

Scenes and helpers working together

A scene can genuinely include helper entities too, not just lights and switches, an input_boolean flag or an input_select mode can be part of a scene's saved snapshot exactly like any other entity. This means activating one scene can simultaneously set a room's lighting and flip a related mode flag together, keeping your dashboard's helpers and your physical devices in sync automatically rather than needing separate manual steps for each.

Naming scenes clearly and consistently

As your collection of scenes grows, a genuinely consistent naming pattern, "Movie Night," "Good Morning," "Away," each a short, clear, purpose-driven name, keeps a dashboard full of scene buttons instantly understandable at a glance. Avoid vague names like "Scene 1" or "Test," they read fine the day you create them but become genuinely confusing within weeks once several more scenes have joined the list.

How many devices belong in one scene

There's genuinely no fixed rule for how many entities one scene should include, two lights and a switch is entirely reasonable, and so is a dozen entities spanning several rooms at once for something like a whole-house "Away" scene. A useful guide is to ask whether every entity in the scene genuinely belongs to the same real-world moment you're trying to capture, if two devices don't logically belong together, they probably deserve two separate scenes instead of one crowded one.

A closing thought on snapshots versus rules

Everything built earlier in this module, timers, thresholds, flags, describes a rule, a relationship that keeps holding true as conditions change. A scene is genuinely the opposite idea entirely, a single frozen snapshot of exactly how things should look at one specific moment, and both approaches turn out to be equally valuable once you're genuinely building a real home that needs both kinds of logic working comfortably side by side.

Key takeaways

What's next

With two working scenes in place, the next lesson introduces scripts, a reusable sequence of actions you can call by name from any automation, any dashboard button, or any other script.