Skip to content

Stack Features and Versions

Stack Version (GitLab Tag) EITT Certification Template : Test Specification (8/10/5) Point API Specification (3/10/5) ETS : Manufacturer Tool Version Comments
1.0.0 (available) V39 : 1.1.1 1.1.0 >= 6.4 : >= 6.4 See CHANGELOG in knx-iot-point-api-stack
1.1.0 (available) V40 : 1.1.1 1.4.0 >= 6.4 : >= 6.4 See CHANGELOG in knx-iot-point-api-stack
1.2.0 (12/2026) TBD : TBD 1.5.0 (voting cycle Q4/2026) TBD FreeRTOS (main feature, other features see below)
1.3.0 (first half 2027) TBD : TBD 1.x.0 TBD C-SDK (main feature, other features see below)
1.4.0 (2nd half 2027) TBD : TBD 1.x.0 TBD TLS (main feature, other features see below)

Info

All dates are tentative and subject to change.

Feature Overview

  • ✅ Fully implemented
  • ❌ Not implemented (yet)

KNX IoT End Device Features

Devices, running an application that is capable of sending/receiving messages (for example, a push button device). The stack implements these features.

Category1 Feature Support Comments
Discovery DNS-SD / mDNS, CoAP Resource Discovery ✅ -
Device Interface Object Device Commands ✅ -
Device Resources ✅ -
Application Program (Resources & Load State Machine) ✅ -
Point (GET, PUT, POST, DELETE) ✅ -
Security PASE / SPAKE2 ✅ -
OSCORE ✅ -
Access Control Resources ✅ -
Access Scopes ✅ -
TLS (with X.509 certificates) ❌ stack version 1.4.0, is an optional feature
Functional Blocks Functional Block Resources ✅ -
Point Access Point Read / Write ✅ -
Publish & Subscribe ✅ -
Datapoint Metadata ✅ -
Subscription Resources ✅ -
Z8 Extension ✅ -
Group Communication Basics (Services) ✅ -
Tables ✅ -
Patterns (unicast/ multicast) ✅ -
Optimized IPv6 Multicast Group IDs subscription ❌ stack version 1.3.0, ULA/IANA style multicast addresses
Software Update Resources ✅ -
Transfer ✅ -
Modes ✅ -
CoAP Application Protocol Protocol ✅ -
Formats ✅ -
Response Codes ✅ -
Rate Limitation ✅ -
IPv6 Support ✅ -

MaC Device Features

Client-side functionality to configure a KNX IoT End Device (for example, a tool to scan/download devices). The KNX IoT project offers two implementations:

This may change if either implementation supports more features, as listed below.

Category Feature Python C Comments
Discovery DNS-SD / mDNS ✅ ❌ (1.3.0) -
CoAP Resource Discovery ✅ ❌ (1.3.0) -
Device Factory Reset (with optional erase-code) ✅ ❌ (1.3.0) -
Restart Application ❌ ❌ (1.3.0) Python update planned
Programming Mode ✅ ❌ (1.3.0) -
Device Resources ✅ ❌ (1.3.0) scan/list available resources
Tables ✅ ❌ (1.3.0) read/write tables (in case of 's-mode' configuration)
Security PASE / SPAKE2+ (key exchange and PASE handshake) ✅ ❌ (1.3.0) -
Barcode-based onboarding ✅ ❌ ISO 15418 DMC/QR barcode decoding for device passwords
ETS credential import (OSCORE credentials) ✅ ❌ -
Access Control Resources ✅ ❌ (1.3.0) read/write access (tool key) tokens
Credential Creation ❌ ❌ (1.3.0) tool key, group keys, Python update planned
Point Access Point Read / Write ✅ ❌ (1.3.0) 's-mode' runtime group communication, read/write values
Publish & Subscribe ✅ ❌ 's-mode' pub/sub for monitoring/ controller notification
Storage Manage Configuration Data ✅ ❌ read in by a MaC generated configuration data and process them (download the devices)
Secure Credential Storage on Client ❌ ❌ store configured device project data locally (secure keys, tables, and other)
Software Update Firmware Update (SWU) ✅ ❌ PUSH-mode firmware update (.knxfwp packages) over OSCORE

Platform Support

Platforms Usage Support Comments
Linux (POSIX) own development w/o embedded platform from below ✅ -
Windows fast (GUI) demo development ✅ -
Zephyr embedded platform ✅ -
FreeRTOS2 embedded platform ✅ NXP, available on NXP Hub
FreeRTOS2 embedded platform ❌ ESP32, version 1.2.0

Application Demo Features

The demo applications implement these features.

Category Usage Support Comments
HEMS3 (s-mode) configuration with extensive MaC (ETS) ✅ Python client demo code
HEMS3 (pub/sub) configuration with simplified MaC (Handheld) ❌ Python client demo code, Q4/2026
HEMS (S2 interface) EN 50491-12-2 ❌ Python client demo code, Q4/2026

  1. The section 'KNX IoT Device Profile' defines these categories, see Device Profile ↩

  2. In contrast to Zephyr each FreeRTOS port needs an individual (designed) hardware abstraction layer. ↩↩

  3. It is also planned to configure the HEMS demos with the C-code based SDK. ↩↩