HiveMQ Unified Namespace: Edge, Plant Broker and Enterprise
HiveMQ Sparkplug: The Eclipse Listing, Extension and Data Hub
HiveMQ Sparkplug support explained: what the Eclipse compatible list shows, the Sparkplug Aware Extension, Data Hub's module and the STATE permission trap.
HiveMQ Sparkplug support rests on three things: rows on an Eclipse list, a small open-source extension, and a Data Hub module. The Eclipse Sparkplug compatible software page, read on 20 November 2026, has three HiveMQ rows: the MQTT Broker Community Edition, the MQTT Broker Professional Edition and the Sparkplug Aware Extension. It shows no version or date for them, and no row for HiveMQ Enterprise Edition, Edge or Cloud. This page sets out what that proves, what the extension does, and where a plant gets caught. It sits under the HiveMQ unified namespace page in the HiveMQ cluster. Our page on Solace and Sparkplug B explains the protocol’s mechanics, so we do not repeat them.
What the Eclipse list shows for HiveMQ Sparkplug
| Question | What the sources show |
|---|---|
| Is HiveMQ listed? | Yes, three rows: Community Edition broker, Professional Edition broker, Sparkplug Aware Extension |
| Which Sparkplug version, which product version, what date? | None shown on the page as we read it |
| Is Enterprise Edition, Edge or Cloud listed? | No row for any of them. Whether the Professional row covers Enterprise or Cloud is not stated |
| Does HiveMQ claim compatibility itself? | Yes: its Sparkplug page calls the broker “a fully Sparkplug compatible broker as defined by the latest Sparkplug 3.0 specification” and links a certification guide. It does not say it holds a formal certification |
| Is Sparkplug 3.0 a standard? | Yes: announced by Eclipse on 7 November 2023 as an international standard that “will also be known as ISO/IEC 20237” |
Reading it. The list is evidence that HiveMQ submitted test results for those products. It is not evidence for the edition you plan to buy. A plant on HiveMQ Enterprise should ask HiveMQ in writing which edition and version passed, and run the Sparkplug test kit against its own build.
Who speaks for HiveMQ at Eclipse. The approved minutes of the Sparkplug Steering Committee for 4 June 2026 list Magnus McCune as main representative for HiveMQ among the delegates, alongside Chevron, Inductive Automation, Cirrus Link, Opto 22, Flow Software and Autosol. The minutes say quorum requires at least 4 members out of 8. The Eclipse Sparkplug home page also carries a quote from HiveMQ co-founder Dominik Obermaier. HiveMQ’s own Sparkplug page does not state that it is a member, and we could not confirm its membership tier.
The HiveMQ Sparkplug Aware Extension
The extension’s README describes three narrow behaviours.
- Birth certificates are kept. It stores NBIRTH and DBIRTH messages as they pass through and republishes them as retained messages under
$sparkplug/certificates/namespace/group_id/NBIRTH/edge_node_id, and.../DBIRTH/edge_node_id/device_idfor devices. A host that starts late can read them instead of asking every node to rebirth. - NDEATH can be re-stamped. It may replace the NDEATH timestamp with the UTC time the broker attempts delivery.
- Normal broker behaviour continues. Nothing else changes.
It is open source under Apache 2.0 and requires Java 21. The README states no edition requirement and no limitations. HiveMQ’s extension list describes it as adding the optional features needed for Sparkplug 3.0 compatibility certification. The README does not mention STATE, the retained host-status message, so do not assume the extension manages it.
Birth and death on a HiveMQ broker
HiveMQ’s April 2024 operational-behaviour post describes generic Sparkplug behaviour, not a HiveMQ feature. A host application subscribes to spBv1.0/# and publishes its own STATE message. An edge node sets NDEATH as its will on CONNECT; if it has a primary host it waits for that host to be online before publishing NBIRTH and DBIRTH, and holds data while the host is offline. If a host loses its MQTT connection, metrics from known edge nodes are marked stale.

