The KNX protocol is the oldest and most widely deployed open standard for building automation, present in more than 190 countries and backed by close to 500 manufacturers. If you are designing a smart building — a hotel, an office block or an industrial facility — the KNX standard lets you bring lighting, heating, blinds, air conditioning and access control together into one coherent control system that is not tied to a single vendor.
In short: the KNX protocol (ISO/IEC 14543-3) is a decentralised fieldbus in which every device carries its own intelligence and communicates through bus telegrams over twisted pair, radio or IP. It is the backbone of a smart building that runs locally and, through a KNX IoT gateway, connects to the cloud and the wider IoT world.
What is the KNX protocol?
The KNX protocol is an open, standardised communication standard for home and building automation, defined in ISO/IEC 14543-3, EN 50090 and EN 13321-1. It is governed by the KNX Association, headquartered in Brussels, and more than 8,000 product groups already carry its interoperability certificate.
Decentralisation is the defining feature: a classic KNX installation has no central controller whose failure would bring the building to a standstill. Every sensor, push button and actuator is a self-contained device with its own microcontroller that sends and receives telegrams on a shared bus. Commissioning is handled by a single, manufacturer-independent tool — ETS (Engineering Tool Software), currently in its ETS6 release.
How does the KNX bus and its topology work?
The KNX bus is a two-wire twisted pair (TP1) powered at 29 V DC that carries both device power and data at 9,600 bit/s. Access to the medium is arbitrated by CSMA/CA, so devices share the line without collisions and every telegram is acknowledged.
The topology is hierarchical. Its foundation is the line, which serves up to 64 devices and can be extended to 255 with repeaters. Up to 15 lines are joined into an area by line couplers, and up to 15 areas are tied together by the main backbone. In practice a single installation can address more than 58,000 devices — far more than even a large hotel will ever need. The individual address takes the form area.line.device (for example 1.1.5), while logical functions are linked by group addresses (for example 1/2/3), which is what allows one push button to drive any group of luminaires.
Transmission media: TP, RF, Powerline and IP
The KNX protocol defines several physical media that can be mixed within one installation using the appropriate couplers. The choice of medium depends on whether the building is new or being retrofitted.
- KNX TP (twisted pair) — the bus cable itself, the most reliable choice for new buildings; 9,600 bit/s with 29 V DC power supplied over the bus.
- KNX RF — radio communication in the 868.3 MHz band, ideal for retrofits without chasing walls; the KNX RF Multi variant improves immunity to interference.
- KNX PL110 — transmission over the existing 230 V mains (110 kHz), used less frequently and only in selected retrofit projects.
- KNXnet/IP — tunnelling and routing of telegrams over Ethernet/IP (UDP, port 3671), linking bus lines and opening the door to IT and cloud integration.
KNX IoT — the bridge between the building and the cloud
KNX IoT is a set of modern interfaces that connect the classic bus to the Internet of Things and to cloud services. It is the standard's answer to the demand for remote monitoring, analytics and app-based control.
At the lowest level, the KNX IoT Point API uses the lightweight CoAP protocol over IPv6 secured with OSCORE, which turns KNX devices into native nodes of an IP network. The KNX IoT 3rd Party API, in turn, exposes data as JSON over REST and WebSocket, which makes integration with cloud platforms far simpler. In a typical deployment, an IoT gateway with a well-considered architecture maps KNX group addresses onto topics of the MQTT protocol and forwards telemetry to the backend, where it feeds cloud infrastructure and analytics dashboards.
Where to use the KNX protocol? Hotels, offices and industry
KNX proves its worth wherever several building subsystems have to be integrated behind a single interface and the installation is expected to last for decades. It delivers the greatest value in properties with a large number of identical rooms.
In hospitality, KNX is the heart of the guest room management system (GRMS): it controls lighting scenes, room temperature, blinds and do-not-disturb signalling, and through integration with the PMS system (Opera, Mews, Apaleo) it automatically switches the room into economy mode after check-out. It increasingly works alongside modern access control, where a guest check-in triggers the welcome scene. In industry and office buildings, KNX ties into supervisory systems through the BACnet protocol and into machine automation through Modbus, completing the industrial IoT picture.
Security: what is KNX Secure?
KNX Secure is a set of cryptographic mechanisms that protect an installation against eavesdropping and telegram manipulation. Since the bus controls access and heating, security is not optional.
The standard covers two complementary mechanisms. KNX Data Secure authenticates and encrypts individual telegrams with AES-128 CCM, protecting communication at device level. KNX IP Secure wraps KNXnet/IP traffic in an encrypted AES-128 tunnel, securing transmission between buildings and to the cloud. Both are configured in ETS and their keys are delivered with the project file — a practical layer of defence worth enabling in every deployment that is reachable from the network.
Frequently asked questions (FAQ)
How does the KNX protocol differ from BACnet?
KNX operates at field level — it directly controls lighting, blinds and heating inside the room. BACnet works at the building management (BMS) layer and integrates entire subsystems. In practice the two standards work together through KNX/BACnet gateways and complement each other within a single property.
Does the KNX protocol require a cloud connection?
No. Classic KNX runs locally on the TP bus and works without internet access, which improves reliability and privacy. Cloud connectivity is added optionally through a KNX IoT or KNXnet/IP gateway, delivering remote monitoring, analytics and control from a mobile app.
How many devices does a single KNX installation support?
A single KNX TP line supports up to 64 devices, or up to 255 with repeaters. Thanks to the area topology (15 areas of 15 lines each), one installation addresses more than 58,000 devices, which covers even large hotels and office buildings with room to spare.
Summary and key takeaways
KNX is a proven, open foundation for the smart building: decentralised, vendor-independent and scalable from a single flat to a hotel complex. The classic TP bus delivers reliability without a network connection, RF and IP media provide flexibility in retrofits, and KNX IoT closes the gap to the cloud and the IoT ecosystem. What matters most is designing the topology correctly, enabling KNX Secure and building a well-considered bridge to the backend.
FSS Technology combines hardware, firmware and cloud expertise to design gateways, integrations and dashboards for KNX installations — from a single hotel to an entire property portfolio. Want to connect KNX with the cloud and your supervisory systems? Explore our connected device development and system integration services.