Vibration sensors, PLC gateways and motor drives publish condition data to ConnectMQ. Your condition-monitoring models subscribe, score the health of every asset, and your CMMS gets a work order while there is still time to plan the repair.
No card required
PUBLISH plant/dallas/line-1/press-04/vibration
{"ts":"2026-10-22T08:14:05Z","rms_mm_s":7.4,"peak_g":2.9,"bearing_temp_c":71.2,"rpm":1480}QoS 1 · TLS 8883 · PUBACK
Most plants still run on calendar-based PMs and monthly vibration routes. Bearings, gearboxes and pumps wear out between rounds, the data that would have shown it never leaves the PLC or sits in a historian nobody watches, and the first sign is an unplanned stop. Wiring every sensor vendor directly to every analytics tool creates point-to-point integrations that break with each new line.
Wireless vibration and temperature sensors, current transformers or the drive itself measure the machine. An edge gateway such as Node-RED, Kepware or Ignition reads them next to PLC tags over Modbus or OPC UA.
The gateway publishes RMS velocity, peak acceleration, bearing temperature and motor current to the asset’s topic over TLS, every few seconds or on change.
Your condition-monitoring service or ML model subscribes with a wildcard, compares readings with each asset’s baseline and publishes a health score back as retained state.
A ConnectMQ threshold rule alerts the maintenance team, and your integration turns the warning into a work order in the CMMS — SAP PM, Maximo, Fiix or similar — with the readings attached.
Gateways push data as it is measured, and ConnectMQ delivers it to the model, the historian and the dashboard at once — no separate poller per tool.
The ISA-95 workspace organises site, area, line and machine topics, so a model subscribed to plant/+/+/+/vibration picks up new machines automatically.
Threshold rules on vibration or temperature raise an alert even before your model has scored the reading — a simple safety net next to the analytics.
Last Will and retained status show when a sensor gateway drops off, so a silent machine is never mistaken for a healthy one.
plant/dallas/line-1/press-04/vibration
plant/dallas/line-1/press-04/motor/current
plant/dallas/line-1/press-04/health (retained)
plant/dallas/line-1/press-04/status (retained)Many industrial wireless vibration sensors and their gateways can publish MQTT directly. Where a sensor or PLC only speaks Modbus or OPC UA, an edge gateway such as Node-RED, Kepware or Ignition reads the values and publishes them to a topic per asset over TLS.
No. ConnectMQ is the MQTT broker: it delivers condition data in real time and raises threshold alerts. The models — from simple trend limits to machine-learning anomaly detection — run in your own service or analytics platform, which subscribes to the broker and can publish its results back.
They work together. OPC UA is common for reading data from PLCs and machines on the shop floor; MQTT is better at moving that data from many machines and sites to many consumers. A typical setup reads over OPC UA at the edge and publishes to an MQTT broker for models, historians and the CMMS.
Start on the Free plan — no card required — connect your first devices today and upgrade when you go live.
