KNX Scenes Explained: Scene Control, Scene Numbers & ETS Design

By /

A KNX scene allows multiple building functions to be changed together using a single command. Instead of controlling each light, blind, HVAC function or other device individually, a scene can place several devices into predefined states.

For example, a Meeting Scene could set presentation lights to 30%, close selected blinds, adjust room temperature and prepare an AV system. A Welcome Scene in a residence could turn on selected lights, open curtains and establish a comfortable lighting level.

KNX scenes are therefore more than simply “multiple ON/OFF commands.” A well-designed scene architecture defines which devices participate, what values they store, how scenes are recalled, and how the scene structure is maintained in ETS.

1. What Is a KNX Scene?

A KNX scene is a predefined combination of values for multiple KNX functions that can be recalled using a scene command.

Instead of sending separate commands:

Light 1 → ON
Light 2 → 50%
Blind 1 → 80%
Blind 2 → 80%
HVAC → Comfort

one scene command can trigger the required devices to move to their programmed scene states.

Example: Meeting Scene

                MEETING SCENE
                     │
                     ▼
              Scene Command
                     │
       ┌─────────────┼─────────────┐
       ▼             ▼             ▼
   Lighting        Blinds         HVAC
     50%             80%          Comfort

The user therefore operates one logical function rather than several individual controls.

Scene vs normal control

Normal control:

Button → Light ON

Scene control:

Scene 3
   │
   ├── Light 1 → 50%
   ├── Light 2 → 30%
   ├── Light 3 → OFF
   ├── Blind 1 → 80%
   └── HVAC → Comfort

This makes scenes particularly useful where a room needs several systems to assume a coordinated state.

Typical KNX scene applications

Scenes are commonly useful for:

  • Residential lighting
  • Conference rooms
  • Boardrooms
  • Hotel rooms
  • Restaurants
  • Auditoriums
  • Classrooms
  • Presentation spaces
  • Home theatres
  • Central building modes

2. How KNX Scene Control Works

KNX scene control is based on a scene number transmitted to participating devices.

A scene command can therefore be thought of as:

Scene Group Address
        │
        ▼
   Scene Number
        │
        ▼
Participating KNX devices
        │
   ┌────┼────┬────┐
   ▼    ▼    ▼    ▼
 Light Blind HVAC Curtain

The important distinction is that the scene command does not necessarily contain all the individual values for every device.

Instead, the participating device can have a stored scene configuration telling it what value to apply when a particular scene number is received.

Example

Suppose Scene 3 is defined as:

FunctionScene 3 value
Ceiling Light40%
Wall Light20%
Decorative LightOFF
Blind70%
HVAC ModeComfort

The scene command identifies Scene 3.

The participating devices then apply their corresponding scene values.

Basic architecture

                Scene Controller
                       │
                       │ Scene 3
                       ▼
                Scene Group Address
                       │
          ┌────────────┼────────────┐
          ▼            ▼            ▼
      Light Actuator  Blind       HVAC
          │            │            │
       Scene 3       Scene 3      Scene 3
          │            │            │
          ▼            ▼            ▼
          40%          70%        Comfort

Scene recall vs scene storage

There are two different operations that should not be confused:

Recall

Apply the stored values for this scene.

Store

Save the current values as the values for this scene.

This distinction becomes important when users are allowed to customise scenes.

3. KNX Scene Numbers and DPT 17

KNX standardised scene control uses a dedicated scene-number data point type, commonly known as DPT 17.001 – Scene Number.

The scene command therefore carries a scene identifier rather than a lighting percentage, temperature or switching value.

Conceptually:

Scene Group Address
        │
        ▼
     DPT 17.001
        │
        ▼
   Scene Number

Example scene numbering

A project could define:

SceneNumberName
Scene 11Normal
Scene 22Presentation
Scene 33Meeting
Scene 44Video
Scene 55Cleaning
Scene 66Shutdown

The actual scene numbering should be defined as part of the project standard.

Important planning point

Do not create scene numbers randomly while programming individual devices.

Instead create a project-wide scene schedule.

For example:

Scene 01 = Normal
Scene 02 = Presentation
Scene 03 = Meeting
Scene 04 = Video Conference
Scene 05 = Cleaning
Scene 06 = Shutdown

Then use the same numbering convention throughout the project where practical.

Scene Group Address

