What’s new in HiveMQ Edge 2026.2

HiveMQ Edge 2026.2 introduces key enhancements to the platform. The DataHub Designer now features improved user-facing strings and user experience for configuring behavioural policies, and support has been added for ‘readOnly’ and ‘required’ properties in mapping schemas to enhance data integrity and configuration clarity.

DataHub Behavior Policy Designer UX Improvements

What It Is

HiveMQ Edge DataHub now includes an enhanced behavior model selector that helps you choose the right policy model for your use case. Instead of selecting from a plain dropdown, you'll see detailed descriptions, visual summaries, and clear guidance about each model's requirements.

The DataHub offers three behavior models, each designed for specific monitoring scenarios:

• Mqtt.events: Event interception for debugging and monitoring MQTT events with minimal configuration
• Publish.duplicate: Detects consecutive identical messages to identify potential issues or redundant data
• Publish.quota: Tracks publish counts with configurable minimum and maximum thresholds for rate limiting

Additionally, the visualization now uses color-coded states to make policy flows easier to understand at a glance:

• INITIAL states appear in blue, where your policy begins
• INTERMEDIATE states show in gray, processing stages
• SUCCESS states display in green, desired outcomes
• FAILED states appear in red, error conditions

How It Works

1. Open the DataHub Policy Designer and create or edit a behavior policy
2. Select a behavior model from the enhanced card-based selector showing descriptions and summaries
3. Configure model-specific arguments if required (the selector clearly indicates which models need additional parameters)
4. Add transitions between states, selected transitions are highlighted in the diagram for easy reference
5. Review the visual diagram below the form to understand state transitions

The visualization enhances clarity by displaying guard conditions on transition labels and highlighting your currently selected transition with a bold blue line, making complex policy flows easier to navigate.

How It Helps

Key advantages include easier model selection due to rich descriptions and summaries, with clearer policy visualization through color-coded states.Meaning users are much faster at policy configuration using highlighted selections and guard conditions, which reduces configuration errors and user frustration by explicitly showing required arguments before building transitions.

Schema Property Improvements to Safeguard Critical Data Fields

What It Is

HiveMQ Edge now respects the readOnly property from JSON Schema throughout the data mapping interface. When configuring protocol adapters or data combiners, users now see clear visual indicators for read-only fields, and the system actively prevents you from mapping data to protected properties.

This feature ensures data integrity by:

• Displaying a lock icon next to read-only properties with explanatory tooltips
• Blocking drag-and-drop operations onto read-only destination fields
• Auto-removing invalid mappings if a property becomes read-only after mapping
• Providing clear visual feedback consistent with other field validation states

How It Works

1. Open any data mapping interface (Southbound adapters, Asset mapper, or Combiner)
2. Look for the lock icon next to property names—these fields are read-only
3. Hover over the lock icon to see a tooltip explaining the read-only status
4. Try to create a mapping to a read-only property—the system displays "Read-only" instead of a drop zone
5. Existing mappings are automatically cleaned if destination properties become read-only

The read-only indicator appears in both the source and destination property lists, but only destination mappings are restricted. You can still use read-only properties as mapping sources, the protection only prevents writing to protected fields.

How It Helps

The new read-only protection feature significantly enhances configuration reliability and user experience by preventing invalid data mappings. Customers benefit from reduced troubleshooting and deployment errors through visually locked, system-reserved fields, ensuring they never accidentally map data to protected areas. This clarity also leads to a better understanding of the data model, accelerating onboarding for new team members. Furthermore, automatic validation keeps existing configurations clean and operational even if schema roles change, preventing runtime issues. By using a consistent visual language, the feature extends familiar validation patterns, making the overall mapping process more intuitive and dependable.

Additional Improvements

🛠️ Bug Fixes

• Cleanup of code issues reported by ErrorProne.

🚀 Improvements

• An extensive review of the user-facing configuration of adapters has been performed
• A new dev tool for testing the user-facing configuration of adapters has been added to the SDK
• The documentation of the protocol adapter has been completely rewritten
• HiveMQ Edge Helm chart now supports providing a custom Logback configuration for advanced logging scenarios.
• Docker containers now use JRE 25

JDK Upgrade Notice

HiveMQ Edge will be migrated to JDK v25 in April 2026.

JDK v25 provides many enhancements and improvements to the efficiency and performance of HiveMQ Edge, and enables the continuous delivery of new data operations capabilities to be brought to the product.

Get Started Today

Use the download link Get HiveMQ Edge 2026.2, 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