MQTT

MQTT connects Niagara to the world outside the building – cloud analytics, IoT sensors, and enterprise platforms that speak publish/subscribe rather than BACnet. Software Pile builds MQTT integrations that treat the broker as production infrastructure: authenticated, resilient, and observable.

Two Directions, Different Problems

Publishing station data outward – to cloud platforms, analytics pipelines, or a corporate broker – is about topic design, payload schemas (plain JSON, Sparkplug B, or your platform’s format), QoS choices that match what the data is worth, and TLS with proper certificate handling on the station.

Subscribing to external data – wireless sensors, LoRaWAN gateways, third-party feeds – is about turning loosely structured payloads into typed Niagara points with histories and alarms, and deciding what happens when the feed goes quiet.

Reliability Details That Matter

• Reconnect and session behavior when the WAN drops – and what the station does with stale values meanwhile
• Last-will messages so the other side knows the station went away
• Buffering strategy for histories during outages
• Broker authentication: credentials, client certificates, and rotation without site visits

Start the Conversation

Tell us what should flow where: which points, toward which platform or broker, at what rate, and your Niagara version. If a custom payload format is involved, a sample message tells us most of what we need.