Ingest from Any Broker
Subscribe with topic filters and wildcards, then map each topic and JSON path to a tag with a unit.
Subscribe to any broker, publish normalized data back out, and keep topics, QoS and retained state under control.

MQTT is a lightweight publish and subscribe protocol. Devices send messages to named topics on a broker, and anything subscribed to a topic receives them. MQTT defines the transport, not the payload, so two vendors can both speak MQTT and still send incompatible data. IoTServa treats a broker as both a source and a destination, and its gateways send signed telemetry through a broker you configure.
Native Address
Node
Factory > Line 2 > Oven Temperature
182.4°C
Subscribe with topic filters and wildcards, then map each topic and JSON path to a tag with a unit.
Gateways send signed readings over MQTT 3.1.1 to the broker set in the cloud, so a forged message is rejected.
Send clean, consistently named values back out to your own broker or a cloud broker, with the QoS you choose.
Connect over TLS with client certificates or a username and password, and keep secrets sealed rather than in project files.
Plain MQTT is read today. Sparkplug B decoding is on the roadmap; until then a bridge can republish its metrics as plain topics.
Choose QoS deliberately. QoS 0 can drop messages, QoS 2 costs more than most telemetry needs.
Retained messages make a dashboard show stale data as if it were live unless you track message age.
Agree one topic naming scheme per site before devices multiply.
A consistent MQTT topic scheme saves years of pain on multi-site projects. See a simple convention, what to avoid, and how QoS and retained messages fit in.
Read the GuideHow to turn Modbus registers into MQTT topics: polling, decoding scale and word order, topic and payload design, QoS, retained values and failure handling.
Read the GuideQuality of service 0, 1 and 2, retained messages and Last Will in plain terms, with practical guidance for sensor, gateway and alarm telemetry on MQTT.
Read the GuideWhat good, stale and bad quality flags mean, how store and forward keeps history honest during outages, and why dashboards should never repeat an old value.
Read the GuideDrives, meters and PLCs trended together, with alarms that mean something.
See the SolutionGeneration and consumption reconciled in one view.
See the SolutionLuminaire faults, energy and emergency tests from DALI and KNX, in one view.
See the SolutionSensors across land where Wi-Fi and cables never reach.
See the SolutionLook Up a Term in the Glossary or check devices on the Hardware Page
A site rarely runs a single protocol. The same project can read all eight.
No. It connects to the broker you already run, or to one you choose, acting as an MQTT client that can both subscribe and publish, over TLS with client certificates or a username and password.
Yes. Every normalized Node can be published to a broker with a topic pattern and QoS you define, so other systems receive clean, consistently named values with units. Data is also available through the REST API, signed webhooks, and CSV and JSON exports.
QoS 0 delivers a message at most once with no acknowledgement. QoS 1 delivers at least once, so duplicates are possible. QoS 2 delivers exactly once between each sender and receiver using a four-packet handshake (PUBLISH, PUBREC, PUBREL and PUBCOMP). Higher levels use more bandwidth and add latency, so telemetry often uses 0 or 1 and commands use 1 or 2.
Tell us the make and model of what is on site. We will scope a pilot against your real equipment.