Please see our article Choosing an Integration Strategy for a discussion on the various integration options with our devices. 

This article outlines the function and features of the MQTT JSON connector and how it can be used in integrating our devices into a 3rd party platform. Contact our support team for integration documents containing the payloads that will be sent.

The authorisation and authentication requirements of many systems can be accommodated.

Overview

When using Device Manager - devices send their data to Device Manager in their 'native' protocol, which is raw TCP. Device Manager handles firmware updates, parameter updates, debugging, and then controls where this data is directed and via which protocol. 

When selecting the MQTT connector, Device Manager Server re-packages the data and publishes it in JSON format via MQTT to a specified MQTT broker.

Information on connector setup can be found here: Create a Connector

Authentication, Authorisation and Security

Devices communicate to Device Manager over an AES-256 encrypted connection and then when an MQTTS Connector is selected for transmitting payloads onwards the broker can support end-to-end encryption. 

You will need to specify a username and password in the connector settings in order to authenticate.