A typical ETS structure might be:

4 Scenes
   │
   ├── GF Living
   │      └── Scene Recall
   │
   ├── Meeting Room 01
   │      └── Scene Recall
   │
   └── Conference Room 02
          └── Scene Recall

For large projects, scenes can be organised according to the building’s functional structure.

Scene number is not a Group Address

This is an important distinction:

Group Address = communication destination

Scene Number = value sent through that Group Address

For example:

Group Address:
4/1/10

DPT:
17.001

Value:
Scene 3

The Group Address identifies the communication channel; DPT 17.001 defines the scene-number value carried by that communication.

4. KNX Scene Control in ETS

Scene implementation in ETS depends partly on the manufacturer’s application program.

A KNX actuator, push button, room controller or other device may provide scene-related Group Objects and parameters. The available functionality can therefore differ significantly between manufacturers and device families.

A typical workflow is:

1. Enable Scene Function
          ↓
2. Configure Scene Number
          ↓
3. Define Scene Values
          ↓
4. Link Scene Group Address
          ↓
5. Download Application
          ↓
6. Test Scene

Typical actuator configuration

A lighting actuator may provide a scene parameter section such as:

Scene Control
│
├── Scene 1 → 100%
├── Scene 2 → 50%
├── Scene 3 → 30%
├── Scene 4 → OFF
└── Scene 5 → OFF

The exact interface varies by manufacturer.

Scene Group Object

The device may expose an object such as:

Scene
DPT 17.001

This object is then linked to the appropriate Scene Group Address.

Example:

4/1/10
Meeting Room Scene
       │
       ├── Wall Panel
       ├── Lighting Actuator
       ├── Blind Actuator
       └── Room Controller

Multiple devices on one scene address

Several devices can listen to the same scene Group Address when they are intended to participate.

Scene 3
   │
   ▼
4/1/10
   │
   ├── Lighting Actuator
   ├── Blind Actuator
   ├── HVAC Controller
   └── Curtain Controller

Each device interprets the scene number according to its configured scene parameters.

Scene parameters vs Group Addresses

A common misunderstanding is that the Group Address itself contains the values for every device.

In many KNX scene implementations:

Scene Group Address
       │
       ▼
Scene Number
       │
       ▼
Device's stored scene configuration
       │
       ▼
Device applies its own values

This is why scene commissioning requires both Group Address configuration and device application parameter configuration.

5. KNX Lighting Scenes

Lighting is one of the most common applications for KNX scenes.

A professional lighting scene may contain several circuits with different brightness levels.

Example: Conference room

Consider:

  • Ceiling lights
  • Perimeter lights
  • Presentation lights
  • Decorative lights

The scenes could be:

SceneCeilingPerimeterPresentationDecorative
Normal80%70%OFF30%
Meeting60%50%OFF20%
Presentation20%10%100%OFF
Video10%OFF30%OFF
Cleaning100%100%100%100%

One scene command can therefore establish the required room state.

Scene architecture

                    SCENE 3
                 PRESENTATION
                       │
                       ▼
                 Scene Group
                  Address
                       │
        ┌──────────────┼──────────────┐
        ▼              ▼              ▼
   Ceiling Light   Presentation    Decorative
       20%             100%            OFF

Dimming scenes

For dimmable systems, the scene can store brightness values rather than simply ON/OFF.

For example:

Scene 1 → 100%
Scene 2 → 70%
Scene 3 → 30%
Scene 4 → 10%

This is particularly useful with:

  • KNX dimming actuators
  • DALI gateways
  • Constant-light systems
  • Architectural lighting
  • Conference rooms
  • Hospitality projects

DALI integration

In a KNX-DALI installation, the KNX scene command may control the overall scene logic while the DALI gateway manages the relevant DALI groups or ballasts.

The exact implementation depends on the gateway’s application program.

For example:

KNX Scene 3
     │
     ▼
KNX-DALI Gateway
     │
     ├── DALI Group 1 → 30%
     ├── DALI Group 2 → 60%
     └── DALI Group 3 → OFF

This makes scene design especially important when KNX is used as the supervisory control layer for a larger lighting system.

6. Scenes for Blinds, HVAC and Other Functions

Scenes do not have to be limited to lighting.

A well-designed building automation system can use scenes to coordinate multiple subsystems.

Blind scene

For example:

Presentation Scene

