Technology adapter is a special case of an application running on the hub responsible for managing external physical devices, otherwise called things. Their main role is to be an adapter between FIMP and a specific technology protocol while providing functionalities such as:
- pairing/including things into the network,
- unpairing/excluding things from the network,
- relaying commands to the things,
- relaying events from the things.
Adapters may use various communication technologies, such as Z-Wave and Zigbee wireless networks, direct connection through the local network or indirect through a third-party cloud provider.
All adapters should use their resource names as service names.
Exception! Due to the backwards compatibility, Z-Wave's service name is
zwave-ad(while its resource name iszw).
For description of how to add and remove things from the system see the thing management documentation.
For description of how to get connection status or update network see the network_management documentation.
An adapter may provide additional functionalities beyond what is defined in the FIMP protocol requirements. Good examples are advanced configuration or methods specific to the technology, and should be outlined in the adapter documentation. It is recommended that adapters follow guidelines for common interfaces when implementing such functionalities.