Configure MQTT
Applies to SiteSync StandardEnterprise Management
Configure the MQTT connection SiteSync uses to receive live device data.
Common fields
Section titled “Common fields”| Field | Description | Example |
|---|---|---|
| Broker URL or IP address | The address of your MQTT broker (or LNS with built-in MQTT), without the http:// scheme. | chirpstack.example.com |
| Port | Usually 1883, or 8883 for TLS. | 1883 |
| MQTT topic | The topic pattern uplinks are published to. Format is network-server specific. | application/1/device/+/event/up |
| Username / Password | Required by some network servers; optional but recommended for others. | sitesync / •••••• |
Multiple topics on one broker
Section titled “Multiple topics on one broker”A single broker connection can subscribe to multiple topics at once. Separate them with a semicolon (;). This works for any MQTT broker, regardless of network server or version:
application/1/device/+/event/up;application/2/device/+/event/upThis is useful when devices are split across several applications on the same broker. (This is different from multiple connections — see Connection concepts.)
Per-network-server settings
Section titled “Per-network-server settings”The exact broker address, port, and topic depend on your network server. Pick yours:
Common issues
Section titled “Common issues”- No data arriving: confirm the broker URL and port, and that the Ignition gateway can reach the broker through your firewall (typically
1883, or8883for TLS). The MQTT status is polled every 30 seconds — check Connection health. - Connected but no values: the topic pattern may not match your application, or the device still needs a decoder — see Decode error.
- Auth rejected: re-check the MQTT username and password; some brokers require authentication.
For deeper help, see MQTT disconnected.