< Back to all releases
umh-core
v0.44.22

v0.44.22

Improvements

  • Sparkplug B input: request_birth_on_connect now defaults to true, so secondary_active/primary bridges proactively rebirth newly seen nodes on connect. Set it to false to keep the prior behavior (ignored under secondary_passive)
  • Sparkplug B input: field descriptions and the primary-role startup log now clarify that identity.edge_node_id is the Sparkplug v3.0-compatible host_id in the STATE topic (spBv1.0/STATE/<host_id>)
  • New snowflake_put output: ports the warpstreamlabs/bento Snowflake output into benthos-umh for writing batched messages to Snowflake stages with optional Snowpipe ingestion. Supports user/password and key-pair auth, all gosnowflake compression modes, and per-message stage/Snowpipe interpolation

Fixes

  • When an FSMv2 transport worker (auth, push, or pull) was stuck in a transient-retry state, the supervisor heartbeat printed the same stale reason set on entry — for example "Desired state is running, transitioning to Starting" — instead of the live per-tick reason the worker already composes, such as "auth backoff: 42 errors (cloudflare_challenge), delay 60s". The heartbeat now surfaces the live reason within one ~10s cycle.
  • Sparkplug B input: identity.group_id now filters the MQTT subscription by default. Previously an empty subscription.groups subscribed to every Sparkplug group on the broker (spBv1.0/+/#) regardless of identity.group_id. To restore the old behavior, set subscription.groups: ["+"] explicitly
  • Sparkplug B input: bridges now request a rebirth when DATA references aliases the cache hasn't seen (typically after a bridge restart with no retained NBIRTH/DBIRTH on the broker). Previously tags surfaced as …/_historian/alias_<n> until something external triggered recovery

Preview: Write Flows

  • Write flows (preview) now take their input topics directly on the flow, with Go template support for values like {{ .location_path }}. Write flows configured on this preview before this release are not carried over and need to be re-created from the UI; read flows and connection settings are unaffected
Discuss on Discord