KNX

KNX logo

KNX is the worldwide open standard for all applications in home and building control – lighting, shades, HVAC, energy consumption, irrigation and more.

Website: knx.org

About

About

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.


Help

KNX Device

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)).

KNX

Picture 1: KNX node

Driver supports the following connection types:

  • KNX IP
  • KNXnet / IP (Falcon)
  • KNXnet / IP Routing (Falcon)
  • USB (Falcon)
  • EIBLib / IP (Falcon)
  • Serial FT1.2

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.

Data Points

Under the KNX node the following subnodes (representing different KNX data types) can be added:

  • DPT 1 Bit Controlled
  • DPT 2 Ochtet Float
  • DPT 2 Ochtet Signed
  • DPT 2 Ochtet Unsigned
  • DPT 3 Bit Controlled
  • DPT 4 Ochtet Float
  • DPT 4 Ochtet Signed
  • DPT 4 Ochtet Unsigned
  • DPT 8 Bit Signed
  • DPT 8 Bit Unsigned
  • DPT Boolean
  • DPT Character Set
  • DPT Date
  • DPT String
  • DPT Time
  • KNX: Used for data point node grouping.

The data point types are described in the KNX Interworking Document.

Each data type node has the settings shown on picture below.

KNX GroupAddress

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).

KNX IP

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.

Discover

Picture 3: Discover function

Importing database from ETS

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.

KNX Import

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.

Import

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.

KNX ImportFormMulti

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.

KNX TemplateSelection

Picture 7: Device settings

Switching lights

Lights or relay outputs are usually controlled with the following data points:

  • Switch on/off: DPTBoolean
  • Switch status: DPTBoolean

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.

Dimming lights

Dimmable lights are usually controlled with the following data points:

  • Switch on/off: DPTBoolean
  • Relative dimming: 3BitControlled
  • Brightness value: DPT8BitUnsigned (0-100%)
  • Brightness status: DPT8BitUnsigned (0-100%)

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:

  • On/off button: Toggle button linked to "Switch on/off.Value".
  • Dimm down button: MouseDownButton button linked to "Relative dimming.FalseToggle"
  • Dimm up button: MouseDownButton button linked to "Relative dimming.TrueToggle"

Controlling shades

Shades are usually controlled with the following data points:

  • Move up/down: DPTBoolean
  • Stop up/down: DPTBoolean
  • Move to position: DPT8BitUnsigned, Value Type = DPT_Scaling (0-100%)
  • Status position: DPT8BitUnsigned, Value Type = DPT_Scaling (0-100%)

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.

  • Stop button: SetButton linked to "Stop up/down.Value", SetButtonValue = false
  • Down button: SetButton linked to "Move up/down.Value", SetButtonValue = true
  • Up button: SetButton linked to "Move up/down.Value", SetButtonValue = false

Controlling modes and scenes

Different modes (e.g. thermostat mode, heat pump operation mode...) or scenes are usually represented with a number:

  • Thermostat Mode: DPT8BitUnsigned, Value Type = DPTValue1_Ucount (0-255)
  • Call scene: DPT8BitUnsigned, Value Type = DPTValue1_Ucount (0-255)

NOTE: Value type should be set to *DPT_Value_1_Ucount, which means there will be no conversion of data (0-255).*