Integration: TTS - AVEVA PI System

[Jaime-Trinidad]

Summary

Document and validate a native integration path between TTS Cloud and AVEVA, targeting industrial customers who already run AVEVA PI System / CONNECT Data Services / Edge Data Store and need to ingest LoRaWAN telemetry without custom middleware.

Increasing number of prospects in process-industry verticals (oil & gas, utilities, water, manufacturing) where AVEVA PI is the operational data backbone. No documented TTS integration exists for this stack today. This is a recurring adoption blocker.

Approach

Use the TTS MQTT Server as the source and the AVEVA Adapter for MQTT as the consumer. The adapter subscribes to TTS uplink topics, extracts values from decoded_payload via JSON field mapping, converts to OMF, and writes to the configured AVEVA destination.

TTS Cloud (MQTT, 3.1.1, QoS 0)
  → AVEVA Adapter for MQTT (JSON extract → OMF)
  → PI System / CONNECT Data Services / Edge Data Store

Deliverable

A technical integration guide: TTS application setup, payload formatter requirements, MQTT topic structure, API key config, AVEVA Adapter configuration, JSON-to-time-series mapping, OMF destination setup, and validation steps.

[Jaime-Trinidad]

Per the official AVEVA Adapter for MQTT documentation, the adapter collects data from MQTT sources, converts it to OMF, and sends it to a supported AVEVA data archive: PI Server (via PI Web API), CONNECT Data Services, or Edge Data Store. AVEVA is actively moving customers to cloud-based subscriptions via CONNECT Data Services, which is the most accessible target for testing this integration without an on-prem PI Server deployment.
To validate the full TTS → AVEVA integration path, I need access to a working AVEVA environment with the adapter installed and an OMF endpoint available. The specific items to test are:

• MQTT 3.1.1 + TLS connection from the adapter to {tenant}.{cluster}.cloud.thethings.industries:8883
• Topic subscription to v3/{app}@{tenant}/devices/+/up
• JSON field extraction from the nested TTS uplink envelope ($.uplink_message.decoded_payload.*, $.received_at, $.uplink_message.rx_metadata[0].rssi)
• OMF stream creation and time-series data write to the AVEVA destination

Next steps

• Contact AVEVA to request trial or developer access (Partner / Developer Program) — scoped to CONNECT Data Services + Adapter for MQTT
• Read full AVEVA Adapter for MQTT documentation end to end
• Configure AVEVA Adapter for MQTT: MQTT connection, TLS, topic subscription, JSON field mapping, OMF destination
• Set up AVEVA PI System or CONNECT Data Services as the OMF target
• Run end-to-end test with a live TTS uplink and confirm time-series data lands in the AVEVA destination

avevatm_adapter_for_mqtt_6-8-2026.pdf