What Is KNX?

KNX is an open, ISO/IEC 14543-certified communication standard for building automation, merging three earlier European standards — EIB (European Installation Bus), EHS (European Home Systems), and BatiBUS — into a single unified specification. Governed by the KNX Association based in Brussels, the protocol is implemented by over 500 manufacturers offering more than 8,000 certified products, making it the dominant standard for intelligent building control in Europe and widely used across Asia, the Middle East, and increasingly North America.

KNX covers virtually every building function: lighting control, HVAC, blinds and shading, access control, energy metering, security systems, audio/visual control, and EV charging — all on a single installation bus.

Physical Media and Topology

KNX supports four physical media, each suited to different installation contexts:

  • KNX TP (Twisted Pair) — The most common medium for commercial buildings. Devices connect to a 2-wire bus (YCYM 2×2×0.8mm is standard) that carries both data and 29V DC power from a KNX power supply. The bus topology supports line, tree, and star segments. A single line supports up to 64 devices; multiple lines connect through line couplers to form areas, and multiple areas connect through backbone couplers — scaling to 57,375 devices in a single KNX TP installation.
  • KNX RF (Radio Frequency) — Wireless KNX at 868 MHz (EU) or 916 MHz (US) for retrofit applications where cabling is impractical. KNX RF supports bidirectional communication and co-exists with TP installations via RF/TP media couplers.
  • KNX IP — KNX tunneled over TCP/IP using KNXnet/IP protocol (UDP port 3671). Allows KNX devices and controllers to connect over existing LAN/WAN infrastructure. KNX IP is commonly used for backbone links between buildings and for remote access/monitoring.
  • KNX PL (Powerline) — Communication over 230V AC powerline wiring using CENELEC A-band (9 kHz). Less common, primarily used in residential contexts where additional bus wiring is prohibited.

The KNX Communication Model: Group Addresses and Datapoint Types

KNX uses a producer-consumer communication model built around Group Addresses rather than device addresses. This is fundamentally different from BACnet's client-server model:

  • A Group Address (GA) is a logical communication object, not tied to any physical device. GAs are organized in a 3-level (Main/Middle/Sub) or 2-level hierarchy, e.g., 1/2/15 = Lighting / Floor 2 / Desk area on/off.
  • A Sender (e.g., a push-button or presence sensor) writes a value to a Group Address. All devices subscribed to that GA as receivers (e.g., lighting actuators) react to the value simultaneously.
  • A device can be both a sender and receiver on different GAs — e.g., a HVAC controller sends temperature values to a feedback GA and receives setpoint values from a setpoint GA.
  • Datapoint Types (DPTs) define the encoding of Group Address values. DPT 1.001 is a 1-bit on/off switch; DPT 9.001 is a 2-byte floating-point temperature in °C (range -273 to +670.76°C, resolution 0.01°C); DPT 5.001 is a 1-byte percentage (0–100%). Correct DPT assignment is essential for interoperability.

ETS: The Engineering Tool Software

All KNX installations are configured using ETS (Engineering Tool Software), a proprietary application from the KNX Association available as ETS5 (legacy) and ETS6 (current). ETS is the single tool for:

  • Importing device product databases (ETS .knxprod files from manufacturers)
  • Configuring device parameters (sensitivity thresholds, timer delays, DALI ballast addressing)
  • Assigning Group Addresses to communication objects
  • Programming devices via the KNX bus (Download function)
  • Diagnosing network issues using the Group Monitor and Bus Monitor tools

ETS operates on a project file (.knxproj) that is the authoritative record of the entire installation. Best practice requires storing ETS project files in version control and maintaining them throughout the building's lifecycle — changes made without updating the ETS project file create dangerous discrepancies between the as-built system and documentation.

KNX and DALI Integration

In commercial lighting applications, KNX is almost always paired with DALI (Digital Addressable Lighting Interface, IEC 62386). DALI provides fine-grained individual luminaire control (0–100% dimming, color temperature, RGB, emergency lighting status) while KNX provides the room-level and building-level control logic. A KNX/DALI gateway bridges the two systems: KNX Group Address commands (scene recall, dim level, emergency test) are translated to DALI commands delivered to individual ballasts or broadcast to DALI groups. DALI 2 (IEC 62386 edition 2) adds certified device types, push-button inputs, occupancy sensors, and daylight sensors directly on the DALI bus, reducing the number of KNX input devices required.

KNX Secure

KNX Secure, standardized as part of ISO/IEC 14543-3-x and available in ETS5.7+, adds cryptographic security to KNX communications in two layers:

  • KNX IP Secure — Encrypts KNXnet/IP tunneling and routing connections using AES-128 CCM. Requires IP Secure-certified KNX IP devices.
  • KNX Data Secure — Encrypts individual KNX TP telegrams at the application layer, protecting against eavesdropping and replay attacks on the physical bus. Each secure device is provisioned with a Device Authentication Code (DAC) and Tool Key (FDSK) during manufacturing.

KNX Secure is strongly recommended for all new commercial installations, particularly those controlling access control, building entry, or safety systems where unauthorized command injection could have physical consequences.

KNX vs. BACnet for Commercial Projects

Both KNX and BACnet are widely used in commercial buildings, but they occupy different niches:

  • KNX strengths: Decentralized (no controller required — intelligence lives in devices), faster installation for room-level control, dominant in European markets, excellent for lighting/shading/access, and very large product ecosystem at the device level.
  • BACnet strengths: Better for complex HVAC sequence programming, interoperability with large chillers/AHUs, dominant in North American and global HVAC markets, richer object model for energy management, and stronger analytics/FDD ecosystem.
  • Many high-specification buildings deploy both: KNX for room controls (lighting, blinds, occupancy, comfort panels) and BACnet for HVAC plant control, with a KNX-BACnet gateway providing integration at the building management level.