Scene programming is one of the most powerful features of KNX — a single telegram activates multiple actuators simultaneously, creating preset states for lighting, blinds, HVAC, and audio. But poorly designed scene structures create commissioning nightmares: conflicts between group addresses, scene recall overriding manual control, learn-mode accidents overwriting tuned scenes. This guide covers DPT 18.001 architecture, actuator-stored vs. controller-stored scenes, conflict prevention, and ETS6 best practices for large buildings.

DPT 18.001 scene recall architecture

KNX scenes use DPT 18.001 (8-bit): bits 7–0 encode the scene number (0–63), bit 7 = 0 for recall, bit 7 = 1 for store/learn. Scene recall telegram: value 0x01 (= decimal 1) recalls scene 1. Store telegram: value 0x81 (= decimal 129) stores current state into scene 1. The scene recall telegram is sent by a scene controller (push-button, time module, or visualisation) to a group address (GA) linked to one or more actuators. Each actuator channel that participates in the scene stores the scene state in its own non-volatile memory (EEPROM). The scene GA is a common address — all actuators listening to the same scene GA recall their individually stored state simultaneously. This is the key architecture: each actuator stores its own state, the controller just sends the trigger.

Scene controller vs. actuator-stored scenes

Two scene mechanisms in KNX: (1) Actuator-stored scenes (standard, DPT 18.001): push-button or visualisation sends DPT 18.001 value to GA → actuator recalls its stored state. This is the standard method. Actuator must have scene capability and scene GA must be configured. (2) ETS6 scene function block / KNX logic module scenes: a dedicated scene block (MDT Logic Module, Loxone, or Gira X1) stores all scene values in server RAM/flash and sends individual DPT telegrams to each actuator GA when scene is recalled. This is suitable when actuators don't support DPT 18.001, or when scenes need to be dynamically reconfigurable via a UI. Recommendation: for lighting scenes, prefer actuator-stored (DPT 18.001) for reliability (no server required). For complex scenes involving non-scene-capable actuators (e.g., basic binary outputs), use logic module scenes.

Scene number assignment convention

ETS6 scene numbers (0–63 per actuator, per channel). Best practice convention for a commercial building: Scenes 0–7 = standard daily scenes (Scene 0 = Off, Scene 1 = Presence/Work, Scene 2 = Presentation, Scene 3 = Meeting, Scene 4 = Cleaning, Scene 5 = Night security, Scene 6 = Morning pre-set, Scene 7 = Emergency). Scenes 8–15 = custom per-zone scenes. Scenes 16–23 = building-wide scenes triggered by BMS. Scene 0 = Off is important — do not use 0 for on. Maintain a scene register spreadsheet: scene number, name, participating actuators and their set values, GA used for recall. This becomes the commissioning reference for handover.

Group address structure for scenes

Do not use one GA for all scenes — this prevents parallel operation. Recommended GA structure: 1/5/0 = Zone A Scenes (push-button in Zone A sends scene number), 1/5/1 = Zone B Scenes, 1/5/2 = Building Scene (all zones). Actuators in Zone A: channel linked to GA 1/5/0. Actuators in Zone B: channel linked to GA 1/5/1. For building-wide scenes: actuators linked to BOTH 1/5/0 (zone) AND 1/5/2 (building). Scene numbers in building GA: use same scene numbers as zone GA — actuators respond to whichever trigger arrives first. Conflict prevention: if a presence detector dim command (DPT 5.001 to GA 1/1/0) arrives simultaneously with a scene recall (GA 1/5/0 scene 1 also sets GA 1/1/0 to 80%), both telegrams compete — last telegram wins. Prevent by using scene recall priority: set actuator scene priority = High — scene recall overrides direct dim/switch for 30 seconds.

ETS6 scene configuration step-by-step

MDT AKD-0424V.01 4-channel actuator, channel 1, scene configuration: (1) ETS6 Parameters > Channel 1 > Output type = Switching. (2) Parameters > Scene > Enable scenes = Yes. (3) Parameters > Scene 1 name = "Presentation". (4) Parameters > Scene 1 value = On (1). (5) Group addresses > Channel 1 > Scene (DPT 18.001) = GA 1/5/0. (6) Download to actuator. (7) Set initial scene value: from ETS6 Group Monitor, send DPT 18.001 store command (value 129 = store into scene 1) AFTER setting the channel to the desired state (e.g., On). Actuator stores current state (On) as scene 1. Alternative: use ETS6 > Channel 1 > Scene tab > Set scene 1 preset = 1 (On) and download — scene value stored during ETS6 download without needing Group Monitor. Prefer download-preset method to avoid commissioning mistakes.

Learn-mode protection and conflict avoidance

Learn mode (DPT 18.001 bit 7 = 1): accidentally sending a learn telegram overwrites the stored scene with current actuator state. Protection: (1) Disable learn mode in actuator ETS6 parameters: Parameters > Scene > Allow learn = No. This prevents users from accidentally overwriting tuned scenes via push-button long press. (2) If learn must be enabled (client requirement): restrict to commissioning staff via keyswitch (KNX binary input with key switch → links to scene learn GA only when key = active). (3) Never link scene learn GA to the same GA as scene recall — use separate GAs: GA 1/5/0 = recall, GA 1/5/64 = learn (not standard, requires logic module to set bit 7). In ETS6 group monitor: use DPT filter to show only DPT 18.001 telegrams — easier to spot accidental learn transmissions during commissioning.

Large building example: 20-floor office

Each floor has 3 zones (perimeter, core, meeting rooms) × 20 actuator channels per zone = 60 actuator channels per floor. Scenes needed: 8 standard scenes × 60 channels = 480 scene-value records. GA structure: 3-level format: 1/floor/scene_offset. Floor 1, Zone A scenes: GA 1/1/0. Floor 1 Zone B: GA 1/1/1. Floor 1 Meeting: GA 1/1/2. Floor 1 Building (all zones): GA 1/1/10. 20 floors × 4 scene GAs = 80 scene GAs. Actuator channel template in ETS6: create 1 template actuator with all scenes configured → copy to all 60 channels per floor → global scene values identical, vary only per-channel state. ETS6 copy-paste-properties: right-click template device > Copy > select all 60 target devices > right-click > Paste Properties — saves 95% of scene configuration time on large projects. Verify: scene test walk-through — activate each scene GA, visually verify all channels in zone respond correctly.