Skip to main content
Version: 2.6.2

MaestroHub 2.6.2 Release Notes

MaestroHub 2.6.2 builds on 2.6.1 and completes the Sparkplug B connector by adding its inbound half: a Subscribe function that decodes protobuf payloads into a typed metric map, a Discovery tab for browsing a live Sparkplug B network, and a trigger.sparkplugb pipeline trigger that fires on incoming messages. It also fixes how connector function-test results are displayed and restores the Publish Device Data save flow. Your pipelines, connectors and dashboards from 2.6.1 continue to work unchanged.

What's New in 2.6.2​

Sparkplug B — inbound (Subscribe, Discovery & Trigger)​

Until now the Sparkplug B connector could only publish device data. 2.6.2 adds the listening side, so MaestroHub can consume a Sparkplug B network end to end.

  • Subscribe function — A passive listener that decodes Sparkplug B protobuf payloads into a typed metric map at the connection boundary, before they reach your pipeline. Aliases are resolved from NBIRTH/DBIRTH messages, scoped per group and edge node so two devices sharing an alias number never cross-contaminate. Scope the subscription by group / edge node / device and by message type; subscribing to your own edge node needs no extra scope configuration, as connection-level defaults apply. All ten Sparkplug value types are decoded (scalars, DataSet, Template, and explicit sentinels for extension/unsupported types).
  • Cold start is visible, not hidden — If a publisher's birth message happened before MaestroHub subscribed, the affected metrics surface under synthetic _alias_<N> keys with an unresolvedAliases count, instead of silently appearing as an empty map.
  • Discovery tab — Browse a live Sparkplug B network the same way as the MQTT Discovery tab, with protobuf payloads decoded to a readable view rather than shown as raw binary. The tab appears on the connector form once the connection is saved.
  • Pipeline trigger (trigger.sparkplugb) — Fire a pipeline on each incoming decoded message. Deduplication is scoped per edge node, and the trigger exposes Sparkplug metadata — messageType, groupId, edgeNodeId, deviceId, seq and sparkplugTimestamp — to downstream nodes via $trigger._metadata. The trigger node is available directly on the pipeline canvas.

What's Fixed in 2.6.2​

Connectors​

  • Function test results display correctly — The connector Test action now restores the .data response envelope and uses one consistent renderer for both list and form results, so test output renders as expected instead of coming up empty or misformatted.
  • Publish Device Data saves again — The Sparkplug B ddata (Publish Device Data) function form was sending a stale form key (publishDeviceData), which the backend rejected as an invalid function type, so every save failed. The form key is aligned to ddata, and per-operation icons were added so each Sparkplug B function is visually distinct.

Distribution​

  • Lite image mirrored to Docker Hub — The MaestroHub Lite container image is now also published to Docker Hub (multi-architecture, signed) on each main release, alongside the existing registry.

Getting Started​

Download a native binary or pull the Docker image and follow the Getting Started guide to have MaestroHub running in minutes.