MQTT integration

Connect device telemetry with assets, maintenance and production information in Uplyst.

From device telemetry to operational context
  1. Devices and gateways

    Publish observations to MQTT topics.

    Asset identity, measurement, unit and observation time.
  2. MQTT broker

    Routes messages to authorised subscribers.

    Topic permissions, delivery quality and session settings.
  3. Uplyst

    Connects readings with equipment and process information.

    Condition monitoring, maintenance and production context.
Last known values and current conditions

A retained message supplies the latest retained publication for a topic. Its observation time determines whether it is recent enough for an operational decision.

Telemetry and asset mapping

Connect device readings to operational assets

An authorised MQTT subscription can supply device and gateway observations to Uplyst's intelligence layer. Asset identity, measurement units and observation time connect telemetry with equipment, maintenance records and production activity.

MQTT topics route messages; the payload defines what each observation means. Mapping a device to a stable business asset preserves its operational history when sensors are replaced or moved.

Distinguish current readings from last known values

A retained message can give a new subscriber the latest retained publication for a topic. Its arrival does not establish when the equipment was measured or whether the device is still connected. Observation time and an appropriate freshness threshold determine how that value is used.

MQTT 5 message and session expiry settings affect what remains available to reconnecting consumers. Stale readings and missing intervals remain visible in the operational view.

Asset conditionUtilities / Pump P-204

Bearing temperature

72.4°C

Last known reading

Observed
14:02:08 UTC
Received
14:14:08 UTC
Delivery
Retained publication

Observation age at receipt

12 minutes
0 min5 min15 minFreshness threshold

Fresh observation requiredThe broker delivered a value now. The asset was measured twelve minutes earlier.

Maintenance reference
WO-2841 · Bearing inspection
Operational use
Retain in history; exclude from current condition.
Topicutilities/pump-p204/bearing/temperature

Delivery quality and observation history

MQTT provides three quality-of-service levels: at most once, at least once and exactly once within the protocol delivery exchange. Broker and client session settings affect what can be recovered after a disconnection.

Application observation identifiers or sequences help recognise missing and repeated readings. MQTT delivery guarantees do not by themselves guarantee that a downstream maintenance task or database update happens exactly once.

Telemetry concernRequired context
Measurement valueUnit, scale and valid range
Observation timeSource clock and timestamp meaning
Device replacementMapping to stable asset identity
Repeated deliveryApplication observation identity or revision

Scoped broker and topic access

The broker controls authentication and authorisation for publishers and subscribers. Supported TLS settings, dedicated client identities and topic permissions limit access to the relevant equipment or site. Credential and certificate renewal form part of maintaining that connection.

Put equipment conditions in business context

Changes in condition can be considered alongside maintenance history, production schedules and quality records. Units, valid ranges and clock quality help distinguish a real operating change from a faulty or delayed observation. Equipment control requires its own authorised industrial workflow.

Connect your systems
with Uplyst.

Talk with our team about the systems you use and the decisions they need to support.

Discuss an integration