Skip to content
Website
🧱 CFC 238KNX home automation: topology, addressing and parameter settingChapter 4 of 10 in the section

Addressing cleanly: physical address, group address and naming plan

This chapter details the logical structuring of a KNX project: the distinction between physical address and group address, the three-level hierarchy ensuring seamless handover to a third party, device labelling rules in distribution boards, and the programming file export procedure for the project records.

Key takeaways

  • The physical address locates the hardware component while the group address links the functionalities.
  • The three-level hierarchy separates main functions, geographical zones and control points.
  • Device naming in ETS must strictly replicate the physical designation of the low-voltage cabinet.
  • The complete source file exported from ETS must be handed over to the client with the operating binder.

Building a three-level tree structure readable without the designer present

On a commercial or major residential construction site in Romandy, the telematics technician or integrator does not design a home automation network for themselves, but for the operator of the structure. Two types of addresses coexist on the bus: the physical address and the group address. The physical address (Area.Line.Device, for example 1.1.12) identifies the hardware location of the component on the twisted-pair cable. It serves solely for the initial download of the application programme and diagnostic operations via the line coupler. The group address, on the other hand, establishes functional links between inputs (push-buttons, presence detectors, weather stations) and outputs (switching actuators, 1-10 V or DALI dimming modules, blind actuators).

KNX group address
Logical instruction telegram shared between one or several transmitters and receivers. Unlike the physical address which is unique per device, a single communication object can be linked to multiple group addresses to respond to direct, central or scene commands.

To ensure the longevity of the installation, the group address structure must imperatively adopt the three-level model (Main group / Middle group / Subgroup). A standardised architecture assigns the main group to the trade or major technical function, the middle group to the spatial location or sub-function, and the subgroup to the concrete action.

Recommended three-level structuring matrix in Romandy
Main group (Trade)Middle group (Zone / Storey)Subgroup (Specific action)Address exampleStandardised designation
0: Central functions0: Entire building1: Master shut-off0/0/1CEN_Bld_Master-Off
1: Switching lighting1: Ground floor10: Corridor ON/OFF command1/1/10LGT_GF_Corridor_Cmd
1: Switching lighting1: Ground floor11: Corridor status feedback1/1/11LGT_GF_Corridor_Stat
2: Dimming lighting2: 1st floor20: Office 101 relative dimming2/2/20DIM_L01_O101_Rel
3: Blinds / Valves1: Ground floor5: Living room Up / Down3/1/5BLI_GF_Living_Up-Dn

The device naming convention within the ETS software tree structure must unambiguously mirror the reference designations marked on the wiring diagrams and distribution board labels. A device must never keep its default factory name. The device name character string must include the distribution board reference, the physical location of the control or action element, and the abbreviated product designation.

  • Modular actuator in cabinet: DB-GF_ACT-SW8_01 (Ground-floor distribution board, 8-channel switching actuator no. 1).
  • Storey push-button: PB_L01_Master-Bed_4G (Wall push-button on first floor, master bedroom, 4-gang).
  • Interface gateway: DB-BS_GW-DALI_L1 (Basement board, DALI gateway to KNX bus line 1).
  • Room sensor: SNSR_GF_Living_Temp-CO2 (Combined temperature and carbon dioxide sensor in living room).

Securing the handover: project file export and technical file delivery

Under Swiss construction law, the contractor assumes liability for the proper and faithful execution of their mandate pursuant to art. 364 CO. In the field of extra-low voltage and building automation, this requirement extends to the transmission of the software elements necessary for the maintenance of the installation. Delivering a KNX network while withholding the project source file without handing it over to the client constitutes professional negligence that paralyses any subsequent troubleshooting intervention.

  1. Project database cleanupDelete unused phantom devices, orphaned group addresses without a linked communication object, and purge obsolete application versions prior to project sign-off in the ETS software.
  2. Integrated object documentationFill in the description line for each group address and each specific device parameter directly within the provided text fields of the project tree structure.
  3. Standardised archive exportExport the complete file in the official project archive format (.knxproj). For KNX Data Security secured installations, the security certificate and the decryption key table must imperatively be attached.
  4. Address list generationProduce exports in the form of CSV spreadsheets and printable PDF reports compiling all physical addresses, group addresses and their associations.

The technical file at the end of the construction site, filed in the pocket of the distribution cabinet or archived on sealed digital media, includes the raw software backup, the schedule of physical components labelled according to installation schematics, and the programming matrix. Any network electrician or maintenance technician intervening subsequently must be capable of analysing the bus using a group monitor without having to guess the destination of a telegram.

Physical addressing and device naming convention in cabinets

Physical addressing in a KNX installation follows a strict hierarchy dictated by the network topology: Area.Line.Device (for example 1.1.25). This address serves only two specific functions: locating the component on the bus cable for diagnostics and downloading its programming from the ETS software. It never takes part in executing daily control commands. Assigning a physical address at random immediately complicates the maintenance task of the technician intervening after the delivery of the construction site.

A rigorous device naming convention compensates for the lack of direct visibility inside distribution cabinets or flush-mounting boxes. Each device declared in ETS must receive a unique designator incorporating its geographical location, hardware function and board index. This designation appears on the identification labels affixed directly to the DIN rail module enclosure or on the back of the push-buttons.

Example of standardised naming convention for KNX devices
Physical addressDevice name (ETS)Physical locationHardware function
1.1.1DB-L0_ACT-LGT_01Storey 0 board, row 28-channel binary switching actuator
1.1.2DB-L0_ACT-DIM_01Storey 0 board, row 24-channel universal dimming actuator
1.1.10PB_L0-LIV_01Ground-floor living room, entrance on kitchen side4-gang push-button with sensor
1.1.20DET_L0-COR_01Ground-floor corridor, false ceiling centrePIR presence and brightness detector

