HiveMQ Edge OPC-UA: Data Flow Stops After Reconnect
Problem
Data stops flowing through HiveMQ Edge after an OPC-UA connection reconnect event. This issue can occur when the OPC-UA adapter experiences a disconnection and subsequent reconnection to the OPC-UA server, resulting in no data being published to MQTT topics despite the connection appearing to be re-established.
Affected Product
Product: HiveMQ Edge
Component: OPC-UA Protocol Adapter
Resolved In: HiveMQ Edge 2025.12
Solution
Immediate Resolution
Upgrade to HiveMQ Edge version 2025.15 or later, which includes a fix for the OPC-UA reconnect issue where data stopped flowing.
Upgrade Steps
Download HiveMQ Edge 2025.15 from the official HiveMQ releases page
Stop your current HiveMQ Edge instance
Back up your existing configuration files
Replace the HiveMQ Edge binary with version 2025.15
Restart HiveMQ Edge
Verify that data flow resumes after OPC-UA reconnection events
Verification
After upgrading, verify the fix by:
Monitoring your OPC-UA adapter connections in the HiveMQ Edge web interface
Simulating a connection interruption to the OPC-UA server
Confirming that data flow resumes automatically after reconnection
Checking MQTT topic subscriptions to ensure messages are being published
Root Cause
This was a known bug in HiveMQ Edge versions prior to 2025.12 where the OPC-UA adapter failed to properly resume data collection and publishing after a reconnection event to the OPC-UA server.
Prevention and Best Practices
Version Management
Keep HiveMQ Edge updated to the latest stable version to benefit from bug fixes and improvements
Subscribe to HiveMQ release notifications to stay informed about critical updates
Test new versions in a non-production environment before deploying to production
Additional Resources
Note: This issue was resolved in HiveMQ Edge 2025.15. If you experience similar issues after upgrading, please contact HiveMQ Support.
Important: HiveMQ Edge will migrate to JDK v21 on October 1, 2025. Versions released on or after this date will require Java Runtime Environment v21 or higher. Note that this change removes support for 32-bit CPU architectures.