HDM Zones

This functionality has not been fully replaced and supported in Device Access (DA). The FIM groups (implementing the interface com.prosyst.mbs.services.fim.groups.Group can be used for grouping a set of devices or items. But as a functional restriction, they do not support invoking operations on the Functional Items in the group, or setting multiple properties. Additional limitation is that is no predefined system group.

HDM Async Utility

This functionality has no replacement and is not supported in DA.

HDM Hooks

This functionality has no replacement and is not supported in DA.

HDM Multicast Handlers

This functionality has no replacement and is not supported in DA. The MulticastHandler functionality is integrated only with the old HDM API - Home Devices and Device Class Objects.

HDM JSON RPC

There is no JSON-RPC API for the DA APIs. DA provides a REST-based API for remote calls that replaces the JSON-RPC API. The bundle with symbolic name com.prosyst.mbs.da.rest.api provides the DA specific JAX-RS mappings of the M2M Device Management Management REST API.

HDM Home Device Configuration

DA offers a new Device Configuration Model and an abstraction that target configuring of devices and device items by a unified API & SPI for providing Device and Device Items configurations. A detailed overview and guide for Device Configuration feature of DA can be found in the DA Developer Guide > Device Configuration >Overview.

Backup/Restore

DA supports the backup/restore functionality based on the Backup Admin API without any changes from HDM, by registering a custom BackupProvider service that handles and performs the actual backup/restore processes.

During runtime, or upon Gateway /DA startup, any existing HDM backups can be successfully applied, converted transparently in the new internal HDM structure and migrated to DA. After restore, the devices loaded from the database, if enabled, will be visible via both APIs - DA API & HDM API - with retained identifiers but with certain restrictions on the representation by the DA API.

In HDM the Home Device functionalities come from the protocol adapter represented as a device class implementation, and they are not compatible with FIM as functional items - therefore, no device items will be available via the DA API.

Also, some of the HDM properties, such as type, vendor and version are not mapped to Device properties. The full HDM parent-child structure including Device Class Objects and processes, if enabled, will be visible only through the HDM API.

Backup/Restore of the HDM module to the DA module should work seamlessly with the devices in the database visible as Devices via the DA API when loaded. This is given that there are no other unexpected issues with any protocol adapter implementation or dependent modules, or the database is not corrupted, invalid or altered incorrectly.