Update security credentials for admin
Define sensor schema, gateway channel mappings (`field1..field8`), and display properties.
Provision a physical plant instrument or gateway channel to your tenant.
Telemetry1 connects physical plant instruments (ATAGO refractometers, flow meters, PLCs, temperature sensors) to your cloud dashboard in 3 connected stages:
Create a Device Profile defining sensor channels (field1..field8) and register your Device ID with an API Key.
Configure your CloudPLC / ESP32 / Gateway to send sensor readings via HTTP GET/POST or MQTT broker topic.
As soon as first packet arrives, the card appears live on Fleet Monitor and is logged in Data Explorer.
Device profiles tell the IoT platform how incoming gateway channels map to human-friendly process metrics.
{"field1": "brix", "field2": "temp", "field3": "nD"}).°Bx, °C, L/min) and designate a Hero Metric for card display.Each physical gateway or sensor is registered to your tenant (tenant-A):
atago-line1-juice or cloudplc-01).ak_live_...).Industrial microcontrollers (ESP32, Arduino, SIMCOM cellular modems, CloudPLC) can publish using standard HTTP requests:
http://31.220.87.225/api/telemetry/update
For high-frequency or bidirectional telemetry, use the built-in MQTT broker:
Once your device transmits its first payload via either HTTP or MQTT:
DEVICE_PROVISIONING_GUIDE.md
Client-side & Ingestor threshold evaluation for uni-directional sensors
Tabular process logs, time-series chart, and historical data export
| Timestamp ▼ | Device ID | Sensor Type | Brix (°Bx) | Temp (°C) | Refractive (nD) / Flow | Status | Payload |
|---|---|---|---|---|---|---|---|
| Loading telemetry records... | |||||||
Define hardware schemas, channel decoders (field1..field8), and register plant devices
| Device ID | Name | Profile | API Key / Token | Last Seen | Status | Action |
|---|---|---|---|---|---|---|
| Loading registered devices... | ||||||