KNX is the worldwide STANDARD for all applications in home and building control, ranging from lighting and shutter control to various security systems, heating, ventilation, air conditioning, monitoring, alarming, water control, energy management, smart metering as well as household appliances, audio/video and lots more. KNX is the worldwide standard for home and building control with a single, manufacturer independent design and commissioning tool (ETS), with a complete set of supported communication media (TP, PL, RF and IP) as well as a complete set of supported configuration modes (system and easy mode). KNX is approved as a European (CENELEC EN 50090 and CEN EN 13321-1) and an International standard (ISO/IEC 14543-3). KNX products made by different manufacturers can be combined – the KNX trademark logo guarantees their interworking and interoperability.
KNX driver for ComfortClick bOS enables whole building integration, control and automation (usage examples). The driver is compatible with IP, USB or serial KNX communication interfaces manufactured by any KNX certified manufacturer. It supports simple importing of ETS projects and fast creation of beautiful KNX visualization themes with unlimited number of visualization panels. The KNX functionality can be upgraded with bOS logical operations and tasks. Additional bOS supported devices can be integrated with the KNX system to create a true smart house experience.
KNX software (driver) supports communication with EIB/KNX installations over IP, USB and serial adapters. Before creating the bOS configuration, configure the KNX system with ETS or contact your installer to get a Group Address export file (.esf or .xml (ETS 5)).
Picture 1: KNX node
Driver supports the following connection types:
It is necessary to ensure that the KNX IP interface is on the same network as the server machine. It is recommended that the static IP address is set on the interface. KNX IP interfaces sometimes require a second KNX interface to program the static IP.
Under the KNX node the following subnodes (representing different KNX data types) can be added:
The data point types are described in the KNX Interworking Document.
Each data type node has the settings shown on picture below.
Picture 2: KNX data type node settings
Address setting is the group address. Currently only three level group addresses are supported (e.g. 0/0/0). Status Address is used for receiving object values. If Status Address is set, values received on Address are ignored. Multiple status addresses can be entered, separated by comma. Communication flags and cyclical sending can be used for each data point. Multiple actions can be set when device is connected (read of write to address).
Under KNX IP you can find your IP address, port and your NAT (Network Address Translation). If you don't know your KNX IP address, you can use Discover function, which will search for your KNX device on your local network, find its IP and use it in your configuration.
Picture 3: Discover function
Datapoint definitions can be imported from a Konnex OPC Server Export file (.esf) or Group Address export file (.xml (ETS 5)) by clicking on the Import from ETS button.
Picture 4: KNX data type node settings
If your esf file contains illegal characters it is advisable to fix them in ETS and make another export.
Picture 5: Illegal characters
In the next step we check the Data Types. The unknown data types must be selected manually or it will not be imported. When importing the ETS database we sometimes import data that we do not need.
NOTE: To edit multiple data types (same size), left click and drag up/down to select, right click on the selection and set the desired data type.
Staus addresses should also be set for every control group address, to save time in later configuration.
Picture 6: Import form multi-select
In next step value templates should be selected in order to use them in scenes, schedules, themes... They are used to generate the control buttons for scene settings and automatic control creation.
Picture 7: Device settings
Lights or relay outputs are usually controlled with the following data points:
You can use "Switch status" optionally. The Address from the "Switch status" should be copied to the Status address of the "Switch on/off" node. This way we have a single node (and single button) to control the output with status feedback. Multiple status addresses can be used if necessary.
Dimmable lights are usually controlled with the following data points:
The control in percentage is easier to operate and automate. Use "Brightness value" object for dimming control if this is supported by the KNX module. You must import the "Brightness value" and "Brightness status" objects from the ETS. The Address from the "Brightness status" should be copied to the Status address of the "Brightness value" node. This way we have a single node (and single button) to control the dimmer with status feedback.
Some modules don't support "Brightness value" control. Alternatively you can also control dimming with the "Switch on/off" and "Relative dimming" data points directly. This way you need to create 3 buttons to control the shades from theme panels:
Shades are usually controlled with the following data points:
The control in percentage is easier to operate and automate. Use "Move to position" object for blinds control if this is supported by the KNX module. You must import the "Move to position" and "Status position" objects from the ETS. The Address from the "Status position" should be copied to the Status address of the "Move to position" node. This way we have a single node (and single button) to control the shades with status feedback.
Some modules don't support "Move to position" control. Alternatively you can also control blinds with the "Move up/down" data points directly. This way you need to create 3 buttons to control the shades from theme panels.
Different modes (e.g. thermostat mode, heat pump operation mode...) or scenes are usually represented with a number:
NOTE: Value type should be set to *DPT_Value_1_Ucount, which means there will be no conversion of data (0-255).*