A well-designed KNX group address (GA) structure is the foundation of a maintainable, scalable project. For small residential projects (50-100 GAs), any structure works. For large commercial buildings with 2,000+ GAs across multiple floors and disciplines, a poorly planned GA hierarchy becomes the biggest source of commissioning errors, maintenance headaches, and subcontractor handover failures. This guide covers the 3-level address format used by KNX professionals, functional vs topological organisation strategies, naming conventions, and ETS6 project management techniques for projects up to 500+ rooms.

KNX group address format: 3-level vs 2-level vs free

KNX supports three GA formats: 3-level (Main/Sub/Address: 31/7/255 max), 2-level (Group/Address: 31/2047 max), and free (0-65535). ETS6 default is 3-level — use this for all commercial projects. 2-level is used in older installations or when specific tools require it. Free format is rarely used. The total GA space is identical (65,535 addresses) regardless of format. 3-level example: GA 1/2/5 = Main Group 1 (Lighting) / Sub Group 2 (Floor 2) / GA 5 (Kitchen dimmer level). The 3-level structure is readable — any engineer can decode the GA meaning from the three numbers if a consistent scheme is followed.

Functional vs topological organisation

Two fundamental philosophies: Functional (by signal type): Main group = function (1=Lighting, 2=Blinds, 3=HVAC, 4=Energy, 5=Security, 6=Access). Sub group = floor or area. GA = specific device. Example: GA 1/2/4 = Lighting / Floor 2 / Meeting room 201 dimmer. Topological (by location): Main group = floor or building zone. Sub group = function. GA = specific device. Example: GA 2/1/4 = Floor 2 / Lighting / Meeting room 201 dimmer. Same information, different hierarchy. Professional recommendation: use Functional organisation for buildings with 2+ floors, multiple integrators, or BMS integration requirements. Reason: BMS integrators looking for all energy metering data (GA 4/x/x) can find everything under Main Group 4, regardless of floor. Commissioning engineer for lighting (GA 1/x/x) finds all lighting GAs under one main group. Topological is preferred for single-floor residential where the owner asks "what are all the group addresses for my bedroom?"

Recommended GA structure for commercial office building

Main Group 0 — System/Housekeeping: time/date telegrams, KNX system messages, bus voltage monitoring, PSU fault status. Main Group 1 — Lighting: Sub 0=Common (all floors), Sub 1=Floor 1, Sub 2=Floor 2, etc. GAs: 0=ON/OFF (1-bit DPT 1.001), 1=Absolute level (1-byte DPT 5.001), 2=Scene recall (1-byte DPT 18.001), 3=Level status feedback (1-byte, read-only for Gira X1), 4=Presence (from sensor, 1-bit DPT 1.002). Main Group 2 — Blinds/Shading: same sub-group structure. GAs: 0=UP/DOWN (1-bit DPT 1.008), 1=Position (1-byte DPT 5.001, 0=up, 255=down), 2=Slat angle (1-byte DPT 5.001), 3=Position status feedback. Main Group 3 — HVAC: GAs: 0=Setpoint (DPT 9.001), 1=Actual temperature (DPT 9.001), 2=Mode (DPT 20.102 HVAC mode: auto/heat/cool/fan), 3=Occupancy (DPT 1.002), 4=Valve position (DPT 5.001), 5=Fan speed (DPT 5.001). Main Group 4 — Energy: GAs: 0=Active power L1+L2+L3 total (DPT 9.001 W), 1=Energy import kWh (DPT 12.001 4-byte counter), 2=Reactive power (DPT 9.001 var), 3=Power factor (DPT 9.001 cos-phi), 4=Current L1 (DPT 9.001 A). Main Group 5 — Security: GAs: 0=Presence alarm (DPT 1.005), 1=Door open (DPT 1.002), 2=Panel armed (DPT 1.001), 3=SPD fault (DPT 1.001).

Sub-group numbering for floor/zone assignment

For a 20-floor commercial building: Sub Group 0 = All floors (broadcast commands — scene recall all lights off in fire evacuation). Sub Groups 1-20 = Floors 1-20 respectively. Sub Group 30 = Plant room/roof. Sub Group 31 = Car park. Within each sub group: GA 0-9 = Open plan office zones, GA 10-19 = Meeting rooms, GA 20-29 = Corridors, GA 30-39 = WCs/service areas, GA 50-59 = Individual desk lighting (if addressable). This structure accommodates 60 individually addressed areas per floor with 4 GAs each (on/off, level, scene, feedback) = 240 GAs per floor, 4,800 for 20 floors. Well within the 65,535 GA space.

ETS6 project management techniques

GA naming convention in ETS6: always use descriptive names, not just GA numbers. ETS6 > Group Addresses > each GA has Description field (up to 255 chars). Standard format: [Floor]-[Room]-[Function]-[Type]. Examples: "F2-MR201-Light-Switch", "F2-MR201-Light-Level", "F2-MR201-Light-Scene", "F2-MR201-Temp-Setpoint". ETS6 GA search: use ETS6 search (Ctrl+F) to find all GAs matching "F2" (floor 2) or "Temp" (all temperature GAs) — much faster than scrolling through 2,000 entries. ETS6 GA export for BMS: File > Export > Group Addresses > CSV or XML. Include: GA number, name, DPT, connected communication objects. Share this export with BMS integrator (Siemens Desigo CC, Schneider EBO) — saves 10-20 hours of BMS configuration versus manual entry. ETS6 project backup: export .knxproj file monthly during commissioning phase. Store in project documentation folder (SharePoint/NAS). ETS6 projects cannot be recovered from KNX devices alone — the project file is the single source of truth for all group address assignments and device parameters.

Common mistakes and how to avoid them

Mistake 1: Using 2-level GA format in ETS6 default 3-level project — sends ETS6 error on device download in some older firmware. Fix: use 3-level consistently. Mistake 2: Same GA assigned to multiple devices as "write" without understanding conflict. If two actuators both send on a shared status GA, telegrams collide. Fix: one device sends per GA (write), others receive only (read). Mistake 3: No feedback GAs for actuator status — visualisation shows command state, not actual state. Fix: always add separate status feedback GA for every controlled output. Actuator writes actual state (after execution) back to status GA. Mistake 4: Too many sub-groups for a simple building. Single residential apartment: Main Group 1 (Lighting) > Sub Groups 0-5 (rooms) > GAs 0-4 (functions) = max 30 GAs. No need for floor-level sub-grouping in a single-story apartment. Match GA structure complexity to project size. Mistake 5: GA numbers reused across projects. Use a project GA template document (Excel or ETS6 GA export) and start each new project from the same baseline template — copy and rename rather than inventing fresh.