Overview of the DECT Technology

The DECT network has a star topology - one controller (called "Base Station" or "CMBS") communicates with end devices over the wireless DECT protocol.

• The controller is a hardware module integrated in the Gateway which runs the Bosch IoT Gateway Software runtime, or an external device that connects to it (via USB for example) and acts as a Base Station.
• The end devices are DECT-enabled sensors or actuators (e.g. different types of switches).

Components

OSGi Components

The DECT module consists of the following OSGi components - please see the list of Bundles for further information:

DECT Driver Bundle

Enables you to manage DECT devices by providing access to the DECT Base Station API.

DECT DA HDM Adapter Bundle

The DECT HDM Adapter bundle provides integration of the DECT module with the Device Access so that DECT devices can be managed through the generic mechanism provided by the DA Home Device Manager or Functional Item Management.

Non-OSGi Components

The OSGi Runtime connects to the Base Station over the DECT Native Remote API Component.

The DECT Native Remote API Component

The Native Remote API Component provides access to the DECT Base Station. It is an executable component which runs directly (natively) on the Gateway to which the Base Station is connected, and provides a JSON-RPC API. The Native Remote API Component communicates with the Base Station by calling its API methods (asynchronously). The result from the execution of these methods is sent to the OSGi Runtime through a TCP socket, over JSON-RPC. There are two versions of the Native Component - for Windows and for Linux OS. Refer to the Setup Guide for information how to install the native component.