|
|
|
|
|
The KNX protocol adapter enables you to control all kinds of devices that support the Wireless M-Bus protocol.
Protocol Information
The Protocol Information necessary for management of KNX networks through the abstraction layer provided by the Home Device Manager (HDM) API.
Protocol Name
HDM allows for controlling home networks of devices through a specified protocol adapter. To be able to manage KNX networks via the Home Device Manager you need to select the protocol adapter registered under the name KNX.
Protocol Operations
The KNX protocol adapter supports the following device administration operations: "remove parent only" and "ADD". The "remove parent only" ensures that you cannot remove directly the home devices created for the endpoints of a joined physical device. You can do this only by removing their parent home device.
KNX devices are added to HDM via a Web interface, which is provided by the KNX HDM Adapter.
Protocol Properties
The device properties related to the underlying KNX protocol adapter are described in the table below:
Property |
Access |
Description |
Resolution |
|---|---|---|---|
address |
Readable |
The physical address of the device |
Optional |
applicationProgram |
Readable |
The device's model, according to its manufacturer. |
Optional |
applicationProgramName |
Readable |
The device's model name, according to its manufacturer. |
Optional |
You can retrieve the values of these properties for each device by using the getProperties or getPropertyMetadata method of the corresponding HomeDevice object.
Polling
If the physical address of the KNX device is configured (either automatically by importing the ETS project through the KNX config wizard, or manually when adding the KNX device), the Home device manager polls for changes in the KNX HDM device ONLINE/OFFLINE status. The polling interval can be configured with the system property mbssh.hdm.knx.pingInterval, the default value is 6000.
KNX-to-HDM Mapping
Structure of the KNX to HDM Mapping.
For each physical KNX device a HomeDevice object is created. For each end device there is a child HomeDevice attached. The end device has DeviceClassObjects with properties which correspond to the device's Datapoints.
The KNX protocol adapter does not provide direct mapping of KNX devices and HDM interfaces, so you must attach the DeviceClassObjects to the KNX devices in the network and specify the Datapoint which corresponds to each DeviceClassObject property manually.
The KNX protocol supports the following Device Class Object interfaces: