Last updated on September 16th, 2024
JSON formats compliant with the ThingsBoard platform.
- ThingsBoard compliant format for all messages
Thingsboard raw type Basic V1.1
- ts: timestamp of the message reception date at the satellite (milliseconds since 01/01/1970 UTC)
- device_id: transmitting device identifier
- msg_date: message reception time at the satellite in UTC
- msg_id: message identifier
- raw_data: user payload in hexadecimal format
- bit_length: payload length in bits. If the length is not multiple of 8 bits, payload is padded with extra 0 bits to the right, in order to fit to an even number of hexadecimal digits.
JSON example
{
"ts":"1633524783542",
"values":[
{
"device_id":51244,
"msg_date":"2021-10-06T12:53:03.542Z",
"msg_id":"965985862653317120",
"raw_data":"08f222cc79e222551000f424011fb7fffee1ee8de70f0f0f0f00007eaf7680",
"bit_length":248
}
]
}
- ThingsBoard compliant formats for processed messages received from 28-bit address devices with a codec declared
Thingsboard processed type Basic
Only messages with correct integrity control are distributed
- ts: timestamp of message reception date at the satellite (milliseconds since 01/01/1970 UTC)
- device_id: transmitting device identifier
- msg_date: message reception time at the satellite in UTC
- msg_id: message identifier
- RAW_DATA: encoded user payload in hexadecimal format
- CRC_OK: integrity check status
- checked: message verification status
JSON example
{
"ts":1633524783542,
"values":[
{
"device_id":51244,
"msg_date":"2021-10-06T12:53:03.542Z",
"msg_id":"966002314227916800",
"RAW_DATA":"2CC79E222551000F424011FB7FFFEE1EE8DE70F0F0F0F00000",
"CRC_OK":true,
"checked": "Y"
}
]
}
Thingsboard processed type Expert
All messages are distributed regardless their integrity control
- ts: timestamp of message reception date at the satellite (milliseconds since 01/01/1970 UTC)
- device_id: transmitting device identifier
- msg_date: message reception time at the satellite in UTC
- msg_id: message identifier
- RAW_DATA: user payload in hexadecimal format
- CRC_OK, BCH_STATUS: integrity check status, number of bits in error, Message Counter, Service Flag
- checked: message verification status
JSON example
{
"ts":1633524783542,
"values":[
{
"device_id":51244,
"msg_date":"2021-10-06T12:53:03.542Z",
"msg_id":"966002314227916800",
"RAW_DATA":"2CC79E222551000F424011FB7FFFEE1EE8DE70F0F0F0F00000",
"CRC_OK":true,
"BCH_STATUS":1,
"checked":"Y"
}
]
}
- ThingsBoard compliant format for native location (Doppler) messages
Thingsboard location format V2
- ts: timestamp of the location message date (milliseconds since 01/01/1970 UTC)
- location_date: computed location date time in UTC
- location_id: location identifier
- revision: number of revisions of the location, range [0..+10]
- longitude: longitude in degrees in range ]-180..+180]
- latitude: latitude in degrees in range [-90..+90]
- altitude: altitude from sea level in meters
- error_radius: error radius of the location in meters
- raw_msg_ids: raw messages ids linked with this localization info
JSON example
{
"ts": 1234567
"values": [
{
"device_id": 51244,
"location_date": "2006-01-02T15:04:05.000Z",
"location_id": 5431232,
"revision_id": 1,
"longitude": 18.484897811810058,
"latitude": 69.55063092812153,
"altitude": 0,
"error_radius": 123,
"raw_msg_ids": [ "123456789", "124567826" ]
}
]
}