What's new in HiveMQ Edge 2026.4

HiveMQ Edge 2026.4 upgrades the Pulse Agent integration to version 2.2.4 and reinforces MQTT protocol correctness through early oversized-packet rejection.

Pulse Agent 2.2.4 Upgrade

HiveMQ Edge 2026.4 ships with Pulse Agent 2.2.4, which introduces a cleaner API for resolving MQTT topics from OPC-UA node information. The PulseAssetProvider has been refactored internally to use the new getTopicForNode() API, replacing the previous approach of manually parsing JSON properties.

Breaking change: Pulse Agent 2.2.4 (bundled with this release) is not backward compatible with older versions of HiveMQ Pulse. If you upgrade HiveMQ Edge to 2026.4 before upgrading HiveMQ Pulse, Edge will lose connectivity to Pulse. Ensure your Pulse deployment is updated to 2.2.4 or later before upgrading HiveMQ Edge.

Additional Improvements

🚀 Improvements

• MQTT Max Packet Size Early Rejection: HiveMQ Edge now rejects oversized MQTT packets as soon as the fixed header has been read, before the full payload is buffered into memory. This change improves resource efficiency under load and brings HiveMQ Edge into closer alignment with the Community Edition.

Advance Notice

Starting April 2026, HiveMQ Edge will be compiled with Java v25 (class file 69) as the target.

This means that Java 25 (or a compatible JDK 25 distribution) will be required to run HiveMQ Edge going forward. Java 25 is a Long-Term Support release, making it a solid foundation for enterprise deployments. For Edge's container distribution, JDK 25 is already the Java Runtime Environment since 2026.2. Note that Java 21 — the previous LTS — reaches the end of permissive licensing in September 2026. Upgrading now avoids last-minute disruption. We encourage users who provide their own runtime environment to plan their JDK upgrades accordingly ahead of the April release.

Java 25 is a Long-Term Support release and brings meaningful concurrency improvements to HiveMQ Edge. Virtual threads — introduced in Java 21 — are now fully supported, and structured concurrency and scoped values — finalized in Java 25 — make the internal management of concurrent tasks safer and more predictable. Together, these features allow HiveMQ Edge to handle more connections with lower resource overhead and lay the groundwork for further performance and reliability improvements in future releases.

Get Started Today

Use the download link Get HiveMQ Edge 2026.4, or find us on GitHub and Docker:

Get started by running

    docker run --name hivemq-edge --pull=always -d -p 1883:1883 -p 8080:8080 hivemq/hivemq-edge
  

Or clone our repository

    git clone git@github.com:hivemq/hivemq-edge.git
  

You may also try out our Helm Chart

    helm repo add hivemq https://hivemq.github.io/helm-charts && helm repo update