Forward data over MQTT

MQTT forwarding publishes new readings to a broker and topic. A receiving system subscribes to that topic to read the messages.

Configure the broker

A Manager or Owner can create an MQTT profile under Organization → Data → Data Forwarding.

Field	Value
Host	Broker hostname or reachable address
Port	The broker's listening port
Client ID	A dedicated ID that does not conflict with another client
Topic	The receiver's subscribed topic, such as site-a/sensor/data
Username and password	Credentials required by the broker

Save and enable the profile. The current form has no TLS certificate settings or encryption switch. Changing the port to 8883 alone does not enable TLS. If the broker requires TLS, ask the platform administrator to verify the connection method first.

Message format

The payload is a JSON array containing one or more point records. See the HTTP POST request body for an example of identifiers, times, and values. Parse each entry and normalize time units.

Forwarding publishes data to the configured topic; it does not create a downstream control topic. Use the Open API for device control from another system.

Verify receipt

1. Subscribe to the target topic using a separate client ID.
2. Keep the subscriber connected and have a device report new data.
3. Check received point identifiers, times, and values, then inspect forwarding counts.

A successful publish is separate from subscriber processing. Store messages in the receiving system if you need retention. A broker connection does not verify historical backup.

No messages arrive

Check the host, port, account permissions, and matching publish and subscription topics. For repeated disconnects, check client ID conflicts. If sent counts do not increase, first check for new device reports.