The largest development ecosystem for home and building solutions is ready to take off. With all the necessary components in place, it is now your chance to explore the extensive range of possibilities available in the KNX IoT environment. Please find below a selection of the most critical information:
KNX IoT specifications
KNX Specifications are, as usual, the cornerstone for any KNX development that aims certification. The following specifications are the foundation for KNX IoT:
- 3/10/1 KNX IoT introduction
- 3/10/2 KNX IoT Constants
- 3/10/3 KNX IoT Information Model
- 3/10/4 KNX IoT 3rd Party API (KNX IoT API Server)
- 3/10/5 KNX IoT Point API (KNX IoT Devices)
- 3/10/6 KNX IoT Router
Any KNX Member can access the full set of specifications via MyKNX - Resources section (log in required).
Certification is also part of the development workflow:
- KNX IoT API Server certification, you can watch a seminar recording here. It is worth mentioning that the test templates for KNX IoT API Servers are included in EITT from EITT v4.4.
- KNX IoT Device certification and KNX IoT Router certification, are currently available under the existing certification scheme (devices).
The KNX IoT ecosystem, in a nutshell
Confused with the various terms found within the KNX IoT domain? Let’s clarify them with one single image:
- KNX IoT Device (KNX IoT Point API device):
This is simply a device, with the peculiarity that it uses a new approach to fit into the IPv6 architecture. There is an open-source stack available for this type of device, as well as new modules from system component providers. Thread is one of the many network layers that KNX IoT Devices can work on, as long as they are IPv6-based. Is KNX certification possible? Yes.
- KNX IoT Router:
There are more than 8000 certified devices that are not KNX IoT, so if we want those devices to communicate with KNX IoT Devices, a KNX IoT Router is required. In the picture, the KNX IoT Router is embedded in a server from one of our startups, but it can be included in network devices, too. KNX certification possible? Yes.
- KNX IoT API Server.
This is a new solution in KNX that aims to improve the way data from KNX installations is presented to the world. It creates an abstraction layer between the KNX-specific knowledge and software development on the IT side, thanks to the KNX Information Model (KIM). It can make use of data of the ETS project offered in accordance with KIM and can be located on-premises or in the cloud without any constraints. Is KNX certification possible? Yes.
- KNX IoT API client (application).
This is the counterpart of the KNX IoT API Server. It includes application-based solutions that interact with the KNX installation through the KNX IoT API Server. It is not limited to software applications running on a computer, but it can also be a software client running on a device (such as the voice control unit shown in the image) or a service running on a cloud server (such as the Human Centric Lighting service offered by our startup Kumux). Is KNX certification possible? No.
- IPv6 Border Router
In this picture, KNX IoT devices are using Thread as a network layer; therefore, the IPv6 Border Router is required to connect to the IPv4 world and hence communicate with non-KNX IoT devices. Think of it as a network component, like a network router between the WAN and the LAN in every house or building. Is KNX certification possible? No.
KNX IoT tooling
Our tooling also needs some updates in order to deal with the KNX IoT landscape, or even new software tools. Below, the most important ones:
- ETS
Currently, in a beta version for KNX Members, the ETS6 will have the necessary capabilities to export KIM information (v6.1.1 already exports semantic info) as well as support of KNX IoT devices.
- Falcon
This is an essential component for ETS and it requires an update in order to communicate with IPv6 based devices.
- Manufacturer Tool
The main software to create the Product Description for KNX Devices is also required to handle KNX IoT Devices.
- EITT
As mentioned before, the v4.4 Beta is already capable of dealing with the certification of KNX IoT API Servers, available for every EITT licensee in MyKNX.
- Semantic Export ETS App
This is an ETS App that has been developed with the purpose of enabling the workflow between the ETS and the KNX IoT API Server. Eventually, it will not be required, since ETS will export the data natively without the need of a dedicated ETS App.
Development components for KNX IoT Devices
- Open Source stack (here).
- Modules from Cascoda (external link).
- Modules from Nordic Semiconductor (external link).
Development components for KNX IoT API servers
There are no dedicated physical components for KNX IoT API Servers, but there are some useful resources, which URL and login details can be found here:
- KNX IoT API Server Proof of Concept.
- Semantic Export ETS App.
KNX IoT events
- The KNX IoTech forum, which took place at the IoTSWC (February, 2023), was recorded and it is available here.
- We presented the full KNX IoT Development Landscape at ISE in Barcelona (February, 2023), and the first 2 KNX IoT Devices at ISH 2023 in Frankfurt (check the brochure here).
- KNX Association has been Gold Sponsor of the Thread Group Members Meeting in Philadelphia (April, 2023)
- The KNX IoT Startup Incubator, which startups are committed to develop KNX IoT based solutions, is being introduced to the USA market at IoT TECH EXPO in Santa Clara (May, 2023). Registration here.
- The full KNX ecosystem landscape was presented at Light + Building 2024 in Frankfurt (check the 3D digital booth here).
- KNX IoT devices (prototypes in pre-certification status) were presented at the IoTSWC 2024 in Barcelona (more info about ATOUCH KNX IoT keypads based on Cascoda's platform here).
- More upcoming events (e.g. KNX Tech & Business & Startup Forum in November 2024), please check KNX events page.