Knowledge Base

KNX is an international standard for smart building automation, commonly used in residential, commercial, and industrial projects.

It allows different systems, such as lighting, shading, heating,g cooling, ventilation, security, energy monitoring, and visualization, to communicate over a shared bus network. KNX is manufacturer-independent, meaning devices from different brands can work together in the same installation when configured correctly.

In ComfortClick, KNX devices are usually connected through KNX group addresses, which allow bOS to read values, send commands, monitor states, and create automation logic based on the building’s KNX installation.

Our KNX driver supports communication with KNX installations over IP, USB, and serial adapters, our Jigsaw KNX server also has a KNX gateway built-in which connects directly to the KNX bus for communication and integration so no additional KNX gateway is required.

Before creating the bOS configuration, configure the KNX system with ETS program or contact your installer to get a Group Address export file of your project. 

bOS supports all types of ETS projects (.knxproj, .xml or .esf file).

Table of contents

Supported Connection Types

Driver supports the following connection types:

• KNX IP

  • Used for connecting to a KNX installation through a KNX IP interface or KNX IP router over the local network. This is one of the most common connection methods for communicating with KNX devices from bOS.

• KNXnet / IP (Falcon)

  • Uses the KNX Falcon driver to connect through KNXnet/IP tunneling. This method is typically used when communicating with a KNX IP interface that supports tunneling connections.

• KNXnet / IP Routing (Falcon)

  • Uses the KNX Falcon driver with KNXnet/IP routing. This method is typically used with KNX IP routers and allows communication through multicast routing on the KNX network.

• USB (Falcon)

  • Uses the KNX Falcon driver to connect directly to the KNX bus through a KNX USB interface. This is useful when the server is physically connected to the KNX installation by USB.

• EIBLib / IP (Falcon)

  • Uses the Falcon driver to connect through the EIBLib/IP protocol. This option is mainly used for older or specific KNX IP interfaces that support EIBLib/IP communication.

• Serial FT1.2

  • Used for connecting to the KNX bus through a serial FT1.2 interface. This is typically used with older KNX serial adapters or legacy installations.

• Custom Jigsaw KNX driver

  • A ComfortClick-specific KNX driver designed for Jigsaw servers with integrated KNX connectivity. This driver allows the Jigsaw server to communicate directly with the KNX installation without requiring an additional external KNX interface.

Discovery

Running the Discovery function scans the local network for available KNX IP interfaces and ComfortClick Jigsaw devices.

When a device is found, its IP address is automatically detected and filled in, making the connection setup faster and easier.

This is useful when setting up a new KNX connection, checking available KNX interfaces on the network, or quickly identifying Jigsaw servers with integrated KNX support.

KNX Secure

bOS supports KNX Secure connections.

If KNX Secure is used in the installation, open the KNX device settings and configure the required KNX Secure parameters.

Make sure to enter the correct:

• Commissioning Password

• Authentication Code

These credentials must match the KNX Secure configuration of the device or interface. If the information is incorrect, bOS will not be able to communicate with the KNX installation securely.

Jigsaw KNX Secure

KNX secure is also available on our Jigsaw servers. Instead of setting the KNX secure settings in the KNX node under the Devices, KNX secure settings are available in the Jigsaw node under General.

Commissioning password and authentication code can be set once KNX secure is enabled.

KNX Group Address

The Address setting defines the KNX group address used by the datapoint.

bOS supports both standard three-level group addresses and free group addresses.

Examples:

• Three-level group address: 1/2/3

• Free group address: 755

Status Address

The Status Address is used for receiving object values and feedback from the KNX installation.

If a Status Address is configured, values received on the main Address are ignored. This is useful when the command address and feedback address are separated.

Multiple status addresses can be entered by separating them with commas.

Value Type

The Value Type defines the type of the group address, including its data type, unit, and visualization image.

This setting can be configured manually for each group address or assigned automatically when importing group addresses from ETS using the import wizard.

Many KNX group addresses can be configured with different Value Types, depending on the function they represent.

For example, similar group addresses may be used for:

• Temperature control

• Temperature shift

• Setpoint adjustment

• Status feedback

• Switching

• Dimming

• Shading control

Changing the Value Type changes how bOS interprets, sends, and receives values on the KNX bus, while still using the same group address.

This allows the same group address structure to be adapted to different device functions and ensures that values are handled correctly in logic, visualization, scenes, schedules, and automation.

Communication Flags and Cyclical Sending

Communication flags and cyclical sending can be configured individually for each datapoint.

These settings define how the datapoint communicates with the KNX bus, including reading, writing, and sending values cyclically.

Multiple actions can also be configured when the device connects, such as reading from or writing to the group address.

KNX Templates

Each KNX group address used in the visualization should have the correct Template assigned.

To set a template, select the KNX group address and open the Values tab. Templates define how the group address is controlled and displayed in the visualization, including the correct control type, image, colors, and behavior.

Using templates reduces the amount of manual work required when creating the visualization, because many visual and functional settings are prepared automatically.

Templates can also be assigned during the ETS import process by using the import wizard.

Additional template examples are available on the ComfortClick website. These examples are designed especially for KNX and commonly used device types, such as:

• Heating control

• Lighting control

• Shading control

The examples include predefined group addresses and ready-made visualization panels for easier integration.

