KNX Commissioning Process from Design to Handover
Follow a practical KNX commissioning process from pre-site preparation through ETS programming, room tests, integration, snagging, and final handover.
KNX commissioning is not the day an engineer arrives with ETS and starts pressing programming buttons. It begins when the function list is stable enough to turn into addresses, parameters, and test cases.
The fastest commissioning teams do more work before site access. They prepare the topology, import the exact product applications, create naming rules, identify repeated rooms, and agree how each function will be proven. Site time is then used to verify the building rather than invent the design.
The commissioning stages
| Stage | Main activity | Exit evidence |
|---|---|---|
| 1. Design freeze | Approve functions, devices, loads, topology, and interfaces | Signed schedules and current drawings |
| 2. ETS preparation | Build topology, buildings, addresses, parameters, and templates | Reviewed ETS project version |
| 3. Electrical pre-check | Verify bus polarity, mains circuits, labels, and insulation boundaries | Pre-commissioning checklist |
| 4. Device commissioning | Assign individual addresses and download applications | ETS download status and device list |
| 5. Functional testing | Test each room, circuit, scene, sensor, and fail state | Completed test sheets |
| 6. Integration | Map and witness BMS, DALI, PMS, Modbus, or other points | Signed point-to-point record |
| 7. Acceptance | Close snags and demonstrate agreed scenarios | Witness-test certificate |
| 8. Handover | Deliver as-builts, ETS backup, credentials, and training | Owner receipt and controlled archive |
Skipping an exit document usually moves uncertainty into the next stage. It does not save time.
1. Freeze what is being commissioned
At minimum, the team needs:
- current electrical circuit schedule;
- room function descriptions;
- keypad and sensor locations;
- actuator channel assignment;
- topology and power-supply calculation;
- group-address naming standard;
- lighting scene table;
- HVAC sequence and setpoint limits;
- third-party point lists;
- failure and recovery behaviour;
- acceptance test format.
Record the revision number inside the ETS project notes. If drawings change later, the issue log should identify whether wiring, parameters, visualization, labels, or tests are affected.
2. Prepare ETS before going to site
Create the building structure and topology so an engineer can find a device by either physical location or bus line. Use clear names such as L03-East-Office-Actuator-A, not Device 47.
Repeated rooms can be built from a reviewed template, but every copy needs unique individual addresses and the correct room group addresses. Templates reduce typing; they do not replace verification.
In ETS, a download can include separate elements:
- individual address;
- application program;
- group-address links and tables;
- parameters.
Understanding those parts helps avoid unnecessary full downloads and explains why a device can have the right physical address yet still run old parameters.
3. Complete the electrical pre-check
Do not use ETS to diagnose unfinished electrical work. Before connecting the commissioning interface, check:
| Check | Method |
|---|---|
| Bus polarity and continuity | Inspect terminals and measure at representative points |
| Bus voltage and current | Record at supply and remote branches |
| Mains separation | Confirm bus cable is routed and terminated correctly |
| Load circuits | Test locally from actuator or approved temporary method |
| Labels | Match device, channel, terminal, circuit, and drawing |
| IP network | Confirm address, VLAN, firewall, and interface access |
| Secure certificates | Match FDSK/device certificate to installed location |
If actuator channel 5 operates the wrong lighting circuit manually, fix the wiring or schedule before programming a software workaround.
4. Address and download devices systematically
Work line by line and cabinet by cabinet. Apply a temporary “commissioned” marker only after the physical address and application have been verified. For devices above ceilings or behind finished panels, record the serial number and location before access is closed.
After downloads, use ETS device diagnostics to confirm reachability and application state. In a Secure project, verify the project password, certificates, and security status before the site becomes busy. Security recovery should not be designed during handover week.
5. Test functions from both ends
Every output should be tested from the local user interface and from any central or automatic source that controls it. For a lighting circuit, that might include keypad, presence sensor, scene, schedule, touch panel, and BMS command.
A useful room test sheet includes:
- command source;
- destination circuit or equipment;
- expected result;
- actual status feedback;
- timing or level tolerance;
- power-loss recovery state;
- pass/fail and issue number.
Test toggles after a scene or central command. A button that works twice in isolation may require two presses after another control source changes the load if status feedback is not designed correctly.
6. Use diagnostics with a question in mind
ETS provides Group Monitor, Bus Monitor, and device diagnostics. Start with the least intrusive tool that answers the question.
| Tool | Best use |
|---|---|
| Group Monitor | Read/write group values and inspect normal group telegrams |
| Bus Monitor | Capture full bus traffic for deeper analysis |
| Device Diagnostics | Check reachability, application state, and configured addresses |
| Line scan / programming-mode search | Find addressing and topology problems |
Save useful traces with the issue number and timestamp. A screenshot of one telegram without context rarely helps another engineer.
7. Commission integrations point by point
A gateway being online is not proof that integration works. Test every agreed point for:
- data direction;
- datapoint type and engineering unit;
- scaling and decimal precision;
- command priority;
- status feedback;
- update on restart;
- alarm and timeout behaviour;
- naming at both systems.
For 300 points, use a controlled witness sample only if the contract allows it and the integrators have already completed a full self-test. Otherwise “sampling” becomes a way to leave untested mappings behind.
8. Close snags without losing control of versions
Keep one issue register. Each item should name the room, function, cause, responsible party, ETS version fixed, retest date, and evidence. Avoid multiple chat threads with photos that never make it into the final record.
At practical completion, freeze a release candidate of the ETS project. Apply accepted changes to that version, retest affected functions, then export the final archive. Do not hand over a laptop folder containing final, final2, and latest-final projects.
Handover package
The owner should receive:
- final editable ETS project export;
- project password and Secure-device recovery process through an approved channel;
- as-built topology and cabinet drawings;
- device and firmware/application versions;
- group-address and datapoint schedule;
- scene and sequence descriptions;
- gateway mapping files;
- test and issue records;
- backup/restore instructions;
- operator and maintenance training.
Keep a read-only checksum or document-control record for the handed-over ETS file. Future changes can then be traced to a known baseline.
FAQ
Can KNX devices be commissioned before the loads are connected?
Addresses and applications can be downloaded, but final functional acceptance requires the real loads, sensors, interfaces, and recovery conditions.
Should every device receive a full download?
Use the ETS download variant appropriate to the change. A parameter or group-link change may not require rewriting every part, but ETS download status must be understood and the result tested.
What is the difference between Group Monitor and Bus Monitor?
Group Monitor is suited to normal group communication and can read or send group values. Bus Monitor records lower-level bus traffic and requires exclusive bus access during the capture.
Who should own the final ETS file?
The contract should state ownership, but the building owner normally needs the final editable project and credentials to maintain the asset and appoint qualified support.
Official references
- KNX Association, ETS download functions
- KNX Association, Bus Monitor, Group Monitor, and ETS Bus Activity Monitor
- KNX Association, device diagnostics
- KNXmart, KNX installation checklist before handover
Commissioning is complete when the installed functions can be demonstrated, diagnosed, restored, and understood by someone other than the original programmer.