KNX: KNX Device Configuration and Commissioning

KNX devices are not plug-and-play. Unlike consumer smart home devices that auto-discover and configure themselves, KNX relies on a structured, deliberate commissioning process that gives installers full control over every aspect of device behavior. This precision is what makes KNX suitable for professional, large-scale building automation.

Configuration Tools

ETS — Engineering Tool Software

ETS is the official software for designing, configuring, and commissioning all KNX projects.

• Available in editions: ETS Lite (for small projects), ETS Professional (for commercial installations)
• Used to assign physical addresses, set parameters, and link group addresses
• Requires manufacturer-provided product databases (.knxprod files) for each device model
• Works with all KNX devices from all 500+ manufacturers — a single tool for the entire ecosystem

+-----------------------------+
|     ETS Software (PC)       |
+-----------------------------+
| Project design              |
| Physical address assignment |
| Parameter configuration     |
| Group address linking       |
| Download to devices         |
+-----------------------------+
         |
         | (via KNX bus or KNX/IP)
         v
+-----------------------------+
|     KNX Devices             |
|  (receives configuration)   |
+-----------------------------+

Manufacturer-Specific Tools

Some vendors provide additional apps or plugins that extend ETS with specialized functions — for example, advanced HVAC logic programming, LED dimming curve configuration, or energy metering setup. However, all standardized KNX configuration still happens inside ETS.

Steps in Configuring KNX Devices

The configuration workflow follows five steps, typically performed in order:

Step 1: Assign Physical Address (Individual Address)

Each device receives a unique ID in the format Area.Line.Device (e.g., 1.1.15).

• This address uniquely identifies the device on the bus
• Assigned by putting the device in programming mode (pressing the programming button) and downloading the address from ETS
• Without a physical address, the device cannot be individually targeted for configuration

Step 2: Load Application Program

The application program defines the device's functionality at a fundamental level.

• Example: A switch actuator's application program defines how many output channels it controls, what load types it supports, and which advanced features (timers, logic, scenes) are available
• Downloaded from ETS into the device's non-volatile memory
• Different device models from the same manufacturer may have different application programs

Step 3: Parameterization

Each device has a set of configurable parameters that fine-tune its behavior. These are set in ETS and downloaded to the device.

Examples:

• Dimmer actuator: minimum brightness level, fade-in time, dimming curve type (linear/logarithmic), maximum brightness
• Motion detector: sensitivity level, delay time before switching off, day/night brightness threshold
• HVAC controller: temperature setpoints, control algorithm (PI/PID), valve protection cycle interval

Parameterization is where the device's behavior is tailored to the specific installation requirements.

Step 4: Group Address Assignment

Group addresses are the logical links that connect input devices (switches, sensors) to output devices (lights, actuators).

[Push-Button]
  sends "ON/OFF" to group address 1/0/1
         |
         v
  [KNX Bus]
         |
         v
[Light Actuator]
  listens to group address 1/0/1
  turns on/off accordingly

A single device can be linked to multiple group addresses for different functions:

• A dimmer might listen to 1/0/1 for ON/OFF, 1/0/2 for dim level, and 1/0/3 for scene recall

Step 5: Download to Device

Once the configuration is complete in ETS, it is physically downloaded to the device over the KNX bus (or via KNX/IP for remote commissioning).

After download, the device:

• Stores its configuration in non-volatile memory
• Begins operating according to its programmed parameters and group address assignments
• Is ready for functional testing

Configuration Modes in KNX

KNX defines three standardized configuration modes for different use cases and installer skill levels:

S-Mode (System Mode)

The most common mode, used with ETS.

• Full flexibility: installers configure every parameter, group address, and application program
• Used in: residential and commercial projects of all sizes
• Requires trained KNX installers and ETS software
• Maximum control over device behavior

E-Mode (Easy Mode)

For simpler installations:

• Devices configure themselves or via push-button pairing — point one device at another and press a button to link them
• Limited flexibility compared to S-Mode
• Quicker setup for small, straightforward projects
• Does not require ETS software for basic configuration

A-Mode (Automatic Mode)

Devices auto-configure with minimal user input:

• Designed for plug-and-play or consumer-grade KNX solutions
• Minimal configuration required from the installer
• Used in simple residential applications where full professional commissioning is not justified

A-Mode     E-Mode     S-Mode
--------   --------   --------
Plug &     Push-btn   Full ETS
Play       pairing    control
Simple     Limited    Maximum
consumer   commercial professional

Most professional projects use S-Mode because of its scalability, precision, and the ability to document and reproduce the configuration.

Diagnostics and Maintenance

ETS Diagnostic Tools

ETS includes built-in diagnostic tools for troubleshooting installations:

• Bus monitor — captures and displays all telegrams on the bus in real time
• Helps identify whether devices are communicating correctly
• Reveals duplicate group addresses, missing responses, or unexpected commands
• Device status checks — read back device parameters to verify configuration
• Communication error logging — logs checksum failures and bus collisions

Device Replacement

When a device fails and needs replacing:

1. Export the device configuration from the existing ETS project
2. Install the replacement device
3. Assign the physical address
4. Download the same application program and parameters

ETS stores all configuration in the project file, making device replacement systematic rather than requiring complete reconfiguration from scratch.

Firmware Updates

Some modern KNX devices support firmware upgrades via ETS or manufacturer applications:

• Delivered over the KNX bus or via KNX/IP
• Adds new features or fixes bugs without replacing hardware
• Keeps installations current with evolving standards

Future Trends: Remote and Secure Configuration

KNX Secure for Configuration

KNX Secure extends beyond runtime security to protect the configuration process itself:

• Device configuration is encrypted and authenticated
• Protects against unauthorized reprogramming — an attacker cannot send false configuration data to devices
• Ensures only authorized ETS installations can modify device parameters

Cloud and Remote Commissioning

Emerging tools and workflows are enabling:

• Pre-configuration of projects remotely before visiting the site
• Final on-site commissioning reduced to downloading pre-prepared settings
• Significant reduction in commissioning time for large commercial buildings
• Remote diagnostics and maintenance via secure IP connections

Traditional Commissioning:
[Installer on-site] --> [ETS] --> [KNX Devices]

Future Commissioning:
[Remote pre-config] --> [Cloud project] --> [On-site final download]
                                                     |
                                              [KNX Devices]

Summary

KNX device configuration is a systematic, five-step process:

The ETS software is the central tool for all professional KNX commissioning, supporting the full workflow from project design to device download to diagnostic monitoring. Mastering ETS is the practical foundation for KNX installation work.