KNX vs BACnet vs Zigbee vs Matter: where each protocol fits

A modern building rarely runs on a single protocol. KNX dominates room-level control. BACnet rules HVAC plant. Zigbee is everywhere in retail smart-home products. Matter is the new arrival aiming at residential cross-vendor. Knowing where each fits keeps your projects pragmatic.

KNX. Open standard ISO/IEC 14543-3, also EN 50090. Decentralized: every device is autonomous, no central controller required. Strongest at room-level control: lighting, blinds, room HVAC, scene control. Mature ecosystem with deep ETS tooling. Twisted pair, IP, RF, and powerline media. Lifetime measured in decades.

BACnet. ASHRAE/ANSI standard 135. Centralized: typically a building automation server orchestrates devices. Strongest at central plant: chillers, AHUs, boilers, large-scale HVAC. Weak at lighting and room-level control. Bridges to KNX commonly via KNX-BACnet gateways at the floor level.

Zigbee. IEEE 802.15.4 mesh radio standard. Strongest at retail smart-home products: light bulbs, plug-in switches, sensors, locks. Cheap, easy to install, but vendor interoperability is famously inconsistent (Zigbee 3.0 helps but does not solve the issue). Bridges to KNX via Home Assistant or vendor-specific gateways.

Matter. Newer standard backed by Apple, Google, Amazon, Samsung. IP-native, runs over Wi-Fi, Thread, and Ethernet. Strongest at residential cross-vendor (an Apple Home and a Google Home can both control a Matter device). Limited feature set today; most products are basic switches and lights. Watch the next two to three years; bridges to KNX are emerging.

When to use which. KNX for any whole-building control project, period. BACnet for the central plant if the building has one. Zigbee or Matter for retail products the customer brought themselves and wants to integrate. Bridge between worlds at the visualization layer or with hardware gateways at the cabinet, not deep inside any one protocol.