Telemetry
Telemetry
Understand how device data flows through the Sensorclouds platform
Telemetry is the core data flow in Sensorclouds - the path your device's sensor readings take from the physical device to your dashboard.
Data Pipeline
When a device publishes telemetry, the platform processes it through this pipeline:
- Device publishes data to its MQTT telemetry topic
- Platform validates and parses the message
- Hex payloads are auto-detected and converted
- Payload decoder runs (if configured on the device profile)
- Timestamp determined (platform time or device-provided time)
- Data stored in the time-series database
- New fields are auto-discovered and registered
- Device status updated to ONLINE
- Alarm rules evaluated against the new data
- Data broadcast to dashboards via WebSocket
Telemetry Pipeline
1Ingest
Device publishes
Validate & parse
Hex auto-detect
2Transform
Payload decoder
Apply timestamp
3Persist
Store time-series
Field discovery
4React
Mark ONLINE
Evaluate alarms
Push to dashboards
Each message a device publishes flows left to right through these four stages before it reaches your dashboard.
Limits
| Limit | Description |
|---|---|
| Messages per device | Rate-limited per minute to prevent abuse |
| Max payload size | Limited per message to ensure processing efficiency |
History & Access
- Device history defaults to a recent window (last 7 days), with older ranges available up to your plan's retention window.
- Telemetry can also be pulled programmatically via the external API.