Introduction
A KNX system does not fail at handover because of missing features.
It fails because small commissioning steps were skipped under time pressure.
Many post-handover issues — offline devices, wrong feedback, unstable scenes, confused users — are not design problems. They are commissioning discipline problems.
This article provides a practical KNX commissioning checklist to be completed before handover, based on what actually prevents callbacks, complaints, and emergency site visits.
Commissioning Is Not Programming
Programming makes the system work.
Commissioning makes the system reliable, predictable, and maintainable.
A system can be fully programmed and still be poorly commissioned.
???? PHASE 1: Infrastructure & Electrical Health
These checks must be completed before touching logic or scenes.
✅ Bus Power Verification
✔ Bus voltage measured at power supply
✔ Bus voltage measured at farthest device
✔ Voltage stable under load
✔ Power supply operating below rated current
If power is marginal, stop commissioning.
✅ Line & Topology Validation
✔ Physical topology matches ETS topology
✔ Line couplers / IP routers correctly placed
✔ No unused or ghost devices in ETS
✔ Correct area and line addressing
Topology mismatch creates invisible problems later.
✅ Cable & Connection Inspection
✔ No loose bus terminals
✔ No crushed or stressed cables
✔ Proper strain relief in panels
✔ No exposed conductors
Most future faults start here.
???? PHASE 2: Device & Communication Integrity
✅ Individual Address Audit
✔ All devices respond correctly
✔ No duplicate addresses
✔ Replaced devices correctly reassigned
✔ No “unknown” devices on the bus
Address conflicts must be resolved now — not later.
✅ Group Communication Verification
✔ All group addresses trigger correct functions
✔ No delayed or missed responses
✔ Cross-line communication verified
✔ No unnecessary group traffic
Use Group Monitor to confirm clean communication.
✅ Filter Table Validation
✔ Filter tables generated
✔ Downloaded to all couplers and routers
✔ No over-filtering
✔ No missing feedback across lines
Filters must reflect the final design.
???? PHASE 3: Logic, Feedback & User Behaviour
✅ Control vs Feedback Separation
✔ Separate group addresses for control and feedback
✔ Keypads listen to feedback, not commands
✔ Feedback accurate from all control points
This single check eliminates most “LED not working” issues.
✅ LED & Status Indication Check
✔ LEDs show real load state
✔ Correct polarity (normal/inverted)
✔ Behaviour consistent across rooms
✔ No misleading or stuck LEDs
LEDs shape user trust immediately.
✅ Scene Behaviour Validation
✔ Scenes trigger expected results
✔ Partial scene activation tested
✔ Scene recall tested from multiple points
✔ Scene changes reflected correctly in feedback
Scenes must behave consistently, not just “work once”.
???? PHASE 4: KNX IP & Network Stability (If Applicable)
✅ IP Router & Routing Health
✔ All IP routers reachable
✔ Routing enabled
✔ Group communication across lines verified
✔ No intermittent routing loss
ETS connection alone is not proof of routing health.
✅ Network Configuration Check
✔ KNX VLAN (if used) correctly assigned
✔ Multicast allowed
✔ IGMP snooping verified or disabled
✔ EEE disabled on KNX ports
Network issues surface after handover, not during demos.
???? PHASE 5: Stress & Real-World Testing
✅ Simultaneous Operation Test
✔ Multiple buttons pressed simultaneously
✔ Multiple scenes triggered
✔ Motion sensors active concurrently
✔ Logic running under load
KNX systems must survive real usage, not ideal demos.
✅ Time-Based Behaviour Check
✔ Test during different times of day
✔ Verify logic tied to schedules
✔ Confirm night / day behaviour
Many problems appear only outside commissioning hours.
???? PHASE 6: Failure & Recovery Scenarios
✅ Power Cycle Test
✔ Power supply rebooted
✔ Devices recover correctly
✔ No stuck states
✔ Feedback restored automatically
Recovery behaviour is as important as normal operation.
✅ Network Interruption Test (IP Systems)
✔ Temporary network disconnect
✔ Reconnection without manual intervention
✔ Routing restored automatically
Clients experience outages — systems must recover gracefully.
???? PHASE 7: Documentation & Handover Readiness
✅ ETS Project Hygiene
✔ Clear naming conventions
✔ Logical group address structure
✔ Comments added where logic exists
✔ Backup saved and archived
A clean ETS project is part of the deliverable.
✅ Client-Facing Documentation
✔ Basic system explanation
✔ Scene descriptions
✔ Do’s and Don’ts
✔ Service contact information
Documentation reduces support calls.
✅ Integrator Exit Checklist
✔ Final ETS backup created
✔ IP addresses documented
✔ Power ratings recorded
✔ Change history noted
If you leave today, another engineer should understand the system.
Most Common Steps Skipped (Seen on Real Sites)
❌ Power margin verification
❌ Filter table checks
❌ Feedback testing
❌ Network stress testing
❌ Recovery behaviour testing
These omissions cause 80% of post-handover issues.
Why This Checklist Saves Time
Because:
- Problems are fixed before users see them
- Callbacks are reduced dramatically
- Client confidence increases
- System reputation improves
Good commissioning is invisible — bad commissioning is unforgettable.
Conclusion
KNX commissioning is not about ticking boxes — it is about proving system readiness under real conditions.
A system that passes this checklist:
- Is stable
- Is predictable
- Is maintainable
- Survives real-world use
Before handover, ask only one question:
“If I’m not here tomorrow, will this system still behave correctly?”
If the answer is yes — commissioning is complete.
