Individual address rules — Area.Line.Device

Addressing rules:
  Area:    1–15  (0 = backbone)
  Line:    1–15  (0 = line coupler connection to area)
  Device:  1–255 (0 = line coupler itself; 255 reserved for line coupler PA)

First device on every new line:
  1.1.255  → Line coupler physical address (always .255 by convention)
             Actual end devices start from 1.1.1

Device numbering within a line:
  1.1.1    → First end device (sensor, actuator, push button)
  1.1.2    → Second end device
  ...
  1.1.64   → Maximum 64 end devices per KNX TP line (IEC 14543-3)

Multi-line example — 8-floor office:
  1.1.x    → Floor 1 lighting and blinds
  1.2.x    → Floor 1 HVAC and presence
  1.3.x    → Floor 2 lighting and blinds
  2.1.x    → Wing B, Floor 1 lighting (different area)
  0.0.0    → Unaddressed factory default — bus will not respond

Recommended 3-level group address topology

Main group → System function:
  1/x/x   → Lighting (switching, dimming, status)
  2/x/x   → Blinds and solar shading (up/down, position, slat angle)
  3/x/x   → HVAC (setpoint, actual temp, fan speed, valve position)
  4/x/x   → Security (alarm zones, motion, door/window contacts)
  5/x/x   → Energy (meter readings, demand, power factor)
  6/x/x   → Scenes (recall, store, all-off)
  7/x/x   → Emergency (lighting test, alarm routing)
  8/x/x   → Audio and media control
  9/x/x   → Access control (lock/unlock, bell, camera)
  10/x/x  → System (time, date, presence master, fault summary)

Middle group → Zone or floor:
  x/0/x   → Building-wide (global commands)
  x/1/x   → Floor 1 / Zone 1
  x/2/x   → Floor 2 / Zone 2
  ...
  x/7/x   → Floor 7 / Zone 7

Sub group → Individual data point:
  x/x/1   → Switch command (write)
  x/x/2   → Switch status feedback (transmit)
  x/x/3   → Relative dimming (write)
  x/x/4   → Absolute brightness value (write)
  x/x/5   → Brightness status feedback (transmit)

ETS6 Group Monitor — useful filter patterns

Filter by group address:
  1/*      → All lighting group addresses (Main group 1)
  1/1/*    → All Floor 1 Office A group addresses
  1/1/2    → Exactly one GA — lighting status for Office A

Filter by source individual address:
  1.1.5    → All telegrams sent by device 1.1.5 (e.g. a push button)
  1.1.*    → All telegrams from area 1, line 1

Useful during commissioning:
  Step 1: Press physical push button → telegram should appear
  Step 2: Verify Source = push button PA, Destination = correct GA
  Step 3: Verify DPT and value match expected (e.g. 1.001 = 1/On)
  Step 4: Verify actuator sends status feedback telegram on correct GA

Common errors visible in Group Monitor:
  - Wrong GA assigned → telegram goes to 0/0/1 instead of 1/1/1
  - Flag missing → Write flag off → telegram rejected, no bus traffic
  - Wrong DPT → value decoded as 0 when physical value is 100%
  - Flooding → cyclic telegram every 1s from misconfigured sensor

ETS6 backup procedure

Rule 1: Export .knxproj before any firmware update
  → Firmware update may reset device to factory defaults
  → Without a backup, all parameters are lost

Rule 2: Keep 3 project generations
  → ProjectName_v1_YYYY-MM-DD.knxproj  (initial commissioning)
  → ProjectName_v2_YYYY-MM-DD.knxproj  (first modification)
  → ProjectName_v3_YYYY-MM-DD.knxproj  (latest — always current)
  → Delete v1 when v4 is created (rolling 3-version window)

Rule 3: Store backups in 3 locations
  → Company NAS (primary)
  → Cloud storage with version history (secondary)
  → USB key left inside the panel (on-site emergency access)

Rule 4: Export GA CSV with each backup
  → GA CSV is readable without ETS6 — useful for BMS support calls
  → Filename convention: ProjectName_GA_YYYY-MM-DD.csv

Rule 5: Document ETS6 project password in secure password manager
  → Never use project password = "knx" or "1234"
  → Client must receive the password at handover