Using the KNX Configuration Wizard

To be able to do that, you must first configure the KNX protocol adapter. The setup procedure consists of the following:

1. Import your KNX network's ETS project to HDM.
2. Map the KNX devices in it to HDM Devices and Device Classes.

Once it is finished, the information about the KNX devices and their mapping will be exported to ConfigTree where the HDM module can access it.

The KNX module comes with a Web interface that guides you through the procedure. To start it, go to your Web Admin Console and click on the KNX Config Tab.

Step 1: Importing an ETS 4 and 5 Project File

Import an ETS 4 or 5 project file (.knxproj) that contains the settings and configuration to the KNX network you are currently connected to.

1. Click Choose File.
2. Specify the location of your .knxproj file.
3. Click Submit. You will see all KNX devices from the project you imported.

If the information in the Devices tab is correct, Click Next.

Step 2: Selecting Devices

Select the devices that you would like to be able to control via the Home Device Manager.

By clicking on each device you will see a list of its Datapoints (check the Datapoints section in the Technology Overview) along with their descriptions, Group Addresses (check the Group Addresses section in the Technology Overview) that have been assigned to them (if any), flags, data types and priority.

Select the devices and when you are ready click Next.

Step 3: Selecting Datapoint Types

Go through the list of Datapoints of your devices and make sure that their types are set correctly:

1. Select a device to see its Datapoints.
2. Open the Data Type drop-down menu of each Datapoint. You will see a list of all data types (check the Datapoints section in the Technology Overview) that correspond to the size of the Datapoint (for example, if its size is one bit, you will only see boolean data types).
3. Select a data type for the Datapoint (refer to the documentation of the device).

   Do this for all devices and then Click Next.

Step 4: Creating Child Devices

A complex physical device that has more than one function, is typically represented in HDM as several devices in a parent-child relationship.

In order to manage a complex device via HDM, you must create child devices for it and distribute its properties among its children:

1. Select a complex KNX device.
2. Click the Add Device Button. The HDM will create a new child device for it.
3. Optionally, you can change the name of the child device by double-clicking on it.
4. Select the Datapoints which should be assigned to the new device.

   Do this for all devices and then click Next.

Step 5: Creating Device Class Object Mapping

The Home Device Manager works with universal interfaces for device management called Device Class Objects:

In order to manage your devices via HDM, you must attach one or more of these interfaces to each KNX device, registered in HDM and map the KNX Datapoints to Device Class Object properties.

Attaching Device Classes

To attach a Device Class to a KNX device:

1. Select a KNX device and click Add Device Class. You will see a list of the HDM Device Class Interfaces which have properties that are similar to the device's datapoints.
2. From the list of Device Classes, click on the one which best describes the device's functionality and capabilities. See below.

Mapping Datapoints to Device Class Object Operations

To map a Datapoint to a Device Class Object property:

1. Select the Device Class. You will see all its Device Class Object operations in the Label column of the Data Points table.
2. From the drop-down menus in the Data point Name column, select the data point, which you want to map to the operation.
3. From the Properties table you can edit some Device Class Object-specific mapping properties:

Mapping a KNX Sensor

The Home Device Manager contains generic interfaces that can be used for gathering data from different kinds of sensors:

Binary Sensor

The Binary Sensor interface represents a sensor with two possible states. To map a KNX device to a Binary Sensor:

• In the dp_sensor drop-down menu, select the datapoint which contains the sensor's data.
• In the value_off and value_on fields fill the values that the sensor sends when its state changes.

  The following example maps a simple light detecting device to a binary sensor.

Multi-Level Sensor

The Multi-Level Sensor interface can represent any sensor. To map a KNX device to a Multi-Level Sensor:

• In the dp_sensor drop-down menu, select the datapoint which contains the sensor's data.
• In the value_min and value_max fields, write the minimum and maximum value of the data.

Mapping a KNX Switch

The Home Device Manager contains generic interfaces that can be used for controlling different kinds of switches:

Binary Switch

The Binary Switch interface can represent any switch which is used for turning a device capability on or off. To map a KNX device to a Binary Switch:

• In the dp_switch drop-down menu, select the datapoint used for changing the state of the switch (the datapoint must have the WRITE flag enabled).
• In the dp_status drop-down menu, select the datapoint which the HDM will listen to update the state of the switch if it is changed manually.
• In the value_off and value_on fields enter the values that must be sent to the datapoint in order for its state to change.

The following example maps the Windalarm Datapoint to a binary switch which allows users to turn it off and on via HDM.

Multi-Level Switch

In most cases the Multi-Level Switch interface is used for dimmers. To map a KNX device to a Multi-Level Switch:

• In the dp_level drop-down menu select the datapoint used for directly changing the level of the switch.
• In the dp_up_down drop-down menu select the datapoint used for relative level change.
• In the level_min and level_max fields write the maximum and minimum switch levels.

The following example maps a dimmer device to a multi-level switch. The dimmer can also function as a normal On/Off switch. For this reason we added an additional Device Class (of type Binary Switch) to the device and mapped it to its on/off datapoint.

Key

The Key interface is used for controlling buttons that supports different functions on short and long press. To map a KNX device to a key:

• In the dp_long drop-down menu select the datapoint which corresponds to the button's long press.
• In the dp_short drop-down menu select the datapoint which corresponds to the button's short press.
• In the value_long_press and value_short_press fields, enter the values of the dp_long and dp_short datapoints that will be sent when the press operations are triggered.

The following example maps a two button device to two keys. The two child devices (button-up and button-down) control the same Datapoints, but they sent different values to them: the button-down sends "0" and button-up (as you can see in the screenshot), sends "1".

When you are ready, click Finish to end the setup procedure:

• The KNX devices will be imported and you can manage them via the Home Device Manager.
• The information about the KNX devices and their mapping will be saved in ConfigTree and you will be able to import and export it between different systems.