Message Profiles

The Thingsee Message Protocol defines how devices communicate with the cloud platform. Messages are organized into profiles based on functionality, with each profile assigned a specific ID range.

Protocol Reference

• Message Header - Standard header fields and structure
• Message Commands - Sending commands to devices

Message Structure

Every Thingsee message contains a standard header with the following fields:

Event Types (tsmEv)

Common event type codes used across all profiles:

Profile ID Ranges

Data Format

Messages are transmitted as JSON (for APIs) or CBOR (optimized binary format for device communication). The content is identical between formats.

Example Message:

[{
    "tsmId": 1110,
    "tsmEv": 101,
    "tsmTs": 1492603998,
    "tsmTuid": "TSPOD6789",
    "tsmGw": "TSGW1234",
    "batl": 34.6,
    "chrg": 2
}]

Working with Messages

Receiving Messages

Sensor data messages are delivered through your configured integration:

• MQTT: Subscribe to device topics
• Azure IoT Hub: Use Event Hub consumer
• AWS IoT: Use IoT Rules or direct consumption

Sending Commands

Configuration and command messages are sent via the Open Service API:

curl -X POST \
  "https://{api-url}/v1/things/{tuid}/commands" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '[{
    "tsmId": 1500,
    "tsmEv": 30,
    "measurementInterval": 60,
    "reportInterval": 300
  }]'

The device will respond with tsmEv: 31 containing the applied configuration.

In This Section

Individual profile specifications with message IDs, payload formats, and examples.