KNX Scene Programming in ETS6: Lighting, Blinds and HVAC Scene Configuration
Configuring scenes across multiple actuator types in ETS6 requires systematic parameter setup, correct group address linking and efficient copy-paste workflows to keep large projects manageable. This guide covers every actuator type from dimmer to HVAC thermostat with real-world parameter paths and a complete meeting-room scene example.
Scene programming workflow overview
ETS6 scene programming follows a consistent sequence regardless of actuator type. The workflow below applies to every device — complete each step before moving to the next actuator to avoid GA assignment errors and missed parameters.
ETS6 scene programming sequence
Step 1: Enable scene on actuator channel Device > Parameters > Channel X > Scene enable = Yes Step 2: Assign scene GA to channel Group Objects > Channel X "Scene" > link to scene GA Example: 1/5/0 (Zone A scenes) Step 3: Set scene numbers and preset values Parameters > Channel X > Scene 1 = [preset value] Parameters > Channel X > Scene 2 = [preset value] (repeat for all required scene numbers) Step 4: Configure learn mode Parameters > Channel X > Scene learn mode = Disabled (or Enabled if end-user adjustment is required) Step 5: Download to device ETS6 > Download > Full download (first time) ETS6 > Download > Partial download (subsequent changes) Step 6: Verify in Group Monitor Group Monitor > send DPT 18.001 Scene 1 recall Observe actuator responds with correct preset value Verify all participating actuators simultaneously
MDT AKD-0424V dimmer actuator scene configuration
The MDT AKD-0424V is a 4-channel 0–10V/DALI/universal dimmer actuator commonly used in commercial KNX installations. Scene configuration is per channel and supports up to 64 scenes per channel.
MDT AKD-0424V ETS6 parameter path
Device: MDT AKD-0424V (4-ch dimmer)
ETS6 path: Parameters > Channel 1 > Scene
Scene enable: Yes
Scene 1 name: Presence/Work
Scene 1 dim level: 100%
Scene 2 name: Presentation
Scene 2 dim level: 80%
Scene 3 name: Video
Scene 3 dim level: 20%
Scene 0 name: Off
Scene 0 dim level: 0%
Scene learn mode: Disabled
Scene dimming speed: Immediate (0s fade)
or 2.0s for smooth transition
Group object: Channel 1 "Scene" → GA 1/5/0
After download:
GA 1/5/0 Scene 2 recall → channel dims to 80%
GA 1/5/0 Scene 0 recall → channel dims to 0%The scene dim level is a percentage (0–100%) independent of any soft-start or minimum dim level configured on the channel. If the channel has a minimum dim level of 10%, a scene preset of 0% (Off) will switch the channel off completely — the minimum dim level applies to manual control only, not scene recall.
ABB switch actuator scene configuration
Switch actuator scenes store a binary on/off value per scene per channel. Each channel in a multi-channel switch actuator stores its own scene states independently — a 8-channel actuator can have completely different scene presets on each channel.
ABB 2CDG110069R0011 8-channel switch actuator
Device: ABB SA/S8.16.6.1 (8-ch switch actuator) ETS6 path: Parameters > Channel 1 > Scene Scene enable: Yes Scene 1 value: On (receptacle circuit: energised) Scene 2 value: On (receptacle circuit: energised) Scene 3 value: Off (receptacle circuit: off during video) Scene 0 value: Off (receptacle circuit: off at end of day) Channel 2 (different load): Scene 1 value: On Scene 2 value: Off Scene 3 value: Off Scene 0 value: Off Both channels → same scene GA: 1/5/0 Each channel stores its own on/off preset. Single scene recall telegram controls all 8 channels.
Blind actuator scene programming
Blind actuator scenes store two values per scene: blind position (0–100% where 0% = fully open, 100% = fully closed) and slat angle (0–100%). Both values are recalled simultaneously by a single scene telegram, allowing precise scene-specific shading control.
MDT AKM-0800.01 8-channel blind actuator
Device: MDT AKM-0800.01 (8-ch blind actuator) ETS6 path: Parameters > Channel 1 > Scene Scene enable: Yes Scene 1 position: 0% (fully open — work light) Scene 1 slat: 0% (slats horizontal) Scene 2 position: 70% (partial close — presentation) Scene 2 slat: 50% (slats angled, reduce glare) Scene 3 position: 100% (fully closed — video) Scene 3 slat: 100% (slats vertical, blackout) Scene 0 position: 30% (end of day — neutral position) Scene 0 slat: 50% Blind actuator scene notes: Position 0% = motor fully retracted (open, maximum daylight) Position 100% = motor fully extended (closed, blackout) Slat 0% = horizontal (flat, maximum light passage) Slat 100% = vertical (closed, minimum light passage) Both position and slat stored separately per scene. Scene recall moves blind to position first, then adjusts slat.
Sun protection override:if the blind actuator has a sun protection input active (wind or rain sensor), scene recall may be blocked or overridden depending on actuator parameter settings. Check "Scene enable during sun protection = Yes/No" in MDT blind actuator parameters if scene recall appears to have no effect during sun protection periods.
HVAC scene integration
HVAC thermostats and heating actuators can participate in the same scene GA as lighting and blinds, allowing a single scene recall to simultaneously set comfort setpoints, economy setpoints and operating modes across all systems.
MDT heating actuator SCN-HCA.02 scene config
Device: MDT SCN-HCA.02 (heating actuator with KNX thermostat) ETS6 path: Parameters > Thermostat > Scene Scene enable: Yes Scene 1 setpoint: 21.0°C (Presence/Work — comfort) Scene 1 HVAC mode: Comfort Scene 2 setpoint: 21.0°C (Presentation) Scene 2 HVAC mode: Comfort Scene 3 setpoint: 21.0°C (Video — maintain comfort) Scene 3 HVAC mode: Comfort Scene 0 setpoint: 18.0°C (Off — economy/standby) Scene 0 HVAC mode: Economy Combined scene GA 1/5/0: → Dimmer: dim level per scene → Blind: position + slat per scene → Thermostat: setpoint + HVAC mode per scene One button press sets lighting, shading AND temperature.
Note that HVAC setpoints in scene presets define the target setpoint — the heating or cooling actuator then runs its normal control loop to reach that setpoint. Scene recall for HVAC is an instantaneous command; actual room temperature change is gradual. Design scene presets considering the thermal mass of the space.
Multi-scene push-button floor example
A 4-button Niko One in a meeting room with full scene configuration demonstrates how all actuator types are coordinated via a single scene GA.
Meeting room scene assignment — Niko One 4-button
Scene 2 — Presentation
Scene 3 — Collaboration
Scene 4 — Video
Scene 0 — Off
All four Niko One buttons send DPT 18.001 recall telegrams to GA 1/5/1 (Zone B meeting room scenes). Dimmer channel, blind channel and HVAC thermostat all linked to GA 1/5/1. A single ETS6 download programs presets into all three actuator types simultaneously.
ETS6 copy-paste-properties for large buildings
In a building with 60 dimmer channels and 4 scenes each, configuring channels one by one would take hours. ETS6 copy-paste-properties transfers the complete parameter set (including all scene configurations) from one channel to another in seconds.
Copy-paste-properties workflow
Step 1: Configure Channel 1 completely - All scene presets (scenes 0, 1, 2, 3) - Dimming speed, minimum level, scene learn mode - Link Channel 1 scene object to GA 1/5/0 Step 2: Right-click Channel 1 → Copy Properties Step 3: Select channels 2–60 (Shift+click for range) Right-click selection → Paste Properties ETS6 copies all parameter values to all selected channels Step 4: Adjust only per-room GAs Channel 2 scene object → GA 1/5/1 (Zone B) Channel 3 scene object → GA 1/5/1 (Zone B) Channel 4 scene object → GA 1/5/2 (Zone C) (Scene preset values remain identical; only GA changes) Step 5: Download all devices Select all changed devices → Download (partial) Result: 60 channels programmed with correct scenes. Time saved vs. manual: approximately 95%.
Paste Properties limitation: Paste Properties copies parameter values only — it does not copy group address links. Group address links (GA assignments to communication objects) must still be set per channel after pasting parameters. Use ETS6 group address view sorted by main/middle group to quickly link all scene objects for a zone to the correct zone GA.
Scene conflict resolution with presence detectors
Presence detector control and scene recall frequently conflict in commercial spaces. When a user activates a scene, the presence detector may immediately send a full-on override dim command, cancelling the scene preset. Scene priority flags and hold periods prevent this.
Priority and hold period configuration
Actuator parameter: Scene priority = High
Actuator parameter: Scene hold period = 30 seconds
Effect on conflict:
T=0s User presses Presentation → Scene 2 recall → 80%
T=2s Presence detector dim command → 100%
→ Blocked by scene hold (30s active)
T=30s Hold period expires
→ Presence detector resumes direct control
→ Dim to 100% (presence on)
For residential:
Scene hold period = 0 seconds (no hold)
Direct control always takes priority over scene
User expects to dim manually after scene recallVisualisation integration
Scene recall can be triggered from any KNX-connected visualisation system by sending a DPT 18.001 telegram to the scene GA. The integration method depends on the visualisation platform used.
Gira X1 homeserver
HTML5 panel scene buttons: add a "Scene" widget, select scene GA, set scene number. Gira X1 sends DPT 18.001 recall telegram on button press. Scene buttons appear in the Gira Smart Home app for iOS/Android remote control.
IP-Symcon virtual scene buttons
IP-Symcon KNX module: create a KNX data point with DPT 18.001, link to scene GA. PHP script: KNX_SetValue($id, 0x01); sends Scene 2 recall. Virtual buttons in WebFront trigger the script on click. Full scene scheduling possible via IP-Symcon event module.
ARISTO BewO script
BewO action script syntax: BUTTON 1 PRESSED = SET GA("1/5/0") = 1 sends the DPT 18.001 recall telegram for scene 1 to GA 1/5/0 from a touchscreen button action. Supports conditional scene recall based on time or occupancy variables.
Testing and handover
Scene testing at handover requires a systematic pass/fail matrix covering every scene in every zone. Random spot-checking is insufficient — a missing scene link on one actuator out of 60 will not be found without complete testing.
Scene test matrix format
Zone | Scene 0 | Scene 1 | Scene 2 | Scene 3 -----------|---------|---------|---------|-------- Zone A | PASS | PASS | PASS | PASS Zone B | PASS | PASS | FAIL | PASS ← investigate Zone C | PASS | PASS | PASS | PASS Bldg-wide | PASS | PASS | PASS | PASS FAIL: Zone B Scene 2 — blind actuator ch3 not responding. → Check: GA link missing on blind ch3 scene object. → Fix: link ch3 scene object to 1/5/1 → re-download. → Retest: Zone B Scene 2 → PASS.
For end-client training, demonstrate scene learn mode (long press) only if enabled in parameters. Show the client that a long press stores current dim levels as the new preset. Document which scenes have learn mode enabled in the handover manual — users should not accidentally overwrite security or emergency scene presets.
Need complete KNX scene configuration for your project?
We program ETS6 scenes across dimmer, switch, blind and HVAC actuators — with full scene register documentation, visualisation integration and a complete zone-by-zone test matrix at handover.
Request a quote →