Sparkplug B
Decodes Sparkplug B messages into readable JSON, or publishes your topics as a Sparkplug edge node.
- Direction:
- Reads and writes
- Role:
- Client
Connectors bring PLCs, machines and devices into MQTT, send setpoints back and deliver clean data to your databases, streams and AI tools, all from inside the MQTT Broker.
Decodes Sparkplug B messages into readable JSON, or publishes your topics as a Sparkplug edge node.
Hosts an OPC UA server in the Broker, so OPC UA clients read your data and write back to MQTT.
Produces and consumes Kafka topics, on your own cluster or a managed service.
Platform
They’re the MQTT Broker’s way in and out, so there’s nothing extra to install. Your plan sets how many you can run.
Reads BACnet objects, follows changes of value and writes setpoints back to HVAC, lighting and metering controllers.
Serves your MQTT topics as Modbus registers and coils, so a SCADA or HMI can read and write them.
7 Connectors shown
Controllers, buildings, databases, streams and AI tools, all read and written from inside the MQTT Broker.





If it has an HTTP API, the REST API Connector (opens in a new tab) reaches it. If it already speaks MQTT, it connects straight to the Broker. For anything else, tell us what you need.