MQTT, fully unified inside xSERVA
xSERVA brings MQTT sensor fleets and edge telemetry into the same platform as your BACnet, KNX, and Modbus systems, with configurable QoS levels and broker-based ingestion built in from day one.
Book a DemoWhat is MQTT?
MQTT (Message Queuing Telemetry Transport) is a lightweight, publish/subscribe messaging protocol designed for constrained devices and low-bandwidth, high-latency networks. Rather than devices talking directly to each other, every device publishes updates to named topics on a central broker, and any interested system subscribes to the topics it cares about. That decoupling is what makes MQTT the standard choice for modern IoT: sensors do not need to know who is listening, and new subscribers can be added without touching the devices themselves. Originally developed for industrial telemetry over unreliable links, MQTT has since become the default protocol for smart-building sensor networks, environmental monitors, and edge devices of every kind.
Publish/subscribe for IoT sensor fleets
xSERVA's MQTT integration is built around the same publish/subscribe model that makes MQTT efficient at scale. Temperature, humidity, occupancy, air-quality, and vibration sensors publish readings to topics as they change, and xSERVA subscribes to the relevant topics to bring that telemetry directly into its dashboards, alarms, and analytics — without polling every device individually. This matters most in buildings with dense sensor deployments, where hundreds or thousands of low-power devices need to report frequently without saturating the network or draining battery-powered hardware, something protocols built around request/response polling struggle to do efficiently at the same scale.
Broker architecture and QoS levels
Every MQTT deployment runs on a broker — the central hub that routes published messages to subscribers. xSERVA connects to the broker already in use on site, or ingests through its own broker connection, and supports all three standard MQTT quality-of-service levels: QoS 0 (at most once, fire-and-forget) for high-frequency, low-stakes readings; QoS 1 (at least once) for data that must arrive but can tolerate the occasional duplicate; and QoS 2 (exactly once) for critical telemetry where both loss and duplication are unacceptable. Choosing QoS per device lets a project balance network efficiency against delivery guarantees instead of applying one blunt setting to every sensor on the bus.
Real-time telemetry at scale
Because MQTT connections stay open and messages push the moment a value changes, xSERVA receives sensor updates in real time rather than waiting on the next poll cycle. That responsiveness matters for use cases like occupancy-driven HVAC adjustment, leak detection, or vibration-based predictive maintenance, where a delayed reading is a missed intervention. xSERVA's MQTT layer is built to hold large numbers of concurrent topic subscriptions without degrading, so a sensor network can grow from a pilot floor to a full campus without a platform migration along the way.
Where MQTT shows up in real buildings
MQTT is the protocol behind large-scale environmental and occupancy sensor networks, wireless retrofit sensor kits added to older buildings, and edge devices reporting equipment health for predictive maintenance programs. It is especially common in projects that need dense point coverage — a sensor in every room rather than one per zone — without the wiring cost of a dedicated field bus. xSERVA folds that MQTT sensor data into the same dashboards, alarm queues, and energy models used for BACnet, KNX, and Modbus devices on the same site, so a real-time MQTT air-quality sensor and a BACnet air-handling unit can be correlated and acted on from one console.
Frequently asked questions
Does xSERVA run its own MQTT broker, or connect to an existing one?
xSERVA can connect to an existing MQTT broker already deployed on site, or ingest MQTT data through its own broker connection, depending on how the sensor fleet was originally commissioned.
What MQTT QoS levels does xSERVA support?
xSERVA supports all three standard MQTT quality-of-service levels, so telemetry can be tuned per device between at-most-once, at-least-once, and exactly-once delivery based on how critical each data point is.
Is MQTT suitable for large sensor deployments?
Yes. MQTT was designed specifically for lightweight messaging across large numbers of constrained devices, which is why it is the standard choice for dense IoT sensor networks in xSERVA-connected buildings.
Can MQTT sensors and BACnet controllers be monitored together?
Yes. Inside xSERVA, MQTT sensor data and BACnet, KNX, or Modbus device data all resolve to the same underlying data model, so they appear together in one dashboard and one alarm queue.