Device Cloud & API Integrations

IoT Connectors from Existing Device Clouds and Device APIs

A common situation is hardware is already connected to a 3rd party Device Cloud or has a published API and you wish to connect them to your Exosite Application (Eg. ExoSense or ExoHome).

For that purpose, the Exosite Murano platform supports a standard Cloud-To-Cloud integration. This integration is compatible with Exosite applications as an IoT Connector. The IoT Connectors can be managed and connected to applications the same ways as Standard IoT Connectors.

Device Cloud Integrated IoT Connector
Custom Device API Integrated IoT Connector

Existing Integrations

The following integrations can be found in Exchange under the IoT Connector Template section. These templates were created to provide a zero-development integration experience.

Integration

Guides

Sigfox

AWS-IoT

Banner Engineering

RadioBridge

ElectricImp

Ewon

MachineQ

OpenWeatherMap

Configuration of Integrations

Each integration may have specific setup steps that include setting credentials, etc.

Data Schema Transformation

Your hardware model might have some unique data structure not compatible with the ExoSense data model.

For this purpose, Cloud-To-Cloud templates provided a set of customizable scripting modules allowing you to apply the data transformation to & from the 3rd Party API.

You can directly update those modules' logic through Murano scripting Editor under your Cloud-Connector Modules->vendor.c2c.transform. While not mandatory, you probably want to have a look at the Murano Scripting reference to give you more context on the scripting.

Note: The vendor name-space is 'safe' and will not be updated if the Cloud-Connector is updated to a newer version of the template. However any modification made outside of the vendor name-space will be lost.

Create your own (Advanced)

If you cannot find your 3rd party API listed on the Exchange Marketplace, you might need to do the integration using the advanced Murano platform scripting & integration capabilities.

An advanced Exosite account may be required, please contact support to discuss the integration.

Thankfully you can re-use the same base template, used by all standard Cloud-Connectors, to make your integration easier and ensure compatibility with Exosite applications.

The Cloud-Connector base template is a public Github repository published by Exosite. You will find all the necessary information there.

A highlight of the required steps:

  1. Define the remote API using OpenAPI v2 swagger and publish it as a Murano-Service on the Exchange Marketplace

  2. Fork & customize the Cloud-Connector base template to fit your integration need

  3. If you want to share your integration make both the service and the template Public

You will also need to make yourself familiar with Murano platform custom application development and solution publishing.