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 Server- devices send their data to Device Manager Server in their 'native' protocol, which is raw TCP. Device Manager Server handles device management including firmware updates, parameter updates, debugging, and controls where this data is then directed. 

When using the TCP connector, the raw TCP data is simply forwarded to the end server (front-end tracking platform). When using the HTTP connector, Device Manager Server repackage the data and sends it in JSON format via HTTP POST to the desired endpoint. The end server must respond with 200, 201, 202, or 204 OK to confirm the message has been received; then, Device Manager Server instructs the device to delete these messages from its memory, as they have been saved to the server. When using the MQTT connector, Device Manager Server repackage the data and publish it in JSON format via MQTT to a specified MQTT broker.

Connectors control this in Device Manager. Connectors can be set up as shown here - Create a Connector

Authentication, Authorization and Security

The latest generation of our devices connect to Device Manager over an AES-256 encrypted connection. After Device Manager, when transmitting to a 3rd party server, the MQTT connector can be used to ensure complete end-to-end encryption. 

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