Blinds
   │
   ├── Position → 80%
   └── Slats → 20%

The goal may be to reduce glare while maintaining natural daylight.

HVAC scene

A room mode can also include HVAC-related settings.

For example:

Meeting Mode
   │
   ├── HVAC → Comfort
   ├── Temperature Setpoint → 22°C
   └── Fan → Auto

The exact implementation depends on the HVAC controller and its available scene objects.

Curtain scene

In a conference room:

Presentation
   │
   ├── Blackout Curtain → CLOSED
   ├── Window Blind → 80%
   └── Lighting → 20%

AV integration

KNX can also be integrated with AV control.

For example:

VIDEO CONFERENCE
       │
       ├── Lighting → 30%
       ├── Blinds → 70%
       ├── Curtains → CLOSED
       ├── HVAC → Comfort
       └── AV System → Meeting Mode

The AV action may be implemented through an integration or control system rather than directly through a KNX scene object.

The important engineering principle is to clearly define which system owns each function.

Avoid duplicated control ownership

For example:

KNX Scene
    │
    └──► AV Controller
             │
             └──► Lighting

KNX Lighting Scene
    │
    └──► Lighting Actuator

If both systems independently control the same lighting output, unexpected interactions can occur.

For integrated projects, document the control authority for each function.

7. Saving and Modifying KNX Scenes

There are two broad approaches to scenes:

Fixed scenes

The integrator defines the scene values during commissioning.

Example:

Scene 3 = Presentation

Light 1 = 20%
Light 2 = 10%
Blind = 80%
Curtain = Closed

Users simply recall the scene.

This is common in:

  • Offices
  • Meeting rooms
  • Hotels
  • Commercial buildings

User-adjustable scenes

Some devices support a “learn” or “save” mechanism that allows the current state to be stored as a scene.

For example:

User adjusts room
       │
       ├── Light = 65%
       ├── Blind = 70%
       └── Curtain = Closed
              │
              ▼
          SAVE SCENE
              │
              ▼
       Scene 3 updated

The next time Scene 3 is recalled, the stored values can be applied.

Why scene saving needs careful design

User-adjustable scenes introduce additional engineering considerations:

  • Who is allowed to save scenes?
  • Which devices can save?
  • What happens after a power failure?
  • Are values stored permanently?
  • Can users overwrite the commissioning values?
  • How is the final configuration documented?

The answers depend on the specific KNX devices and application programs.

Scene save vs scene recall

Keep the two functions conceptually separate:

RECALL
Scene Number
     │
     ▼
Apply stored values


SAVE
Current device values
     │
     ▼
Store as scene

Not every KNX device supports both functions.

8. Common KNX Scene Problems and Troubleshooting

Scenes can fail partially even when the scene command itself is transmitted correctly.

A typical troubleshooting process should therefore examine the complete scene path.

Problem 1: Scene button sends telegram but nothing happens

Check:

  • Scene Group Address
  • DPT
  • Scene number
  • Receiving Group Objects
  • Device scene function enabled
  • Application parameters
  • Device programming

Use ETS Group Monitor to confirm the actual scene telegram.

For example:

Scene Group Address:
4/1/10

Telegram:
Value = Scene 3

If this is visible but devices do not respond, investigate the receiving devices.

Problem 2: Some devices respond, others do not

Example:

Scene 3
│
├── Ceiling Light ✓
├── Wall Light ✓
├── Blind ✗
└── HVAC ✗

The scene command itself may be correct.

Investigate:

  • Whether the blind/HVAC object is linked.
  • Whether scene functionality is enabled.
  • Whether Scene 3 is configured in those devices.
  • Whether the device supports the required scene function.

Problem 3: Wrong brightness

Suppose:

Expected: 30%
Actual:   80%

Check the scene configuration inside the actuator.

The Group Address may be completely correct while the stored scene value is wrong.

Problem 4: Correct scene number, wrong room

If Scene 3 in Room A and Scene 3 in Room B are intended to mean different things, avoid connecting them unintentionally to the same scene Group Address.

Scene numbering does not automatically define room ownership.

The Group Address architecture determines which devices receive the scene command.

Problem 5: Scene works from one button but not another

Compare:

Button A → Scene GA → Works
Button B → Scene GA → Doesn't work

Check:

  • Same Group Address?
  • Same DPT?
  • Same scene number?
  • Correct communication flags?
  • Correct device programming?

