Thingsee Operations Cloud comes with an MQTT broker that is available for you to subscribe. This is the preferred method for data integration unless you have some specific requirements or customization needs how the integration is done from Thingsee Operations Cloud to your cloud (e.g. direct Azure connection).
Topic Structure
cloudext/json/{groupId Prefix Environment}/{groupId Prefix Country}/{groupId CustomerId}/{tuid}/{messageId}
An MQTT client (your cloud) can subscribe
- to groupId level e.g. when data is needed from a logical group of devices
- a groupId can be e.g. "devices in production use" or "devices in use by customer XYZ"
- a groupId is partially defined by Thingsee and partially by the customer.
- to tuid level when a data is needed from the specific device
- where tuid is the tsmTuid-property of the JSON message.
- to messageId level when the specific data needed from the specific device
- where messageId is the tsmId-property of the JSON message.
Connection details
An MQTT broker address and X.509 certificate is delivered as part of Thingsee Operations Cloud installation process.
Note that you must allocate and manage ClientId (MQTT), and make sure that only one connection per ClientId is established at the same time. If you need to use multiple connections, then you must use unique ClientIds per connection.
Published messages
Messages are published as a single JSON objects
Sample data
Example message published to cloudext/json/rd/fi/samplegroup/XXXX03X2Z80562557/12100
{
"tsmId": 12100,
"tsmEv": 10,
"airp": 101364.599,
"lght": 6,
"temp": 21.3,
"humd": 21.7,
"tsmTs": 1520416221,
"tsmTuid": "XXXX03X2Z80562557",
"tsmGw": "XXXX00EFS80560445"
}
Example message published to cloudext/json/rd/fi/samplegroup/XXXX03X2Z80562557/1111
{
"tsmId": 1111,
"tsmEv": 10,
"accx": -1024,
"accy": 64,
"accz": -192,
"tsmTs": 1520416221,
"tsmTuid": "XXXX03X2Z80562557",
"tsmGw": "XXXX00EFS80560445"
}