Connect your first data source

Bring an actual gateway reading or export. This guide uses authenticated HTTPS batch submission. Source-type labels do not activate MQTT, OPC UA, BACnet, Modbus or vendor API collectors.

Signed-in customers connect automatically. Optional development tokens stay in page memory only. Do not enter gateway passwords or secrets in reading payloads. No sample readings are automatically inserted.

Optional development token access

Not connected.

Connect to your organization.
Choose or register a source.
Map actual measurement keys and units.
Preview, submit and verify stored event receipts.

1. Choose or register a source

Existing source

2. Map measurements

Choose a source first.

3. Prepare and preview actual readings

Or load an exporter JSON file (up to 32 KiB)Batch JSON: {"readings":[{"event_uuid":"UUID","source_key":"mapped key","observed_at":"timestamp with timezone","value":number}]}

1–100 readings. Each event needs a stable lowercase UUID: reuse it only when retrying that same event. Payloads must contain only the documented fields; credentials do not belong here.

Export endpoint: Choose a source. External exporters use their own authorized credentials; this page does not configure or start them.

4. Verify persistence and continue

Submit a previewed batch first.

Queue acceptance does not establish database persistence. Receipts verify event IDs and content, not live gateway connectivity or calibrated values. Historical imports may be stale and timestamps in the future remain suspect.

Open monitoring, history and alerts →

Your signed-in organization session continues on the monitoring page. Development-token users must reconnect there. Refresh monitoring/history, then inspect scheduled incident checks separately. This guide cannot certify alert recovery until you provide real observations crossing your configured thresholds.

Advanced source management