The KNX IoT Point API in plain language

The KNX Association published the KNX IoT Point API to extend the protocol natively over IPv6 without abandoning the data-point semantics every KNX engineer already knows. Devices that implement KNX IoT speak CoAP (a lightweight HTTP-like protocol designed for constrained devices) and use OSCORE for end-to-end encryption.

The big idea: the same temperature setpoint that lives at group address 3/2/15 in a classic KNX project can be expressed as a JSON resource at a URL on a KNX IoT device. A cloud platform, a building information dashboard, or a third-party app can read or write it through standard REST-like calls without needing a vendor gateway.

For the day-to-day installer, KNX IoT does not change ETS workflows yet. Most projects today still run on twisted pair (TP) and IP, and KNX IoT devices are emerging slowly. Where it already shines is in two scenarios. First, building portfolios where a central platform aggregates dozens of small KNX systems through a thin IPv6 connection. Second, IoT pilots where a customer wants to integrate KNX with a public cloud service like AWS IoT or Azure Digital Twins without bespoke middleware.

If you commission a KNX IoT device, expect a slightly different onboarding flow. Instead of a physical address, you bind the device by its KNX IoT credentials, and OSCORE keys are exchanged during commissioning. ETS6 supports this through the IoT Point API option, but the smoothest experience today is to combine ETS for classic devices and a vendor-supplied IoT commissioning tool for the new ones, until tooling consolidates.