Find the templates in our example page:
https://www.comfortclick.com/Support/ExampleDetails/KNXTemplates

After downloading an example, use the Import function to import it under the main KNX node. Then link the included group addresses with the matching group addresses from your project.

ETS Import

KNX datapoint definitions can be imported from an ETS group address export file by selecting Import from ETS.

Supported file formats include:

• .knxproj

• .xml

• .esf

After selecting the ETS project or export file, all group addresses from the project are displayed in the import wizard.

Most datapoints are detected and configured automatically. If a group address is not defined in ETS, it will also be shown as undefined in bOS.

Editing Data Types Before Import

Before importing, check that the correct data type is assigned to each group address.

Use the search bar at the top of the group address list to quickly find and configure specific group addresses before importing them into the configuration.

To match control group addresses with their status addresses, you can use one of the following methods:

• Manually copy and paste the status address into the correct group address

• Use the Paste to Status Address option

• Use the AI Matching feature

AI Matching

The AI Matching feature helps automatically match control group addresses with the correct status addresses, making the ETS import process faster and easier.

After all group address types are configured, select the group addresses that should be imported and click the AI Matching button in the top-right corner.

A loading bar will appear while AI Matching analyzes the selected group addresses and attempts to match each control address with its corresponding status address.

When the process is complete, review the matched addresses to make sure everything is correct. After checking the results, click Next to continue with the import process.

Selecting Templates

In the next step, select the correct templates for the imported group addresses.

Templates are used in scenes, schedules, themes, and automatic control creation. They help generate the correct control buttons and visual elements for the selected datapoints.

Group addresses can be identified by their name or address number.

Select the desired group address and assign the correct device type. This automatically sets the value type, image, and unit.

All imported values can still be changed later by selecting the group address manually and adjusting its settings.

Encrypted ETS Projects

If the ETS project uses KNX Secure with a commissioning password and authentication code, the .knxproj file may also be locked.

When importing a locked .knxproj file into bOS, a password prompt will appear.

Enter the correct ETS project password to unlock the file. After the password is accepted, the project is imported into bOS and the standard ETS import process continues.

After the import is complete, continue by checking group address types, assigning templates, matching status addresses, and confirming the imported datapoints.

KNX Visualization and Data Types

After the KNX group address and template are configured, bOS can automatically apply the correct visualization behavior when the group address is dragged into the Theme.

Depending on the selected template and value type, bOS can automatically adjust:

• Button behavior

• Control type

• Colors

• Images and icons

• Setpoint controls

• Status display

• ON/OFF states

• Other visualization properties

This makes visualization creation faster and easier, because the group address already contains the information needed for the correct control layout and behavior.

For example, a lighting template may create an ON/OFF or dimming button, while a heating template may create temperature setpoint controls and status display.

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. DPTBoolean data points and types can also be used to control other on/off devices, not just lights.

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 the "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"

Or you can also use one of our pre-built examples that are available in the KNX node. To add the dimming example into the project, select KNX node, and select Add function. Select KNX Folder and select Dimmer Up/down under Templates. This will create a dimming folder with group address options, icons, and already made visualisation option to use in the project.

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 the "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

Or you can also use one of our pre-built examples that are available in the KNX node. To add the shading example into the project, select KNX node, and select Add function. Select KNX Folder and select Shade Up/down under templates. This will create a shading folder with group address options, icons, and already made visualization options to use in the project.

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 = DPT_Value_1_Ucount (0-255)

Call scene: DPT8BitUnsigned, Value Type = DPT_Value_1_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).

ETS Remote Programming

ComfortClick allows ETS projects to be programmed remotely through a Jigsaw server.

This can be done using a remote connection method such as port forwarding or the ComfortClick Remote Access service.

With remote ETS programming, installers can access the KNX installation without being physically present on site. This is useful for making project changes, troubleshooting, updating group addresses, or adjusting KNX device parameters remotely.

When using this function, make sure the network connection is configured correctly and that remote access is secured according to the project and IT requirements.

The whole process of activation and the use of the tunneling service is explained in the video:

BOS allows us to remotely program our ETS project without the need for additional port forwarding and additional security risks using our Remote access service.

By default, the remote programming is disabled. In order to activate the remote programming and control (tunneling) select open the license information of your current server and click Buy button.

Once Buy is selected, connect to the correct Comfortclick account, select Tunnel service and click Buy at the bottom. Our sales team will contact you regarding the activation as the tunneling feature is billable.

Once tunneling is activated, Tunneling Service under license information will also show True.

Once tunneling is activated, select the main KNX node and use KNXIP as connection type. If Jigsaw KNX is being used, switch from KNXIP to Jigsaw as connection type. KNX tunneling is of course olso supported on our Jigsaw server.

Running the KNX Remote Programming function opens the tunneling server settings. Here we can start/stop the tunneling server and change the port that's being used for remote connection.

Once everything is set, select Start server and KNX tunneling is established.

NOTE: KNX IP gateway or Jigsaw is still required to connect and program the ETS project and devices. If KNX Secure is used for secure KNX connection, fill out the Commissioning password and Authentication code in the main KNX node.

In ETS, we can select our PC now for connection type and freely control the devices and even program then remotely, without the need of port-forwarding.