HiveMQ Edge 2025.5 is Released

What’s new in HiveMQ Edge 2025.5

HiveMQ Edge now supports run time configuration changes (hot reloading) when using Helm, which is crucial for ensuring that when making changes to the OT gateway functionality it doesn’t force a restart of the HiveMQ Edge deployment and subsequently temporarily stop data being collected from OT sources during the restart.

How it works

Step 1: Install HiveMQ Edge using Helm

To get started, run the following Helm command:

helm install edge hivemq/hivemq-edge

You should see output similar to:

NAME: edge
LAST DEPLOYED: Mon Mar 31 18:08:41 2025
NAMESPACE: default
STATUS: deployed
REVISION: 1

Step 2: Verify HiveMQ Edge Startup

Use kubectl logs to follow the startup process:

kubectl logs -f hivemq-edge-0

Once the following log message appears, HiveMQ Edge has started successfully:

INFO com.hivemq.HiveMQEdgeMain#main - Started HiveMQ Edge in 2687ms

Step 3: Access the HiveMQ Edge UI

To access the UI, forward the local port to the pod:

kubectl port-forward hivemq-edge-0 8080:8080

Then open your browser and navigate to http://localhost:8080. On the Protocol Adapters page, you’ll notice that no adapters are installed by default.

Step 4: Add a Protocol Adapter at Runtime

You can dynamically add protocol adapters without restarting HiveMQ Edge. Simply define your adapter configuration (e.g., in config.xml) and apply it with:

helm upgrade edge hivemq/hivemq-edge -f values.yaml --set-file config=config.xml

HiveMQ Edge automatically detects changes and integrates new configurations at runtime. The logs will show output like:

INFO com.hivemq.configuration.reader.ConfigFileReaderWriter#readConfigFromXML - Reading configuration file /opt/hivemq/conf-k8s/config.xml
INFO com.hivemq.bridge.BridgeService#updateBridges - Refreshing bridges []
INFO com.hivemq.protocols.ProtocolAdapterManager#refresh - Refreshing adapters
INFO com.hivemq.protocols.ProtocolAdapterManager#createAdapterInternal - Found configuration for adapter simulation / simulation
INFO com.hivemq.protocols.ProtocolAdapterManager#start - Starting protocol-adapter 'simulation'.
INFO com.hivemq.protocols.ProtocolAdapterManager#lambda$start$9 - Protocol-adapter 'simulation' started successfully.
INFO com.hivemq.combining.runtime.DataCombinerManager#refresh - Refreshing data combiners
INFO com.hivemq.combining.runtime.DataCombinerManager#refresh - DataCombiners: []

Step 5: Verify Adapter Installation

Reload the Protocol Adapters page in the UI to confirm the successful installation of the new adapter.

Note: Some configuration options cannot be changed at runtime. For details on which settings are hot-reloadable, please refer to the HiveMQ Edge documentation.

How it helps

Centralized runtime configuration changes for adapters, tags, and topics empower Kubernetes users deploying HiveMQ Edge to modify data collection and governance settings in real time without disrupting existing processes. This ensures uninterrupted data flow while HiveMQ Edge continues collecting, computing, and publishing data seamlessly during configuration updates, significantly reducing the risk of data loss.

This capability eliminates the reliance on planned maintenance windows or downtime for configuration changes. It enables on-the-fly adjustments, accelerating access to operational data and unlocking faster realization of insights and benefits from that data.

Additional Improvements

• Improved toast notification handling to prevent duplicate messages in the GUI
• Fixed an issue where the paginated table displayed no data under certain conditions
• Styled the primary key for improved visibility in the tabular summary
• Redesigned the Combiner Mapping Editor for better usability and clarity
• Fixed an issue where combiner toast notifications could not be closed
• Added validation checks to ensure only valid combiners can be created
• Enhanced the visual identity of combiners in the workspace for easier recognition
• Fixed a bug preventing Data Hub transformation scripts from modifying the retain flag of messages
• Reorganized OpenAPI specifications for better structure and maintainability

Get Started Today

Use the download link Get HiveMQ Edge 2025.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