Skip to content
DigiOS.
Log inBook a working session
Devices, labels and equipment

MQTT and Sparkplug B with DigiOS.

Machine and sensor data flows in over MQTT with Sparkplug B, and commands go back to edge nodes and devices, through an edge unit in your building.

Ask about MQTT and Sparkplug B

What moves each way

MQTT and Sparkplug B
  • Births and deaths: Into DigiOS
  • Data messages: Into DigiOS
  • Commands: Out of DigiOS
  • Host state: Out of DigiOS
DigiOS
What moves between MQTT and Sparkplug B and DigiOS: what, which way, the documents and data, and when.
WhatDirectionDocuments and dataWhen
Births and deathsInAn edge node or device announcing itself with its metrics, and announcing when it goes awayWhen it connects or disconnects
Data messagesInMetric values from edge nodes and devices, such as states, counts and temperaturesAs each value changes
CommandsOutA command to an edge node or device, such as a setpoint or a startWhen the floor releases the work
Host stateOutDigiOS announcing that it is online, so edge nodes know a host is listeningWhen DigiOS connects

On your floor

Conveyor and line viewWatch a carton pass the scanner and divert to its lane, and see which orders a stopped section is holding up. The back office and the conveyor read the same scan.

How DigiOS works with MQTT and Sparkplug B

DigiOS connects to your MQTT broker over TLS and follows the Sparkplug B topic namespace: it hears each edge node and device announce itself, follows their data, and sends commands back. For plain MQTT topics, we agree the topic names and the JSON with you.

Where it stands
1 Nov 2026
About MQTT and Sparkplug B
MQTT is a lightweight publish and subscribe protocol, and Sparkplug B is a specification that standardizes topics and payloads for industrial data over MQTT.
Your account
The devices, printers and controllers stay yours, on your network. DigiOS reaches them through an edge unit in your building, or from the browser.
If a document is rejected
A scan, a label or a command that fails shows on the device and in the exceptions list with its reason, and nothing is sent again on a guess.

Questions about MQTT and Sparkplug B

Do we need Sparkplug B?

No. Sparkplug B gives topics and payloads a shared shape. If you publish plain MQTT, we map your topics and JSON with you.

Does DigiOS run its own broker?

It connects to yours. Where a site has none, the edge unit in your building carries one.

What about a unified namespace?

If your plant publishes into one, DigiOS subscribes to the branches you choose and publishes the work it sends.

OPC UA serversValues in from any OPC UA server. Writes and method calls out.Mobile robot fleets over VDA 5050Jobs out to robots. Position, battery, order progress and errors back.Rockwell Automation and Allen-Bradley PLCs over EtherNet/IPWork out to the controller's tags. Line and machine state back.

Ask about MQTT and Sparkplug B.

Tell us what you run and what you want MQTT and Sparkplug B to do. A person answers in writing.

Ask about MQTT and Sparkplug B