telemetry1.io
Universal Industrial IoT & Telemetry Platform
Cloud VPS Live Let's Encrypt SSL v2.4 LTS
Select Facility Account
telemetry1.io • End-to-End Encrypted Telemetry
Pricing • Terms • Privacy • Refunds • Contact Us

Telemetry1

Unified Fleet & Process Operations
Disconnected
admin (Password)

Change Password

Update security credentials for admin

Create Device Profile

Define sensor schema, gateway channel mappings (`field1..field8`), and display properties.

Gateway Ingestion Field Mappings (JSON) e.g. {"field1":"brix", "field2":"temp"}
Metrics Schema & Formulas (JSON Array) Defines names, units, decimals, hero metric

Register New Device

Provision a physical plant instrument or gateway channel to your tenant.

Need help connecting this device? View Step-by-Step Onboarding Guide →

End-to-End Device Onboarding Guide

Provision on Platform ➔ Configure Physical Device / Gateway ➔ Publish via HTTP or MQTT

How Device Onboarding Works

Telemetry1 connects physical plant instruments (ATAGO refractometers, flow meters, PLCs, temperature sensors) to your cloud dashboard in 3 connected stages:

Step 1: Platform Profile

Create a Device Profile defining sensor channels (field1..field8) and register your Device ID with an API Key.

Step 2: Device Commissioning

Configure your CloudPLC / ESP32 / Gateway to send sensor readings via HTTP GET/POST or MQTT broker topic.

Step 3: Instant Dashboard

As soon as first packet arrives, the card appears live on Fleet Monitor and is logged in Data Explorer.

A Create or Select a Device Profile

Device profiles tell the IoT platform how incoming gateway channels map to human-friendly process metrics.

  1. Navigate to Profiles & Devices tab in the bottom bar.
  2. Click + New Profile (or choose pre-configured profiles such as ATAGO Process Refractometer).
  3. Configure Field Mappings JSON (e.g., {"field1": "brix", "field2": "temp", "field3": "nD"}).
  4. Define display units (e.g., °Bx, °C, L/min) and designate a Hero Metric for card display.
B Register the Device ID & Obtain Ingestion Token

Each physical gateway or sensor is registered to your tenant (tenant-A):

  1. Click + Register Device.
  2. Enter your unique Device ID (e.g. atago-line1-juice or cloudplc-01).
  3. Select your newly created or standard Device Profile.
  4. Click Generate for an API Key, or enter your preferred token (e.g. ak_live_...).
  5. Click Register Device. Your device is now authorized!
HTTP Publishing via HTTP GET / POST Ingestion Endpoint

Industrial microcontrollers (ESP32, Arduino, SIMCOM cellular modems, CloudPLC) can publish using standard HTTP requests:

Target URL: http://31.220.87.225/api/telemetry/update
Option 1: HTTP GET (Standard Gateway Format)
GET /api/telemetry/update?api_key=ak_live_YOUR_KEY&tenant=YOUR_TENANT&device=atago-line1-juice&field1=12.45&field2=24.5&field3=1.3512 HTTP/1.1 Host: 31.220.87.225
Option 2: cURL Testing Command
curl -X GET "http://31.220.87.225/api/telemetry/update?api_key=ak_live_demo&tenant=tenant-A&device=atago-01&field1=12.85&field2=23.2"
Option 3: ESP32 / Arduino C++ Snippet
#include <WiFi.h> #include <HTTPClient.h> void sendTelemetry(float brix, float temp) { HTTPClient http; String url = "http://31.220.87.225/api/telemetry/update?api_key=YOUR_API_KEY&tenant=tenant-A&device=atago-01"; url += "&field1=" + String(brix, 2) + "&field2=" + String(temp, 1); http.begin(url); int httpResponseCode = http.GET(); if (httpResponseCode == 200) { Serial.println("Telemetry successfully sent to platform!"); } http.end(); }
MQTT Publishing via Mosquitto MQTT Broker

For high-frequency or bidirectional telemetry, use the built-in MQTT broker:

Broker Host: 31.220.87.225
Port: 1883 (or 8883 SSL)
Username: device-client
Password: device-secret-123
MQTT Ingestion Topic Hierarchy:
v1/tenants/{tenantId}/devices/{deviceId}/telemetry
Example JSON Telemetry Payload:
{ "brix": 12.85, "temp": 24.2, "refractive_index": 1.3524, "status": "NORMAL" }
Test with mosquitto_pub command:
mosquitto_pub -h 31.220.87.225 -p 1883 \ -u "device-client" -P "device-secret-123" \ -t "v1/tenants/tenant-A/devices/atago-01/telemetry" \ -m '{"brix": 12.85, "temp": 24.2, "refractive_index": 1.3524}'
✓ Verifying Telemetry on Platform

Once your device transmits its first payload via either HTTP or MQTT:

  • Fleet Monitor: The device card will flash and update immediately via SignalR real-time stream.
  • Master-Detail Focus Drawer: Click the card to inspect real-time sparklines, last seen timestamp, and all sensor attributes.
  • Profiles & Devices Tab: Under Registered Devices, check the Last Seen column confirming uplink connectivity.
  • Data Explorer Tab: Query historical points, filter by device, analyze time trends, and export CSV/JSON logs.
Need hardware gateway setup? See DEVICE_PROVISIONING_GUIDE.md
Active Devices
0
Live & transmitting
All Devices
0
Total registered fleet
0 devices
Refractometer

Device Inspector

tenant-A
Live Reading
--
Target Setpoint: Normal
Real-Time Trend (Last 20 pings) ● Active

Live Alert Log & History

Loading history...

Cloud Alert Rules

Client-side & Ingestor threshold evaluation for uni-directional sensors

Create New Rule

Loading rules...

Telemetry Data Explorer

Tabular process logs, time-series chart, and historical data export

Data Availability: Calculating...
Historical Telemetry Trend
● Brix (°Bx) ● Process Temp (°C)
Timestamp ▼ Device ID Sensor Type Brix (°Bx) Temp (°C) Refractive (nD) / Flow Status Payload
Loading telemetry records...
Showing 0 to 0 of 0 entries
Page 1

Device Profiles & Gateway Ingestion Mappings

Define hardware schemas, channel decoders (field1..field8), and register plant devices

Loading device profiles...
Device ID Name Profile API Key / Token Last Seen Status Action
Loading registered devices...