Functional subdivision of group addresses and backup longevity

The three-level group address structure (Main group / Middle group / Subgroup) represents the true operational language of the building. For a successor to understand the operation of the installation without an explanatory guide, the addressing plan must follow a standardised logic by trade or by geographical zone. The division by trade remains the most universal standard in Romandy: the main group defines the technical discipline (lighting, blinds, HVAC), the middle group identifies the room or subsystem, and the subgroup carries the elementary action and its status feedback.

  • Main group (0 to 31): Subdivision by technical trade (e.g. 1 = Lighting, 2 = Motorised blinds, 3 = Heating and ventilation).
  • Middle group (0 to 7): Spatial subdivision by storey or room group (e.g. 0 = Central and master functions, 1 = Ground floor, 2 = 1st floor).
  • Subgroup (0 to 255): Specific functional object (e.g. 1/1/10 Living Room On-Off Command, 1/1/11 Living Room Status Feedback, 1/1/12 Living Room Dimming Value, 1/1/13 Dimming Value Feedback).

The systematic separation between the control command and the status feedback object prevents display desynchronisation on control keypads and supervision interfaces. Each On-Off command must possess its own address, immediately followed by the status feedback address transmitted exclusively by the physical actuator. This rule guarantees accurate visual feedback, including in the event of a manual command applied directly to the front face of a board-mounted device.

  1. Communication flags assignmentMeticulously configure the flags of communication objects in ETS: 'C' (Communication), 'R' (Read), 'W' (Write), 'T' (Transmit) and 'U' (Update). An error on the 'W' flag of a status feedback object can overwrite the actual actuator value with an erroneous status arriving from the bus.
  2. Project export and secure archivingExport the complete project archive in the standardised .knxproj format from ETS. Set a strong password if the project incorporates KNX Data Secure devices, and record this password in plain text in the documentation handed over at the acceptance of the work.
  3. File placement on sitePlace a copy of the ETS project file as well as the address report in PDF format on an industrial USB flash drive, stored in the drawing pocket of the main distribution board, exclusively for the attention of the plant operator and service technicians.

Takeover of corrupted or undocumented bus: emergency protocol and reconstruction

When an integrator or telematics technician takes over a construction site without an ETS archive (.knxproj) or identification drawings, the risk of a complete deadlock is genuine. An incorrect manipulation on the KNX bus can overwrite the programming of a device and paralyse an operational level. Faced with a corrupted database, the technician must secure the existing setup before making any software modification. The contractor is liable for the proper and faithful execution of the work pursuant to art. 364 CO.

  1. Passive mapping and physical detectionConnect the USB or IP interface without injecting data. Launch a line diagnostic in ETS to identify all active physical addresses. This reading scans devices without modifying their application memory. Record each detected physical address against the actual component labelling in the control cabinet.
  2. Bus monitor traffic analysisActivate the group monitor during a representative period of building activity. Record telegrams sent by sensors and local controls. Observing communication objects makes it possible to correlate telegrams with actual loads and deduce the function schedule: switching, dimming, regulation or status feedback.
  3. Handling protected devicesAttempt to read application programme versions. If a device has an unknown access password or authentication key linked to KNX Data Secure, a partial unload is impossible. A factory reset via push-button or bus disconnection is then mandatory to reintegrate the device into a blank project.
  4. Tree reconstruction and re-addressingRecreate a clean three-level tree structure (domain, function, load). Assign group addresses according to the new naming convention of the technical file. Then download physical addresses individually followed by application programmes, module by module, starting with modular actuators in the board before tackling room push-buttons.

Each modification to the control network must be backed up incrementally with a timestamp and exported to external storage. An intervention log records reset devices and recommissioned links, in order to provide the client with technical documentation that is fully verifiable and serviceable by a third party.

Frequently asked questions

What should be done if two devices mistakenly share the same physical address?

The conflict causes collisions on the TP bus and renders ETS downloads impossible. Disconnect the red and black WAGO bus connector from one of the two devices to restore communication with the first. Change its physical address in ETS, then reconnect the second piece of equipment. Use the programming LED flashing function to physically locate the device concerned in the cabinet or false ceiling before reprogramming the line.

Why is it mandatory to separate the switching command address from the status feedback address?

A group address transmitting both the command and status feedback causes a logical loop: the actuator returns its status on the command address, which rearms or disrupts push-buttons and supervision systems. In KNX, a command object only listens to its action group, whilst the status object transmits on a dedicated address. This dissociation ensures the consistency of push-button indicator LEDs during central or scene commands.

What file format must be demanded upon handover of the home automation work?

The installer must hand over the complete project archive in the standardised .knxproj format, not locked by an undisclosed password. This single document contains the topological database, the group address tree, the application parameters of each component and the cabinet notes. Exporting a simple PDF list or a CSV spreadsheet is insufficient to allow a successor to reprogram the installation without starting from scratch.

How should group addresses be structured for a multi-storey office building?

Adopt a standardised three-level structure: the main group defines the trade or discipline (e.g. lighting, blinds), the middle group identifies the level or geographical zone (e.g. ground floor, 1st floor), and the subgroup targets the specific action (e.g. office 102 command, office 102 status feedback). This logic offers up to 65,535 combinations and allows circuits to be added later within a zone without disrupting the numbering of adjacent storeys.

Texts and standards cited

  • CO art. 364contractor's obligations: liability subject to the same rules as that of an employee; performs the work in person or under personal direction; unless customary or agreed otherwise, provides at own expense the necessary means, plant and tools

In the same section