KNX and BACnet are both open international standards for building automation, but they operate at different layers of the building control hierarchy and serve different purposes. In most large commercial buildings — offices above 5,000m², hotels, hospitals — both protocols coexist: KNX at the field level (controlling lights, blinds, access) and BACnet at the management level (HVAC controllers, energy meters, BMS communication). Understanding where each protocol belongs prevents specification mistakes that lead to expensive gateway hardware or system re-work.

Where each protocol operates

KNX (IEC 14543-3): designed for field-level device control — pushbuttons, relay actuators, dimmer actuators, blind actuators, binary inputs, room controllers. Bus-powered at 29V DC, 9600 baud TP or 10Mbit KNXnet/IP. Latency: < 50ms for telegram delivery across a single line. Strengths: low cost per field device, high number of certified manufacturers (450+), simple cable infrastructure (2-core KNX TP). Weaknesses: no native HVAC system protocol (integrates HVAC via gateways), limited BMS data aggregation capability in native KNX without add-on platforms. BACnet (ASHRAE 135, ISO 16484-5): designed for HVAC controllers, building management communication, and supervisory integration. BACnet/IP (UDP, port 47808) or BACnet MS/TP (RS-485). Strengths: native language of HVAC controllers (Siemens, Honeywell, Schneider), BMS platforms speak BACnet natively, standard alarm and trending objects (Notification Class, Trend Log). Weaknesses: no standard KNX field device in BACnet — lighting control via BACnet requires binary output objects commanding relay panels, which is less elegant than native KNX.

Typical commercial building architecture

Standard 10,000m² office tower: BACnet layer — Siemens PXC HVAC controllers for air handling units, VAV boxes, chiller plant (all communicate via BACnet MS/TP to a BACnet IP backbone). Desigo CC BMS aggregates all BACnet data. KNX layer — field devices throughout all floors: MDT relay actuators for lighting, MDT dimmer actuators for LED lighting, blind actuators for external solar shading, binary inputs for occupancy sensors. KNX IP routers on each floor connect to building LAN (VLAN 10). Integration layer — Lingg and Janke KNX Virtual OPC UA server on building server publishes KNX data to Desigo CC as OPC UA client. Intesis IN701KNX translates critical KNX alarms (fire evacuation lighting override) to BACnet Binary Values in Desigo CC. This three-layer architecture is the norm in European commercial buildings designed by specialist M&E consultants.

When KNX replaces BACnet HVAC

For residential and small commercial (up to 2,000m²): all automation can be in KNX. HVAC integration: KNX room thermostat group address (DPT 9.001) directly controls 24V actuators on fan coil unit valves (Belimo LM24 motorised valve, via 0-10V output from KNX module). MDT WTC-0802.01 fan coil controller combines all fan coil control functions (fan speed, chilled water valve, heating valve, temperature setpoint) in a single KNX device — no BACnet gateway needed. For AHU (air handling units) in mid-sized buildings: Siemens ALG thermostatic controller with BACnet MS/TP can be read by a KNX-BACnet gateway (Intesis IN701) and exposed as KNX group addresses to the ETS6 project. This works but adds gateway cost and complexity.

When BACnet cannot be replaced by KNX

Mechanical HVAC plants — chillers, boilers, AHUs above 5,000 CFM — are almost universally programmed in proprietary BACnet controller software (Siemens DESIGO PX, Honeywell Niagara, Schneider EcoStruxure). These controllers provide sophisticated PID loops, fault management, and energy optimisation that ETS6 logic blocks cannot replicate. Attempting to control large HVAC plant via KNX would require custom programming and would lose all the pre-built controller logic. Correct approach: let BACnet controllers manage HVAC plant, expose status and setpoints to BMS, integrate KNX room setpoint telegrams as BACnet Analog Value objects via gateway.

Specification checklist

Include KNX when: field-level lighting control, blind/curtain automation, door bell and intercom integration, room-by-room occupancy sensing, access control dry-contact monitoring, individual switch plate design matters to architect. Include BACnet when: centralised HVAC plant (chiller, boiler, AHU), BMS platform required for FM team, energy reporting to ISO 50001, multi-brand HVAC controller integration, fire alarm panel integration (some modern fire panels use BACnet). Both when: commercial building above 2,000m² where both field device control and HVAC management are required. Budget impact: BACnet gateway adds €2,000-5,000 per gateway device; Desigo CC/EcoStruxure BMS license €15,000-50,000 for typical commercial building; factor into M&E specification before project stage.