AWS IoT payloads & topics

TAMsys ingests device telemetry through AWS IoT Core. Whether you use MQTT or HTTPS, publish each device’s messages to its device-specific topic.

Publish topic

tessol/tamsys/{device_id}

Replace {device_id} with the exact TAMsys device identifier provisioned for the device.

Minimum payload

Messages are JSON objects. Include the device ID and a UTC timestamp in epoch milliseconds:

{
  "id": "00:E0:12:34:56:ED",
  "utctimestamp": 1785488704000,
  "temp": 4.6,
  "latitude": 19.1395068,
  "longitude": 73.0142075
}

Field	Type	Required	Description
id	string	Yes	Device identifier; should match the topic device ID
utctimestamp	number	Yes	Reading time as Unix epoch milliseconds in UTC
Other attributes	varies	Device-specific	Telemetry supported by the device type, such as temperature, location, speed, or voltage

Use valid JSON

Do not include comments, trailing commas, NaN, or Infinity. Publish numeric telemetry as JSON numbers unless the device contract says otherwise.

Delivery guidance

• When using MQTT, use a unique client ID for each active connection.
• Preserve the original reading time in utctimestamp when replaying buffered data.
• Implement reconnect behavior with exponential backoff.
• Do not put secrets or certificates in the telemetry payload.

Continue to MQTT and HTTPS publishing for endpoint, authentication, and TLS requirements.