DSG Metro logo

Dealer Guide

Scene Planning Guide

Scenes are where automation becomes easy to understand. Use this guide to define the routines, rooms, systems, names, triggers, and customer expectations behind each scene before programming begins.

Start Here

Build scenes around routines customers already understand.

A scene should reduce steps. The customer should be able to press one button, tap one command, or trigger one routine and trust the home to respond correctly.

Define the scene before programming it.

Confirm the scene name, systems included, room behavior, and trigger method so the final system feels intentional.

Entertain

Lighting adjusts, music starts, outdoor areas activate, shades move, and common spaces feel ready for guests.

Movie

Lights dim, shades close, display or projector powers on, the right source is selected, and audio moves to the correct mode.

Dinner

Dining and kitchen lighting shift to warmer levels, music plays at a comfortable volume, and adjacent spaces support the mood.

Goodnight

Interior lights turn off or dim, exterior lights stay on as needed, shades move, security arms, and thermostats adjust.

Away

Lighting, shades, climate, audio, security, and access settings move into a reliable away-from-home state.

Morning

Selected shades open, lights come up gently, audio starts in key areas, and the home transitions into the day.

Planning Sequence

Plan the routine before programming the command.

Scene planning should happen before programming. Confirm what the client expects, what systems are included, how the scene starts, and what happens when it ends.

1

Start With Daily Routines

Ask what the customer does every day, every night, when entertaining, when leaving, and when returning home.

2

Define the Room Behavior

Scenes should behave differently depending on the room. A theater scene, kitchen scene, and outdoor scene should not all follow the same logic.

3

Identify Included Systems

Confirm whether the scene controls lighting, shades, audio, video, climate, security, access control, outdoor areas, or a combination.

4

Name Scenes Clearly

Use names that make sense to the people using the system. Simple labels like Movie, Entertain, Away, and Goodnight are easier to remember.

Scene Discovery Questions

Ask these before building the scene list.

These questions help define routines, triggers, room behavior, scene names, included systems, and user expectations.

What are the most common daily routines in the home?
What should happen when the customer comes home?
What should happen when the customer leaves?
What does movie night need to do?
What should entertaining feel like inside and outside?
Do any scenes need to control shades?
Should music or video be included in any scenes?
Should security, locks, or cameras respond to scene changes?
Should any scenes run on a schedule, keypad button, touchscreen, app, sensor, or voice command?
Who needs to understand and use the scene names?

Trigger Methods

Decide how each scene should start.

Scenes can be triggered from keypads, remotes, touchscreens, apps, schedules, sensors, voice commands, or security events. Choose the trigger that makes sense for the room and routine.

Scene Behavior

Define what happens next.

A scene should have a clear result, but also a clear exit path. Confirm what happens when the customer changes activities, turns the scene off, or moves to another room.

Scene Checklist

Document every scene before handoff.

Keep the final scene list understandable for the client, the programmer, and anyone supporting the system later.

Scene name
Rooms included
Lighting levels
Shade position
Audio source and volume
Video source or display behavior
Climate adjustment
Security or access behavior
Trigger method
User permissions

Common Mistakes

Avoid scenes that make systems feel confusing.

Scenes should simplify the home. Too many overlapping scenes, technical names, unclear exit behavior, or untested routines can make automation harder to use.

Creating too many scenes that overlap and confuse the customer.
Using technical scene names instead of simple everyday language.
Forgetting to define what happens when a scene turns off.
Programming scenes before confirming real room behavior.
Including too many systems in a scene when the customer only needs a simple action.
Not testing scenes with the people who will actually use them.

Related Resources

Continue planning the automation system.

Use these related guides to continue planning lighting and shade behavior, automation discovery, control systems, and smart home prewire.

When to Call DSG Metro

Bring us in before scenes become confusing.

DSG Metro can help think through scene naming, lighting behavior, shade positions, audio/video behavior, security modes, trigger methods, and how the control system should feel in daily use.