Telemetry
Telemetry is data emitted by devices, such as measurements, status, events, or operational signals. In Infuse-IoT Cloud, the API surface currently exposes the operational side of telemetry: latest device state, routes, logger progress, and device key-value entries.
Use Infuse-IoT Cloud to understand what the device last reported and how to communicate with it. Use Infuse-DB for raw and computed time-series records after telemetry is ingested into a dataset.
Console Views
The console exposes operational telemetry context from the device detail page:
| Device detail area | Use |
|---|---|
| Summary | Review last seen time, status, application ID, and application version. |
| KV Store | Inspect device configuration and state entries, including decoded values where definitions are available. |
| Logger Sync | Inspect per-logger reported/downloaded blocks, timestamps, and download enablement. |
| RPCs | Review command activity and responses for the device. |
Use these views for support and operations. Use Infuse-DB for queryable time-series data and long-term analysis.
Device State
Device state represents the latest operational state known for a device. It can be read by record ID or by deviceId, and updated by backend services when they receive trusted state changes.
| Task | Endpoint |
|---|---|
| Read state by record ID | GET /device/id/{id}/state |
| Update state by record ID | PUT /device/id/{id}/state |
| Read state by device ID | GET /device/deviceId/{deviceId}/state |
| List devices with state | GET /device-and-state |
Routes
Route data captures the last known communication path for a device. It is used by downlink workflows such as RPC commands.
| Task | Endpoint |
|---|---|
| Read last route for one device | GET /device/deviceId/{deviceId}/lastRoute |
| Read last routes for multiple devices | POST /device/lastRoute |
Logger State
Logger state tracks per-logger download progress and whether logger download is enabled.
| Task | Endpoint |
|---|---|
| Read one logger state | GET /device/deviceId/{deviceId}/loggerState/{index} |
| Update one logger state | PATCH /device/deviceId/{deviceId}/loggerState/{index} |
| Read all logger states | GET /device/deviceId/{deviceId}/loggerStates |
KV Entries
KV entries represent device-side configuration or state values. Entries can be decoded when the relevant KV definitions are known. Pending updates let your backend request device-side changes and track their status.
| Task | Endpoint |
|---|---|
| List entries | GET /device/deviceId/{deviceId}/kv/entries |
| Read one entry | GET /device/deviceId/{deviceId}/kv/entries/{keyId} |
| Read pending or historical updates | GET /device/deviceId/{deviceId}/kv/entries/{keyId}/updates |
| Create an update | POST /device/deviceId/{deviceId}/kv/entries/{keyId}/updates |
| Cancel a pending update | DELETE /device/deviceId/{deviceId}/kv/entries/{keyId}/updates |
The console can show decoded KV values when KV definitions are available. If a definition is unavailable, use the raw base64 view. For more detail, see Device Configuration.
Moving Data To Infuse-DB
Infuse-IoT Cloud is the device communication and operational context layer. Infuse-DB is the scalable time-series data layer. A typical data pipeline receives telemetry from devices or gateways, uses Infuse-IoT Cloud identifiers and definitions to interpret the data, then writes raw or computed streams into Infuse-DB for live and historical fleet access.
For a cross-product flow, see Stream IoT Data to Infuse-DB.