KNX installation is easier to get right while the drawings are still open. We plan bus wiring and controlled circuits around the rooms, then define the keypad functions. You should know how the home will behave before equipment is ordered.
Quick answer
A KNX system lets certified devices exchange control messages over a common bus or IP network. Sensors publish events and actuators control loads according to ETS configuration. Multi-brand capability is useful, but only when the project file and group-address logic are maintained.
Project management consultancy (PMC)
KNX PMC can help keep design decisions and commissioning records together as the project moves between contractors. The final project files should not become a mystery at handover.
KNX suits projects that can accommodate its wiring and commissioning needs. A finished room may call for a different approach.
Review topology, bus power and actuator schedules against the room requirements.
Check panel space, cable routes and keypad locations before finishes restrict access.
Agree delivery of the commissioned ETS project and address records, with witnessed room tests.
The appointment must identify who programs the system and what project-file access the owner receives. No certification is implied.
Discuss the scope with usUnderstand
Read the adjacent technical page before choosing equipment. It may change the wiring, network or control method that belongs in the brief.
A wall key does not have to be wired directly to a lamp circuit. It can send a KNX telegram that an actuator interprets. That separation makes changes possible in software, while the bus wiring and commissioned database keep the system organised.
ETS holds the project topology, device product data, physical addresses, parameters and group-object links. KNX Association describes it as the manufacturer-independent tool for planning, configuring and commissioning KNX installations.
The final archive and relevant passwords belong in the handover. Without them, even a minor change becomes an archaeology exercise.
Topology depends on device count, traffic, physical layout and power-supply design. Line and area couplers provide structure and filtering; IP interfaces or routers connect selected parts to Ethernet.
The drawing records supply location, line segments and device addresses. Rules are checked against current KNX documentation and selected product data.
A sensor exposes communication objects such as switching, dimming or measured values. ETS links those objects to group addresses read by one or more actuators or controllers.
Devices receive addresses and parameters, functions are tested, bus traffic is inspected where needed, and secure settings are verified for the chosen products. The result is backed up after witnessed changes.
Gateways connect KNX to systems such as DALI, HVAC or a visualisation platform. Each adds a mapping table and failure boundary, so it should exist for a defined function rather than to collect logos.
Budget depends on points, actuator channels, bus segments, power supplies, couplers, keypad and sensor choices, panel size, ETS engineering and integrations. KNX can reduce dependence on one product family at the protocol level, but devices, application programs and commissioned project data still require disciplined selection. Conventional controls or a smaller wireless system may suit a limited retrofit with few coordinated functions.
The delivery sequence covers topology and load schedules, cable and panel inspection, device addressing, application programming, group-object testing, scene tuning and backup export. The owner should receive the ETS project, product databases where permitted, physical and group address schedules, passwords and a change log. Loss of visualization or an IP gateway need not stop bus-level functions designed locally. Loss of a line power supply or actuator affects its segment, so segmentation, spares and fault isolation matter.
The bus is deliberate. KNX wired automation normally carries commands and device communication on a dedicated bus while actuators switch or dim the connected loads; topology, power supplies, line limits, panel space and the retained ETS project matter more than treating the word wired as a promise of universal compatibility.
| Artefact | Contains | Needed at handover |
|---|---|---|
| Topology drawing | Lines, couplers and supplies | Yes |
| Group-address schedule | Functions and linked objects | Yes |
| ETS archive | Device parameters and project database | Yes |
Evaluate
Bring the floor plan, reflected ceiling plan or equipment schedule. We can mark assumptions, interfaces and unresolved choices before procurement.
Independent learning
These optional references are published by the organisation named below. They are linked rather than embedded, so the page does not load a video player or start playback.
A standards-body webinar comparing conventional wiring with a KNX bus and explaining sensors, actuators and reprogrammable links. Opens on YouTube in a new tab.
Written by: SmartR Spaces
Technical review: M&M Smarter Automation LLP
Content updated:
Next step
A useful proposal starts with the property, expected behaviour and handover standard. Product names come after those decisions.