HiveMQ Sparkplug in Data Hub
HiveMQ says its Sparkplug module for Data Hub, hivemq-sparkplug under Data Hub > Modules in Control Center, converts Sparkplug data to JSON without writing code, per HiveMQ’s Sparkplug page, which says the module is available in the HiveMQ Platform. Per HiveMQ’s 27 November 2024 blog and that page, it also routes selected metrics to configurable topics (“Metric Fan-Out”), lets you set a topic prefix, validates against schemas with the option to drop or log non-conforming messages, and tracks invalid Sparkplug B messages. The pages we read do not say which edition includes it, and Data Hub licensing is tiered (its free mode is limited to one policy), so ask before planning around it. Our Data Hub page covers the licensing we could source.
Without the module, HiveMQ’s two-part MongoDB blog builds the same pipeline by hand: a Protobuf schema, a JSON schema, a JavaScript transformation and a data policy.
The same November 2024 blog lists Sparkplug challenges: no retained-message support, a limit of three organisational layers, and QoS 0 only. It does not say HiveMQ resolves them. Our read: the retained and QoS points describe Sparkplug’s data messages, since its STATE message is retained and its death will is QoS 1. The three-layer limit is real: group, edge node, device.
HiveMQ Sparkplug and the STATE permission pitfall
A HiveMQ community thread of 14 to 15 January 2025, also cited on the Inductive Automation forum, describes a user who could publish Sparkplug data only with the admin role. The fix was to permit the legacy topic STATE/# in addition to spBv1.0/STATE/#.
Our read: the Sparkplug 3.0 STATE topic is spBv1.0/STATE/host_id, but some primary-host clients still use the older bare STATE form. A role written only from the spBv1.0 prefix then blocks the host’s status message, and edge nodes waiting for it never publish births. When the Enterprise Security Extension or file-based roles are in play, test with the real host application before go-live. The security extension page covers roles.
Brokers not on the Eclipse list
Not being on the list does not mean a broker cannot carry Sparkplug traffic. Here is what the list and vendor documents show, as of 20 November 2026.
| Broker | On the Eclipse list | What the vendor or its documents say |
|---|---|---|
| HiveMQ | Community, Professional, Aware Extension | Calls the broker fully Sparkplug 3.0 compatible |
| Cirrus Link Chariot | Yes | Describes Chariot v2 as the first Sparkplug-aware server (vendor claim) |
| NanoMQ | Yes | Listed as NanoMQ MQTT Server |
| EMQX | No | Rule engine has Sparkplug B decode functions; Community edition support unconfirmed |
| Eclipse Mosquitto, VerneMQ | No | Not listed; we did not research a Sparkplug claim |
| Solace | No | A 2023 community post reported a passing test on one version; see our Solace page |
| AWS IoT Core | No | No official statement found; documented QoS and retained-message differences matter |
| Azure Event Grid MQTT broker | No | Microsoft said on 23 March 2026 that Sparkplug B runs natively |
We declare no winner. A plant with Ignition hosts has a different test list from one that only converts Sparkplug to JSON at the edge.
Where it gets hard
- Evidence without versions. Three list rows with no version or date. Ask which edition passed and run the test kit on your build.
- Edge is not on the list. We found no Sparkplug B publishing adapter in the Edge documentation. Confirm before designing around it.
- STATE permissions. Test roles with the real primary host, including the legacy topic.
- Retained certificates accumulate. The extension adds retained messages under
$sparkplug/certificates/. Decommission nodes cleanly and audit the retained set. - Host and node on one broker. Sparkplug assumes they share a server. How HiveMQ bridges behave with STATE is not documented in what we read; test it before a multi-site design, using our multi-site page as the starting point.
Next: HiveMQ Pulse and the 2026 suite, the modelling layer above the broker.
Frequently asked questions
Is HiveMQ Sparkplug compatible?
The Eclipse Sparkplug compatible software list, read on 20 November 2026, has three HiveMQ rows: the MQTT Broker Community Edition, the MQTT Broker Professional Edition and the Sparkplug Aware Extension. It shows no version or date for them, and no row for Enterprise, Edge or Cloud. HiveMQ also calls its broker fully compatible with Sparkplug 3.0. Ask which edition and version was tested.
What does the HiveMQ Sparkplug Aware Extension do?
Per its README, it republishes Sparkplug NBIRTH and DBIRTH messages as retained messages under the $sparkplug/certificates topic prefix, so a new subscriber can read the current birth certificates, and it can replace the NDEATH timestamp with the broker's delivery time. It is open source under Apache 2.0 and requires Java 21. The README does not mention STATE.
Does HiveMQ Edge support Sparkplug B?
We could not confirm it. HiveMQ Edge is not a row on the Eclipse list, and the Edge documentation we read describes no Sparkplug B publishing adapter. Edge adapters publish JSON payloads over plain MQTT. If a plant needs Edge to emit Sparkplug B, ask HiveMQ for the version and configuration in writing.
Why does Sparkplug data fail to publish through a HiveMQ role?
A January 2025 HiveMQ community thread describes a user who could publish Sparkplug data only with the admin role. The fix was to permit the legacy topic STATE/# as well as spBv1.0/STATE/#. Permission rules written only from the spBv1.0 prefix can miss the legacy STATE form that some primary-host clients still use.
Does HiveMQ convert Sparkplug Protobuf to JSON?
HiveMQ says its Data Hub Sparkplug module converts Sparkplug data to JSON without writing code, routes selected metrics to chosen topics and validates schemas. HiveMQ's pages we read do not state which edition includes it. Without the module, HiveMQ's blogs show a hand-built pipeline using a Protobuf schema, a JSON schema, a JavaScript transformation and a data policy.
References and further reading
- Sparkplug Compatible Software · Eclipse FoundationThe live list. Check the HiveMQ rows before relying on them.
- Sparkplug Steering Committee minutes, 4 June 2026 · Eclipse Foundation
- hivemq-sparkplug-aware-extension · HiveMQ, GitHubThe README is the source for what the extension does and does not mention.
- Decoding the Operational Behavior of MQTT Sparkplug in IIoT · HiveMQ12 April 2024. Generic Sparkplug behaviour, not a product description.
- Overcoming MQTT Sparkplug Challenges for Smarter Manufacturing · HiveMQ27 November 2024. Introduces the Data Hub Sparkplug module.
- Sparkplug RBAC issues · HiveMQ CommunityThe STATE permission thread, 14 to 15 January 2025.
- Eclipse announces Sparkplug as an international standard · Eclipse Foundation