Problem 6: Scene causes unexpected feedback

A scene may change several outputs simultaneously.

If status feedback is correctly designed, many status telegrams may appear after one scene command.

For example:

Scene 3
   │
   ├── Light 1 changes → Status
   ├── Light 2 changes → Status
   ├── Blind changes → Status
   └── HVAC changes → Status

This is not necessarily a fault.

The Group Monitor should be used to distinguish expected scene-related traffic from unwanted telegrams.

9. KNX Scene Design and Commissioning Checklist

A professional scene implementation should be designed before programming individual devices.

Scene planning

  • Scene list defined.
  • Scene numbers allocated.
  • Scene names documented.
  • Participating devices identified.
  • Scene values defined.
  • Scene Group Addresses planned.
  • Scene ownership documented.

ETS configuration

  • Scene function enabled where required.
  • Scene Group Objects enabled.
  • Correct Group Address assigned.
  • DPT checked.
  • Scene number verified.
  • Device scene parameters configured.
  • Application program downloaded.

Functional testing

Test each scene from every intended control source.

For example:

Scene 1 → ✓
Scene 2 → ✓
Scene 3 → ✓
Scene 4 → ✓

Then verify every participating function:

Lighting       ✓
Dimming        ✓
Blinds         ✓
Curtains       ✓
HVAC           ✓
AV Integration ✓
Status         ✓

Test scene interaction

Do not only test:

OFF → Scene

Also test:

Scene 1 → Scene 2
Scene 2 → Scene 3
Manual → Scene
Scene → Manual
Central OFF → Scene
Power Restart → Scene

This can expose unexpected interactions.

Handover documentation

Document:

ItemExample
Scene Number3
Scene NamePresentation
Group Address4/1/10
Lighting20%
Blinds80%
CurtainsClosed
HVACComfort
AVPresentation Mode

For large projects, maintain the scene schedule alongside the Group Address list.

Practical Conference Room Scene Example

A conference room is an excellent example of how KNX scenes can coordinate multiple building functions.

Scene 1 – Normal Meeting

Lighting      → 70%
Blinds        → 60%
Curtains      → Open
HVAC          → Comfort
AV            → Normal

Scene 2 – Presentation

Lighting      → 20%
Presentation  → 100%
Blinds        → 80%
Curtains      → Closed
AV            → Presentation

Scene 3 – Video Conference

Lighting      → 30%
Front Light   → 15%
Blinds        → 60%
Curtains      → Closed
HVAC          → Comfort
AV            → Video Conference

Scene 4 – Shutdown

Lighting      → OFF
Blinds        → UP
Curtains      → Open
HVAC          → Economy
AV            → OFF

The KNX scene architecture can coordinate the building-control functions, while specialist AV or HVAC controllers can remain responsible for their own subsystem functions.

KNX Scene Architecture

A scalable project can use the following structure:

                         SCENE CONTROL
                              │
                              ▼
                      Scene Group Address
                              │
                     ┌────────┼────────┐
                     │        │        │
                     ▼        ▼        ▼
                  Lighting  Blinds    HVAC
                     │        │        │
                     ▼        ▼        ▼
                  Scene     Scene     Scene
                  Values    Values    Values
                     │        │        │
                     └────────┼────────┘
                              ▼
                       Actual Building
                           State
                              │
                              ▼
                         Status Feedback

This connects naturally with the previous KNXHUB articles on Group Address Design, Communication Flags and Status Feedback.

Conclusion

KNX scenes provide a structured way to coordinate multiple building functions from a single logical command.

The key concepts are:

  1. A scene number identifies the requested scene.
  2. A Scene Group Address carries the scene command.
  3. Participating devices interpret that scene number according to their configured scene parameters.
  4. Scene values can include switching, dimming, positions and other supported functions.
  5. Scene recall and scene saving are different operations.
  6. Scene design should be planned before detailed ETS programming.
  7. Each scene should be tested at the device and system level.

The most important engineering principle is:

Do not treat a scene as simply another button command.

A professional scene is a coordinated building state with clearly defined participants, values, Group Addresses and ownership.

For larger KNX projects, maintaining a dedicated Scene Schedule alongside the Group Address list can significantly simplify commissioning, troubleshooting and future modifications.

Related Posts

Scroll to Top