What's new in HiveMQ Edge 2026.5

HiveMQ Edge 2026.5 enhances BACnet integration with device discovery capabilities and extends the LDAP-based role-based access control (RBAC) to Helm chart deployments.

BACnet Device Discovery

HiveMQ Edge now supports automatic discovery of BACnet devices and objects using the UDP Broadcast WHOIS / IAM message exchange.

How it works

Start Edge with the JAVA_OPTS="-Dbacnet.debug=true" option to have the log list all discovered devices and their objects:

    2026-03-11 21:22:52,003 INFO  - New BACnet/IP device discovered: BACnetSimulator (instance: 7509, model: BACnet ACME Dynax, address: Address [networkNumber=0, macAddress=[ac,2,0,2d,a0,c0]])
2026-03-11 21:22:52,003 INFO  - BACnet/IP Device deviceName=BACnetSimulator. modelName=IOTech BACnet Simulator, instanceNumber=7509, address=Address [networkNumber=0, macAddress=[ac,2,0,2d,a0,c0]], oid=device 7509, networkNumber=0,
2026-03-11 21:22:52,016 INFO  - +-- DeviceObject instanceNumber=7509, id=0, name=analog_input_0, type=analog-input Type, units=percent, oid=analog-input 0, currentValue=403.0
2026-03-11 21:22:52,023 INFO  - +-- DeviceObject instanceNumber=7509, id=1, name=analog_input_1, type=analog-input Type, units=percent, oid=analog-input 1, currentValue=135.0
2026-03-11 21:22:52,031 INFO  - +-- DeviceObject instanceNumber=7509, id=0, name=analog_output_0, type=analog-output Type, units=percent, oid=analog-output 0, currentValue=0.0
2026-03-11 21:22:52,034 INFO  - +-- DeviceObject instanceNumber=7509, id=1, name=analog_output_1, type=analog-output Type, units=percent, oid=analog-output 1, currentValue=1.0
2026-03-11 21:22:52,039 INFO  - +-- DeviceObject instanceNumber=7509, id=0, name=analog_value_0, type=analog-value Type, units=no-units, oid=analog-value 0, currentValue=212.0
2026-03-11 21:22:52,048 INFO  - +-- DeviceObject instanceNumber=7509, id=1, name=analog_value_1, type=analog-value Type, units=no-units, oid=analog-value 1, currentValue=188.0
  

How it helps

This feature provides immediate visibility into exactly which devices and objects are present on the BACnet network, including object types and instance numbers, network addresses, and current values. Access to this information makes it much easier to configure tags and subscriptions in the BACnet adapter without external BACnet discovery tools.

Future releases will further improve usability, including UI-based browsing of discovered objects and automated tag creation.

User Role Based Access Control for LDAP via Helm Charts

The LDAP RBAC functionality introduced in HiveMQ Edge 2026.3 is now fully supported in Helm-based deployments.

How it works

You can now configure LDAP and role mappings directly in your values.yaml file:

    adminLdap:
  enabled: true
  simplebind:
    userDn: "cn=admin"
    password: "admin"
  uid: "uid"
  rdns: "ou=people"
  directoryDescent: true
  baseDn: "dc=example,dc=org"
  userRolesEnabled: true
  userRoleAdminQuery: "(&(entryDN={userDn})(memberOf=cn=administrators,ou=groups,dc=example,dc=org))"
  userRoleSuperQuery: "(&(entryDN={userDn})(memberOf=cn=developers,ou=groups,dc=example,dc=org))"
  userRoleUserQuery: "(&(entryDN={userDn})(memberOf=cn=data-scientists,ou=groups,dc=example,dc=org))"
  

Note: The ampersand & character (logical conjunction of LDAP conditions) must be escaped as & in the YAML values. Otherwise, validation of the generated config.xml fails.

How it helps

This update enables consistent and fully automated enterprise security configuration across all deployment types and eliminates the need for manual config.xml edits in Helm environments.

Additional Improvements

🚀 Improvements

• The BACnet DeviceID can now be between 1…4194302 (as defined in the BACnet specification). It can also be set to 0 to assign a random ID automatically. The descriptions have been clarified.
• The pre-login message can now be configured via Helm. Existing parameters in the values.yaml file are now correctly applied in container deployments.

Helm Chart Updates

Helm Chart version: 0.1.27

• Image updated to HiveMQ Edge 2026.5
• LDAP RBAC configuration (userRolesEnabled, role queries) is now supported via Helm values
• Pre-Login notice is now correctly picked up from Helm values in container deployments

Advance Notice

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

This means that Java 25 (or a compatible JDK 25 distribution) will be required to run HiveMQ Edge. 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.5, 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