Table of Contents
- What Professional KNX Commissioning Services Actually Involve
- Step 1: Design and Device Addressing
- Step 2: KNX System Programming Services in Practice
- Step 3: Testing, Scenes and Sign-Off
- KNX Project Handover Documentation: What You Should Receive
- KNX Smart Home Integration Costs: What Drives the Figure
- Common Mistakes to Avoid When Hiring a KNX Commissioning Service
- Conclusion
- Frequently Asked Questions
Last Updated: September 15, 2026
What Professional KNX Commissioning Services Actually Involve
Professional KNX commissioning services cover the design, programming, testing and handover of a building’s KNX automation system, turning installed cabling and devices into a working, documented control system. This guide explains exactly what happens at each stage, so you know what you are paying for and what to expect from your installer.
Commissioning is not a box-ticking exercise at the end of a build. It is the stage where lighting, heating, shading and security start behaving as one system rather than a collection of switches. Get it wrong and you inherit a house full of features nobody can operate confidently.
Below, we break down the full process, the documentation you should receive, and the mistakes that cost homeowners and property managers the most.
Installation Versus Commissioning: Two Different Jobs
First fix and second fix put the cable and hardware in place. Commissioning makes that hardware do something.
An electrician can install KNX cable, actuators and push-buttons perfectly and still leave the system non-functional, because nothing has been addressed, parameterised or linked. Commissioning is a separate skill set, usually delivered through ETS software, the manufacturer-independent tool maintained by the KNX Association.
A common mistake is assuming your general electrician will “sort the programming at the end”. That is where projects stall.
What You’ll Need Before Work Starts
Commissioning runs smoothly when the groundwork is done. Before any programmer sits down with your project, you should have:
- A full device schedule listing every KNX component and its location
- Accurate as-built drawings showing cable runs and distribution boards
- Confirmation that the bus is powered, terminated and free of wiring faults
- Your functional brief: which lights, circuits, scenes and schedules you actually want
- Network access and credentials for any IP gateways or visualisation servers
Miss any of these and the commissioning engineer spends paid time chasing information instead of programming.
Step 1: Design and Device Addressing
Design and addressing come first, because every later step depends on them. The engineer reviews the functional brief, maps each device to a physical address, and groups devices into logical lines and areas.
Physical addressing is the equivalent of giving every device a postal address on the bus. Group addressing is what actually makes things happen: a group address links a sensor to an actuator, so pressing a button dims a circuit.
| Stage | What Happens | Typical Duration |
|---|---|---|
| Design review | Brief checked against device schedule | Half a day |
| Physical addressing | Each device given a unique address | One to two days |
| Group address planning | Functions mapped to group addresses | One day |
| Parameterisation | Device behaviour configured in ETS | Two to five days |
| Testing and sign-off | Functions verified, faults corrected | One to two days |
Timings shift with project size. A large commercial scheme with hundreds of devices takes considerably longer than a single luxury residence (What is ETS?).
Step 2: KNX System Programming Services in Practice
Programming is where the system takes shape. The engineer downloads parameters to each device, builds the group address links, and configures behaviour such as dimming curves, occupancy logic and heating schedules.
Good KNX system programming services go beyond making buttons work. They build logic that suits how the building is actually used: corridor lighting that follows occupancy, blinds that respond to sun position, heating that backs off when a room is empty.
This is also where visualisation is configured. Platforms such as Logic Machine or Iridium Server sit alongside the KNX bus to give end users a touchscreen or app interface rather than a wall of buttons. The KNX Association’s guidance on system architecture is worth reading if you want to understand how these layers fit together.
Ask your commissioning engineer to document group address naming conventions from day one. An unlabelled project with thousands of addresses is nearly impossible for a different engineer to maintain later, and you will pay for that confusion at the next service visit.
Step 3: Testing, Scenes and Sign-Off
Testing proves the system works as specified, and scenes are the part end users notice most. The engineer verifies every function individually, then tests them together under realistic conditions.
Scene programming bundles multiple actions into one command. A “good morning” scene might raise blinds, bring up selected lighting at a set level, and adjust heating. A “cinema” scene dims everything except accent lighting and closes the blinds.
Testing should cover:
- Every push-button, sensor and actuator function
- Scene recall and correct behaviour on repeat activation
- Fault behaviour, including what happens if the bus loses power
- Remote access and app control, if included
- Time schedules and astronomical functions
Sign-off happens once you have walked the building and confirmed each function behaves as briefed. Do not accept sign-off before this walkthrough.
KNX Project Handover Documentation: What You Should Receive
KNX project handover documentation is the record that lets any competent engineer maintain your system without starting from scratch. Without it, future changes mean reverse-engineering the whole installation.
At minimum, you should receive:
- The ETS project file, with a note of the software version used
- A group address list with plain-English descriptions
- Device schedules with locations and model references
- Network and IP configuration details
- Scene and schedule definitions
- Contact details for ongoing support
Treat the ETS project file as the single most valuable document in the pack. If your installer will not hand it over, that is a serious warning sign.
Some installers withhold the ETS project file to lock you into their service. If you change provider later, the new engineer may have to rebuild the entire project from scratch, which is a substantial and avoidable cost.
KNX Smart Home Integration Costs: What Drives the Figure
KNX smart home integration costs depend on device count, system complexity, the number of integrated subsystems, and whether commissioning is bundled with installation or quoted separately.
Pricing for KNX commissioning is project-based, so no honest provider quotes a figure before reviewing your device schedule and functional brief. What you can control is the scope you bring to that conversation. For a specific figure, request a quote based on your drawings and brief rather than accepting a rough estimate over the phone.
The biggest cost drivers are:
- Device count. More devices mean more addressing, parameterisation and testing time.
- Integration depth. Linking KNX with audio-visual, security or access control adds configuration work.
- Visualisation. A bespoke touchscreen interface takes design and programming time that a basic wall panel does not.
- Documentation quality. Thorough handover packs take time to produce, and they are worth paying for.
- Site conditions. Live buildings, occupied hotels and phased handovers all slow the process.
Commissioning is typically a modest share of total project cost, but it determines whether the other 80% works. Cutting it is the fastest way to turn a premium system into an expensive frustration.
For a specific figure, request a quote based on your drawings and brief rather than accepting a rough estimate over the phone.
Common Mistakes to Avoid When Hiring a KNX Commissioning Service
Hiring badly is expensive. These are the mistakes we see most often, and each one has a clear fix.
| Mistake | Why It Hurts | What to Do Instead |
|---|---|---|
| Choosing on price alone | Cheap commissioning often skips documentation and testing | Ask what the handover pack includes |
| No functional brief | Engineer guesses your intent, you get unwanted behaviour | Write down every scene and schedule you want |
| Withholding the ETS file | Future changes cost far more | Make handover of the project file a contract term |
| Commissioning before wiring is verified | Fault-finding time billed as programming time | Confirm bus health before the engineer arrives |
| No support agreement | Small faults become long outages | Agree a maintenance arrangement upfront |
A second common issue is brand fragmentation. Homeowners often already own Philips Hue lighting or basic automation gear, and assume a KNX engineer will either absorb it all or demand a full rip-out. The honest answer sits in between: KNX integrates well with many third-party systems through gateways, but each integration needs configuring, and not every device is worth the effort.
The other question worth asking is what happens after installation. A system is only as good as the support behind it, which is why AME Electrical provides ongoing support rather than treating handover as the finish line.
Conclusion
Frequently Asked Questions
What is involved in professional KNX commissioning?
Commissioning is the stage where the physical installation is programmed and brought to life. An engineer assigns individual addresses to every device, links them into group addresses, loads application programs, sets lighting scenes, heating schedules and blind positions, then tests each function and hands over the project file. It is separate from first-fix wiring and normally happens once all devices are fitted and the bus is powered.
Why is professional commissioning essential for KNX systems?
KNX hardware is only as good as its configuration. Poorly grouped addresses cause lights to trigger from the wrong switch, heating to fight itself and scenes to fail. A certified engineer builds the logic so every device behaves predictably, applies KNX Data Secure settings and leaves a project file that any future engineer can open, edit and extend without re-commissioning the whole system.
How do I find a certified KNX commissioning engineer?
Look for partners listed on the official KNX Association website, then check that the firm holds certified partner status and can show completed projects similar to yours. Ask whether they program in-house or subcontract, request references from comparable residential or commercial sites, and confirm they will hand over the ETS project file rather than keeping it locked away.
What documentation should I expect after KNX commissioning?
A complete handover pack normally includes the ETS project file, a device schedule listing individual addresses, group address lists, network and IP settings, a backup of the configuration and user guides for lighting scenes, heating and access control. Without these, any future engineer must reverse-engineer the system, which adds time and cost to every change.