DECT (deprecated)

The DECT protocol adapter enables you to control all kinds of devices that support the DECT protocol.

Protocol Information

The Home Device Manager (HDM) provides an abstraction layer (a common interface) for controlling home devices using different communication protocols.

Protocol Name

For integration with the Home Device Manager, the DECT Module offers a protocol adapter, named DECT, which exports DECT devices as devices made of HDM device class objects. Each device class object implements a specific device class and owns specific properties. Devices can be controlled by changing the values of their properties or by executing operations on them.

The protocol adapter represents DECT devices as implementing one of the following device classes:

DECT Network Controller (com.prosyst.mbs.services.dect.adapter.deviceclasses.DectNetworkController)
Binary Switch (com.prosyst.mbs.services.hdm.deviceclasses.BinarySwitch)
Binary Sensor (com.prosyst.mbs.services.hdm.deviceclasses.BinarySensor)
Multi-Level Sensor (com.prosyst.mbs.services.hdm.deviceclasses.MultiLevelSensor)
Tamper Alert (com.prosyst.mbs.services.dect.adapter.deviceclasses.DectTamperAlert)
WakeUp (com.prosyst.mbs.services.hdm.deviceclasses.WakeUp)

More information about the device abstraction is available in the Home Device Manager documentation.

Protocol Operations

The DECT protocol adapter supports two types of device administration operations - "search" and "remove parent only".

To add devices to a DECT Network Controller (Base Station), simply put the Base Station in "pairing" mode and then perform directly on the physical device the necessary operation, as specified in the user manual for this device.

The "remove parent only" support ensures that you cannot remove the home devices created for sub-devices of a physical device.

Protocol Properties

The created DECT home devices have the following properties related to the nature of the DECT protocol.

Property Name	Access	Resolution	Description
EMC	R	Optional	Specifies Equipment Manufacturer Code.
HANDSET_TYPE	R	Optional	Specifies the Handset Type.
IPUI	R	Optional	Specifies the International Portable User Identifier (IPUI)
actual.response.time	R	Optional	Specifies the actual paging interval, in milliseconds, to be used by a "pageable" device (Paging Interval).
application.version	R	Optional	Specifies the software version of the application running in the device.
controller.id	R	Optional	Specifies the ID of the Dect controller.
controller.version	R	Optional	Specifies the Version of the used software.
device.enable	R	Optional	Specifies if all units in a device are enabled/disabled.
extra.capabilities	R	Optional	Specifies the paging and broadcast capabilities of the device.
friendly.name	R	Optional	Specifies meaningful names for a device’s units.
hf.core.release.version	R	Optional	Specifies the version of the HAN-FUN release implemented on the device. A HF release encompasses a specific version of the HF Protocol Specification and of the HF Core Services and Interfaces. From all the HF Core services, this version covers only the following ones: Device Management, Device Information, Attribute Reporting, Bind Management, Group Management.
interface.release.version	R	Optional	Specifies the version of the HF Interface Release implemented on the device.
location	R	Optional	Specifies the location of a device in a house.
minimum.sleep.time	R	Optional	Specifies the minimum sleeping period, in milliseconds, a device supports.
profile.release.version	R	Optional	Specifies the version of the HF Profile Release implemented on the device.
hardware.version	R	Optional	Specifies the hardware version of the device.
manufacture.name	R	Optional	Specifies device’s manufacturer

You can retrieve the values of these properties for each device by using the getProperties or getPropertyMetadata method of the corresponding HomeDevice object.

Polling

The DECT protocol adapter does not execute polling of devices.

DECT to HDM Mapping

For each physical DECT device an HDM home device is created.

Device Type	Device Class
On Off	Binary Switch
Alert	Binary Sensor
Alert	Multi-level Sensor
Tamper Alert	DectTamperAlert (based on DECT functionality)
Keep Alive	Wake Up

DECT Network Controller

The DECT protocol adapter represents a DECT controller as an object of type com.prosyst.mbs.services.dect.adapter.deviceclasses.DectNetworkController, which extends com.prosyst.mbs.services.hdm.deviceclasses.NetworkControllerExt.

Wake Up

Some devices support keep alive messages. For those devices the protocol adapter provides a Wake Up (com.prosyst.mbs.services.hdm.deviceclasses.WakeUp) device class object. This object has two properties:

awake - a property which specifies if the system needs to maintain communication with a device. Its value is always com.prosyst.mbs.services.hdm.deviceclasses.WakeUp.EVENT_AWAKE which indicates that the respective device should periodically send keep alive messages for the system to maintain communication with this device and keep its status to HomeDevice.STATUS_ONLINE.
wakeUpInterval - specifies the time period for which a keep alive message is valid. If for 1.50 * wakeUpInterval time no keep alive message is received from a device, its status is set to HomeDevice.STATUS_OFFLINE and the device is no longer available.