Building Automation#Johnson Controls#Metasys#BACnet#BMS

Johnson Controls Metasys: KNX Building Integration via BACnet

SmartMāja Engineering Team·2027-07-30·8 min read

Metasys in European Commercial Buildings

Johnson Controls Metasys is a large-scale BMS (Building Management System) widely deployed in European hospitals, airports, universities, and office complexes. KNX is commonly used for tenant-level controls in the same buildings, creating a need for reliable KNX/Metasys integration.

Integration Architecture

The standard integration architecture uses LOYTEC LGATE-950 or LOYTEC L-INX Automation Server as the KNX/BACnet bridge. The Metasys Network Automation Engine (NAE) communicates via BACnet/IP on the building IP network. LOYTEC LGATE-950 connects to KNX TP bus and presents itself as a BACnet/IP device on the same network. Metasys NAE discovers the LGATE via BACnet Device Discovery (Who-Is/I-Am broadcast).

Metasys SCT Configuration

In Metasys SCT (System Configuration Tool), add the LOYTEC LGATE as a BACnet/IP device. Metasys will enumerate the LGATE BACnet objects, which represent KNX group objects. Map each BACnet object to a Metasys point definition. Example: KNX room temperature DPT 9.001 becomes BACnet Analog Input AI:5 on the LGATE, which maps to Metasys point ROOM_TEMP_01.

HVAC Control Integration

Metasys Global Control Programs (GCP) can use KNX-sourced room temperature points as inputs to AHU (Air Handling Unit) control sequences. This allows the Metasys central HVAC control to respond to actual room temperatures measured by KNX room controllers distributed throughout the building.

KNX Lighting via Metasys

Metasys controls large-zone DALI lighting through KNX: Metasys time schedule triggers a scene recall command through BACnet to the LGATE, which forwards it as a KNX telegram to a DALI KNX gateway, which then controls the DALI luminaires. This chain enables centrally scheduled lighting control without a separate lighting BMS.

BACnet MS/TP Field Level

Many Metasys field controllers (FEC) use BACnet MS/TP (RS485) at the field level. The NAE provides BACnet/IP routing from MS/TP to Ethernet. KNX integration is always at the NAE/BACnet/IP level, not the MS/TP level — the LGATE connects to the same IP network as the NAE.

Metasys REST API Alternative

Metasys offers a REST API for third-party integration. For KNX projects where a direct HTTP bridge is preferred over BACnet, the Enertex EibPC can call the Metasys REST API to read and write points. Authentication uses OAuth2 bearer tokens with 15-minute expiry and automatic refresh — configure the EibPC HTTP client with token refresh logic.

Multi-Tenant Building Strategy

In multi-tenant buildings, KNX handles tenant-level controls (individual office lighting, room HVAC setpoints, blind control) while Metasys manages building-level systems (AHU, chiller, boiler plant). The KNX/BACnet bridge enables tenant energy sub-metering data to flow into the Metasys energy reporting dashboard, providing building-wide energy transparency.

Need help with your KNX or DALI project?

Our certified engineers can discuss panel design, commissioning, integrations and project-specific edge cases. Free initial consultation.

Contact our engineers →
Ielādējas...
Uz augšu