What an undocumented system looks like in practice
The engineer who commissions a KNX system is almost never the one who services it five years later. That single fact should shape how every project gets documented — and on most projects, it doesn't.
Group addresses numbered in the order they happened to be created, not by function or floor. No comments in the ETS project. No as-built drawings. Naming conventions that exist only in the original installer's head, and left the building with him. The system works — right up until something needs to change, and a new engineer spends a full day reverse-engineering logic that a decent naming convention would have made legible in ten minutes.
What good structure actually looks like
KNX group addressing supports a few well-established structures — function-based (grouping by lighting, HVAC, blinds), building-based (grouping by floor or wing), or device-based. None is inherently superior; the failure mode isn't picking the "wrong" one, it's not picking one at all and letting addresses accumulate ad hoc. Two things matter more than which structure you choose:
- Group objects should be self-documented — named to match the function they represent, with a description clear enough that someone unfamiliar with the project can read it and understand what it does, not just what it's called
- The sub-group number should line up with the physical channel number wherever possible, so debugging on-site maps directly back to the project file instead of requiring a lookup table in someone's memory
Why this is a design Decision not paperwork?
A KNX system that's easy to read is easy to safely modify. One that isn't becomes a system nobody wants to touch — every future change turns into an investigation before it can even become a repair, and every investigation is billable hours the client didn't expect to pay for a "simple" request.
A system isn't finished when the lights turn on. It's finished when an engineer who never touched the original install can open the ETS project, understand the structure in minutes, and safely make a change without guessing.
Are we designing systems for the day they're commissioned, or for the decade they'll actually be serviced?
#KNX #BuildingAutomation #SmartHome #SystemDesign
Start writing here...
