MergenHub Envest
Protocol · MQTT

MQTT — automatic discovery and liveness tracking

The publish/subscribe protocol of IoT and field sensors. The MergenHub MQTT driver decodes payloads automatically and clearly marks values as stale when a topic goes silent.

← All protocols & modules
MergenHub — MQTTConnected
Project
Connectivity
MQTT
Field_Sensors
Field_Sensors · broker.site.local : 1883
DriverMQTT Client
Brokerbroker.site.local:1883
SchemeSparkplug B
QoS1
DiscoveryJSON-pointer
TagAddressValueQuality
TemperatureDHT22/temp24.6Good
HumidityDHT22/humidity58.2Good
Door_Statesensors/door/state1Good
Batterysensors/n1/batt3.71Good
Motionsensors/pir/motion0Good

The MergenHub interface — values discovered via MQTT topic / JSON-pointer addresses; liveness via arrival-watchdog.

What is MQTT?

MQTT is a lightweight publish/subscribe protocol where devices publish and subscribe to topics through a broker. It is ideal for sensors, IoT gateways and cloud links; payloads are usually JSON, sometimes binary or plain text.

Where is it used?

Remote field sensors, LoRa/NB-IoT gateways, energy metering links and cloud telemetry. Wherever the device "pushes" data at its own pace and event-driven flow is preferred over polling.

The MergenHub difference

Channel model, smart discovery and liveness

MQTT is not a poll-based PLC; the driver models that difference correctly from the architecture up.

Connection

Channel-level broker

Broker settings live at the CHANNEL level; all device-topics on the same broker share one connection — no double connections or wasted session overhead.

Discovery

Smart JSON discovery

Automatically discovers fields in incoming payloads via JSON-pointer and generates tags; nested objects, arrays and deep structures are walked (with an upper bound).

Format

Multi-format payloads

JSON, key=value, CSV, XML and binary payloads; second/millisecond time-stamp detection.

Liveness

Arrival watchdog

The expected arrival interval is tracked per topic; if no new message arrives in time, the tag quality is degraded.

Difference

Stale data never stays Good

Some tools hold the last value as "Good" indefinitely; MergenHub marks the quality of a silent topic as UNCERTAIN and shows it on screen.

Extensibility

Sparkplug-ready

The channel=broker / device=topic model extends naturally to structured payload frames (e.g. Sparkplug).

Payload and connection support
JSON / JSON-pointerKey=valueCSVXMLBinarysec / ms time-stampShared broker connectionArrival watchdogTLS
Control safety

Stale data is not shown as fresh

GuaranteeThe expected arrival interval is tracked for every topic. If no new message arrives in time, tag quality is downgraded automatically, so a silent sensor does not keep showing an up-to-date value.