OPC-UA Southbound mapper

HiveMQ Commercial Offerings
1

Hi,

I am using HiveMQ Edge (version 2025.13) to try to convert an MQTT publish to an OPC-UA message. According to the docs, this is possible with the OPC-UA adapter of HiveMQ Edge, specifically using the southbound mapping.

The docs do mention that the southbound mapping is only available with a commercial license, but the Inside Sales Representative I’ve been working with claims you can still configure it through the config.xml without the commercial license.

So, I set it up and connected successfully with the OPC-UA server, but when configuring the Southbound mapping, nothing seems to actually happen.

Here’s my config.xml for the southbound mapping:

<protocol-adapters>
        <protocol-adapter>
            <adapterId>MQTT-to-OPC-Router-server</adapterId>
            <protocolId>opcua</protocolId>
            <configVersion>1</configVersion>
            <config>
                <opcuaToMqtt>
                    <serverQueueSize>1</serverQueueSize>
                    <publishingInterval>1000</publishingInterval>
                </opcuaToMqtt>
                <security>
                    <policy>NONE</policy>
                </security>
                <tls>
                    <enabled>false</enabled>
                </tls>
                <id>MQTT-to-OPC-Router-server</id>
                <overrideUri>false</overrideUri>
                <uri>opc.tcp://OPC-router:49420/OPC-Router-OPC-UA-server</uri>
            </config>
            <tags>
                <tag>
                    <name>70B3D57BB10015A6_LogicalOpenPercentage</name>
                    <description>Logical open percentage sensor 15A6</description>
                    <definition>
                        <node>ns=2;s=Devices.70B3D57BB10015A6.OpenPercentageLogical</node>
                    </definition>
                </tag>
                <tag>
                    <name>70B3D57BB10015A6_Valid</name>
                    <description>Status valid sensor 15A6</description>
                    <definition>
                        <node>ns=2;s=Devices.70B3D57BB10015A6.Valid</node>
                    </definition>
                </tag>
            </tags>
            <southboundMappings>
                <southboundMapping>
                    <topicFilter>test/70B3D57BB10015A6/openPercentage</topicFilter>
                    <tagName>70B3D57BB10015A6_LogicalOpenPercentage</tagName>
                    <fromNorthSchema>{}</fromNorthSchema>
                </southboundMapping>
                <southboundMapping>
                    <topicFilter>test/70B3D57BB10015A6/valid</topicFilter>
                    <tagName>70B3D57BB10015A6_Valid</tagName>
                    <fromNorthSchema>{}</fromNorthSchema>
                </southboundMapping>
            </southboundMappings>
            <northboundMappings/>
        </protocol-adapter>
    </protocol-adapters>

And here’s a screenshot showing the workspace with the configured tags and showing that the OPC-UA server is connected:

image
image484×929 35.2 KB

When publishing a message to the MQTT broker under the expected topic, I don’t see anything in the logs, the OPC-UA server or on the web application.

Here are all the logs:

2025-09-10 15:12:26,060 [main] INFO com.hivemq.HiveMQEdgeMain#main - Starting HiveMQ Edge…
2025-09-10 15:12:26,104 INFO - Log Configuration was overridden by /opt/hivemq/conf/logback.xml
LOGBACK: No context given for ch.qos.logback.core.read.ListAppender[null]
2025-09-10 15:12:26,073 INFO - HiveMQ Edge Version: 2025.13
2025-09-10 15:12:26,073 INFO - HiveMQ home directory: /opt/hivemq
2025-09-10 15:12:26,120 INFO - Reading configuration file /opt/hivemq/conf/config.xml
2025-09-10 15:12:26,348 INFO - No valid license is present.
2025-09-10 15:12:26,349 INFO - No provisioning key is configured, control plane connection will not be established.
2025-09-10 15:12:26,364 INFO - HiveMQ Data Hub Module is not started because a valid license is missing.
2025-09-10 15:12:26,452 INFO - HiveMQ Edge starts with Persistence Mode: ‘IN_MEMORY’
2025-09-10 15:12:26,471 INFO - HiveMQ Data Hub Module is not started because a valid license is missing.
2025-09-10 15:12:26,509 INFO - Adding bridge hivemq-cloud
2025-09-10 15:12:26,599 INFO - Discovered 10 protocol adapter-type(s): [‘Modbus TCP’, ‘File Protocol’, ‘Simulation’, ‘Databases’, ‘ADS’, ‘OPC UA’, ‘MTConnect’, ‘Ethernet/IP CIP’, ‘S7’, ‘HTTP(s) over TCP’].
2025-09-10 15:12:26,676 INFO - Starting HiveMQ extension system.
2025-09-10 15:12:26,709 WARN -
################################################################################################################

This HiveMQ deployment is not secure! You are lacking Authentication and Authorization.

Right now any MQTT client can connect to the broker with a full set of permissions.

For production usage, add an appropriate security extension and remove the hivemq-allow-all extension.

You can download security extensions from the HiveMQ Marketplace ( HiveMQ Extensions Marketplace: MQTT Integration Made Easy ).

################################################################################################################
2025-09-10 15:12:26,711 INFO - Extension “Allow All Extension” version 1.0.0 started successfully.
2025-09-10 15:12:26,713 INFO - Refreshing adapters
2025-09-10 15:12:26,714 INFO - Refreshing data combiners
2025-09-10 15:12:26,714 INFO - DataCombiners:
2025-09-10 15:12:26,746 WARN - Unknown channel option ‘SO_REUSEADDR’ for channel ‘[id: 0xbb5edf79]’
2025-09-10 15:12:26,747 WARN - Unknown channel option ‘SO_BROADCAST’ for channel ‘[id: 0xbb5edf79]’
2025-09-10 15:12:26,753 INFO - Started MQTT TCP Listener on address 0.0.0.0 and on port 1883
2025-09-10 15:12:26,753 INFO - Started MQTT-SN UDP Listener on address 0.0.0.0 and on port 2442
2025-09-10 15:12:26,773 INFO - Found configuration for adapter MQTT-to-OPC-Router-server / opcua
2025-09-10 15:12:26,779 INFO - Starting protocol-adapter ‘MQTT-to-OPC-Router-server’.
2025-09-10 15:12:26,781 INFO - Starting OPC UA protocol adapter MQTT-to-OPC-Router-server
2025-09-10 15:12:26,784 INFO - Using default anonymous identity provider
2025-09-10 15:12:26,954 INFO - TLS is enabled: false
2025-09-10 15:12:27,077 INFO - Started WebServer with protocol ‘http’ on port 8080 in 319ms
2025-09-10 15:12:27,077 INFO - Started HiveMQ Edge in 1015ms
2025-09-10 15:12:27,181 INFO - OPC UA client of protocol adapter ‘MQTT-to-OPC-Router-server’ connected: OpcUaSession{sessionId=NodeId{ns=3, id=1528526543}, sessionName=HiveMQ Edge MQTT-to-OPC-Router-server}
2025-09-10 15:12:27,192 INFO - All monitored items synchronized successfully
2025-09-10 15:12:27,192 INFO - Client created and connected successfully
2025-09-10 15:12:27,192 INFO - Successfully started OPC UA protocol adapter MQTT-to-OPC-Router-server
2025-09-10 15:12:27,193 INFO - Successfully started adapter with id MQTT-to-OPC-Router-server
2025-09-10 15:12:27,193 INFO - Protocol-adapter ‘MQTT-to-OPC-Router-server’ started successfully.
2025-09-10 15:12:27,490 INFO - Bridge ‘hivemq-cloud’ to remote broker .s1.eu.hivemq.cloud:8883 started in 960ms.

I would really appreciate help with this. Thanks!

Liam

2

Hello ​Liam,

Southbound data flow, requires the creation of a topic filter schema as described in our documentation.
Please verify if a schema has been created for your topic filters:
​test/70B3D57BB10015A6/openPercentage
test/70B3D57BB10015A6/valid
​

Also, if you could please enable DEBUG logging in <hivemq-edge-2025.13>/conf/logback.xml:

<root level="${HIVEMQ_LOG_LEVEL:-DEBUG}">
  <appender-ref ref="FILE"/>
  <appender-ref ref="CONSOLE"/>
</root>

…and restart the Edge service.

Reproduce the publish from MQTT to OPC UA, and share with us the hivemq.log and timestamp at which the publish was executed.
A publish from the Edge client is sufficient.

​Kind regards,

​Gil

3

Hi Gil,

Thank you for your suggestion and help.

I added a topic filter as instructed:

image
image344×219 18.6 KB

image

(removed anything with /valid, so we can first focus on openPercentage)

In the Schema itself, I used the “Infer a schema” functionality. When no messages have been sent, I get the logs:

No samples were found for the requested topic 'test/70B3D57BB10015A6'.

After I’ve sent messages on that topic, it infers a schema and the log changes to:

2025-09-16 20:47:15,424 DEBUG - Starting sampling for topic: 'test/70B3D57BB10015A6'

So, it does see my messages arrive. And since it is able to infer the schema, the messages should have the right format.

Here’s the json message I’m now sending on topic test/70B3D57BB10015A6:

{"openPercentage":0}

Now this is the protocol adapter tags and southboundMappings in config.xml:


            <tags>
                <tag>
                    <name>70B3D57BB10015A6_LogicalOpenPercentage</name>
                    <description>Logical open percentage of sensor 15A6</description>
                    <definition>
                        <node>ns=2;s=Devices.70B3D57BB10015A6.OpenPercentageLogical</node>
                    </definition>
                </tag>
            </tags>
            <southboundMappings>
                <southboundMapping>
                    <topicFilter>test/70B3D57BB10015A6</topicFilter>
                    <tagName>70B3D57BB10015A6_LogicalOpenPercentage</tagName>
                    <fromNorthSchema>
                        {
                        "$schema": "http://json-schema.org/draft-07/schema#",
                        "title": "OpenPercentageWrapper",
                        "type": "object",
                        "properties": {
                            "openPercentage": {
                            "type": "integer"
                            }
                        },
                        "required": ["openPercentage"]
                        }
                    </fromNorthSchema>
                </southboundMapping>
            </southboundMappings>

With all of that said, I still don’t see any logs when I publish new messages to the broker that follow the topic.

Here’s the full debug log:

2025-09-16 20:41:34,890 [main] INFO com.hivemq.HiveMQEdgeMain#main - Starting HiveMQ Edge...
2025-09-16 20:41:34,947 INFO  - Log Configuration was overridden by /opt/hivemq/conf/logback.xml
LOGBACK: No context given for ch.qos.logback.core.read.ListAppender[null]
2025-09-16 20:41:34,899 INFO  - HiveMQ Edge Version: 2025.13
2025-09-16 20:41:34,899 INFO  - HiveMQ home directory: /opt/hivemq
2025-09-16 20:41:34,948 DEBUG - Loading modules from HiveMQ Home.
2025-09-16 20:41:34,949 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-module-modbus-2025.13-all.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-module-databases-2025.13-all.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-module-etherip-2025.13-all.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-module-file-2025.13-all.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-module-plc4x-2025.13-all.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-module-http-2025.13-all.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-module-mtconnect-2025.13-all.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-module-opcua-2025.13-all.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-commercial-modules-loader-2025.13-proguarded.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-mqtt-persistence-2025.13-proguarded.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-control-plane-2025.13-proguarded.jar.
2025-09-16 20:41:34,951 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-data-hub-2025.13-proguarded.jar.
2025-09-16 20:41:34,952 DEBUG - Found module jar in modules lib /opt/hivemq/modules/hivemq-edge-bidirectional-adapter-2025.13-proguarded.jar.
2025-09-16 20:41:34,958 INFO  - Reading configuration file /opt/hivemq/conf/config.xml
2025-09-16 20:41:35,058 DEBUG - Config can be applied
2025-09-16 20:41:35,058 DEBUG - Setting global maximum allowed connections to -1
2025-09-16 20:41:35,058 DEBUG - Setting the maximum client id length to 65535
2025-09-16 20:41:35,058 DEBUG - Setting the timeout for disconnecting idle tcp connections before a connect message was received to 10000 milliseconds
2025-09-16 20:41:35,058 DEBUG - Throttling the global incoming traffic limit 0 bytes/second
2025-09-16 20:41:35,058 DEBUG - Setting the maximum topic length to 65535
2025-09-16 20:41:35,059 DEBUG - Setting allow server assigned client identifier to true
2025-09-16 20:41:35,059 DEBUG - Setting validate UTF-8 to true
2025-09-16 20:41:35,059 DEBUG - Setting payload format validation to false
2025-09-16 20:41:35,059 DEBUG - Setting allow-problem-information to true
2025-09-16 20:41:35,059 DEBUG - Setting retained messages enabled to true
2025-09-16 20:41:35,059 DEBUG - Setting wildcard subscriptions enabled to true
2025-09-16 20:41:35,059 DEBUG - Setting subscription identifier enabled to true
2025-09-16 20:41:35,059 DEBUG - Setting shared subscriptions enabled to true
2025-09-16 20:41:35,059 DEBUG - Setting maximum qos to EXACTLY_ONCE
2025-09-16 20:41:35,059 DEBUG - Setting topic alias enabled to true
2025-09-16 20:41:35,059 DEBUG - Setting topic alias maximum per client to 5
2025-09-16 20:41:35,059 DEBUG - Setting the number of max queued messages  per client to 1000 entries
2025-09-16 20:41:35,059 DEBUG - Setting queued messages strategy for each client to DISCARD
2025-09-16 20:41:35,059 DEBUG - Setting the expiry interval for client sessions to 4294967295 seconds
2025-09-16 20:41:35,059 DEBUG - Setting the expiry interval for publish messages to 4294967296 seconds
2025-09-16 20:41:35,059 DEBUG - Setting the server receive maximum to 10
2025-09-16 20:41:35,059 DEBUG - Setting keep alive maximum to 65535 seconds
2025-09-16 20:41:35,059 DEBUG - Setting keep alive allow zero to true
2025-09-16 20:41:35,059 DEBUG - Setting the maximum packet size for mqtt messages 268435460 bytes
2025-09-16 20:41:35,060 DEBUG - Adding MQTT TCP Listener on bind address 0.0.0.0 and port 1883. Name: tcp-listener-1883.
2025-09-16 20:41:35,060 DEBUG - Adding MQTT-SN UDP Listener on bind address 0.0.0.0 and port 2442. Name: udp-listener-2442.
2025-09-16 20:41:35,062 DEBUG - No consumer registered yet
2025-09-16 20:41:35,062 DEBUG - No consumer registered yet
2025-09-16 20:41:35,062 DEBUG - No consumer registered yet
2025-09-16 20:41:35,062 DEBUG - Integrating Core Modules
2025-09-16 20:41:35,071 DEBUG - Loading the commercial modules from modules folder.
2025-09-16 20:41:35,071 DEBUG - Loading modules from HiveMQ Home.
2025-09-16 20:41:35,072 DEBUG - Instantiating Module: 'Bidirectional Module'
2025-09-16 20:41:35,072 DEBUG - Instantiating Module: 'Control Plane Module'
2025-09-16 20:41:35,073 DEBUG - Instantiating Module: 'DataHub Module'
2025-09-16 20:41:35,074 DEBUG - Instantiating Module: 'Mqtt Persistence Module'
2025-09-16 20:41:35,074 DEBUG - Start to bootstrap commercial modules.
2025-09-16 20:41:35,110 INFO  - No valid license is present.
2025-09-16 20:41:35,112 INFO  - No provisioning key is configured, control plane connection will not be established.
2025-09-16 20:41:35,124 DEBUG - Start to load commercial modules.
2025-09-16 20:41:35,124 DEBUG - Starting HiveMQ Edge MQTT Persistence.
2025-09-16 20:41:35,125 DEBUG - Started HiveMQ Edge MQTT Persistence.
2025-09-16 20:41:35,125 INFO  - HiveMQ Data Hub Module is not started because a valid license is missing.
2025-09-16 20:41:35,128 DEBUG - 490.00 MB allocated for qos 0 inflight messages
2025-09-16 20:41:35,181 DEBUG - Reading persistence file /opt/hivemq/conf/topic-filters.xml
2025-09-16 20:41:35,186 INFO  - HiveMQ Edge starts with Persistence Mode: 'IN_MEMORY'
2025-09-16 20:41:35,187 DEBUG - Set extension executor thread pool size to 10
2025-09-16 20:41:35,188 DEBUG - Set extension executor thread pool keep-alive to 30 seconds
2025-09-16 20:41:35,203 INFO  - HiveMQ Data Hub Module is not started because a valid license is missing.
2025-09-16 20:41:35,204 DEBUG - Bidirectional Adapter Module bootstrapped.
2025-09-16 20:41:35,204 DEBUG - Commercial Modules bootstrapped.
2025-09-16 20:41:35,208 DEBUG - Building initial topic tree
2025-09-16 20:41:35,221 DEBUG - Started JMX Metrics Reporting in 2ms
2025-09-16 20:41:35,235 DEBUG - Starting Remote HTTP Configuration Service..
2025-09-16 20:41:35,238 DEBUG - Updating 0 active bridges connections from 1 configured connections
2025-09-16 20:41:35,239 INFO  - Adding bridge hivemq-cloud
2025-09-16 20:41:35,239 DEBUG - Starting bridge 'hivemq-cloud'
2025-09-16 20:41:35,264 DEBUG - Starting bridge 'hivemq-cloud'
2025-09-16 20:41:35,327 DEBUG - initializing RSA key
2025-09-16 20:41:35,333 DEBUG - Discovered protocol adapter implementation com.hivemq.edge.adapters.databases.DatabasesProtocolAdapterFactory.
2025-09-16 20:41:35,334 DEBUG - Discovered protocol adapter implementation com.hivemq.edge.adapters.modbus.ModbusProtocolAdapterFactory.
2025-09-16 20:41:35,334 DEBUG - Discovered protocol adapter implementation com.hivemq.edge.adapters.mtconnect.MtConnectProtocolAdapterFactory.
2025-09-16 20:41:35,334 DEBUG - Discovered protocol adapter implementation com.hivemq.edge.adapters.etherip.EipProtocolAdapterFactory.
2025-09-16 20:41:35,335 DEBUG - Discovered protocol adapter implementation com.hivemq.edge.adapters.opcua.OpcUaProtocolAdapterFactory.
2025-09-16 20:41:35,336 DEBUG - Discovered protocol adapter implementation com.hivemq.edge.adapters.file.FileProtocolAdapterFactory.
2025-09-16 20:41:35,337 DEBUG - Discovered protocol adapter implementation com.hivemq.edge.adapters.http.HttpProtocolAdapterFactory.
2025-09-16 20:41:35,337 DEBUG - Discovered protocol adapter implementation com.hivemq.edge.adapters.plc4x.types.siemens.S7ProtocolAdapterFactory.
2025-09-16 20:41:35,337 DEBUG - Discovered protocol adapter implementation com.hivemq.edge.adapters.plc4x.types.ads.ADSProtocolAdapterFactory.
2025-09-16 20:41:35,338 DEBUG - Discovered protocol adapter implementation com.hivemq.edge.modules.adapters.simulation.SimulationProtocolAdapterFactory.
2025-09-16 20:41:35,338 INFO  - Discovered 10 protocol adapter-type(s): ['Modbus TCP', 'File Protocol', 'Simulation', 'Databases', 'ADS', 'OPC UA', 'MTConnect', 'Ethernet/IP CIP', 'S7', 'HTTP(s) over TCP'].
2025-09-16 20:41:35,365 DEBUG - Throttling incoming traffic to 0 B/s
2025-09-16 20:41:35,365 DEBUG - Throttling outgoing traffic to 0 B/s
2025-09-16 20:41:35,406 INFO  - Starting HiveMQ extension system.
2025-09-16 20:41:35,416 DEBUG - Starting extension with id "hivemq-allow-all-extension" at /opt/hivemq/extensions/hivemq-allow-all-extension
2025-09-16 20:41:35,425 WARN  -
################################################################################################################
# This HiveMQ deployment is not secure! You are lacking Authentication and Authorization.                      #
# Right now any MQTT client can connect to the broker with a full set of permissions.                          #
# For production usage, add an appropriate security extension and remove the hivemq-allow-all extension.       #
# You can download security extensions from the HiveMQ Marketplace (https://www.hivemq.com/extensions/).       #
################################################################################################################
2025-09-16 20:41:35,426 DEBUG - Simple authenticator added by extension 'hivemq-allow-all-extension'.
2025-09-16 20:41:35,427 INFO  - Extension "Allow All Extension" version 1.0.0 started successfully.
2025-09-16 20:41:35,427 DEBUG - Starting adapters
2025-09-16 20:41:35,428 DEBUG - Starting data combiners
2025-09-16 20:41:35,428 INFO  - Refreshing adapters
2025-09-16 20:41:35,428 INFO  - Refreshing data combiners
2025-09-16 20:41:35,428 INFO  - DataCombiners: []
2025-09-16 20:41:35,439 DEBUG - Starting MQTT TCP listener on address 0.0.0.0 and port 1883
2025-09-16 20:41:35,443 DEBUG - Starting MQTT-SN UDP listener on address 0.0.0.0 and port 2442
2025-09-16 20:41:35,448 WARN  - Unknown channel option 'SO_REUSEADDR' for channel '[id: 0x29702fe5]'
2025-09-16 20:41:35,448 WARN  - Unknown channel option 'SO_BROADCAST' for channel '[id: 0x29702fe5]'
2025-09-16 20:41:35,454 INFO  - Started MQTT TCP Listener on address 0.0.0.0 and on port 1883
2025-09-16 20:41:35,454 INFO  - Started MQTT-SN UDP Listener on address 0.0.0.0 and on port 2442
2025-09-16 20:41:35,455 DEBUG - finished initializing RSA key in 128ms
2025-09-16 20:41:35,463 DEBUG - Starting WebServer with protocol 'http' on port 8080
2025-09-16 20:41:35,476 DEBUG - Creating adapter 'MQTT-to-OPC-Router-server'
2025-09-16 20:41:35,477 INFO  - Found configuration for adapter MQTT-to-OPC-Router-server / opcua
2025-09-16 20:41:35,482 INFO  - Starting protocol-adapter 'MQTT-to-OPC-Router-server'.
2025-09-16 20:41:35,483 INFO  - Starting OPC UA protocol adapter MQTT-to-OPC-Router-server
2025-09-16 20:41:35,484 DEBUG - Configuring Authentication with auth false tlsEnabled false and keyPairWithChain false
2025-09-16 20:41:35,484 INFO  - Using default anonymous identity provider
2025-09-16 20:41:35,485 DEBUG - Subscribing to OPC UA client with subscriptionId: null
2025-09-16 20:41:35,497 DEBUG - Starting Remote HTTP Usage Service..
2025-09-16 20:41:35,641 INFO  - TLS is enabled: false
2025-09-16 20:41:35,641 DEBUG - Configuring Authentication
2025-09-16 20:41:35,759 INFO  - Started WebServer with protocol 'http' on port 8080 in 302ms
2025-09-16 20:41:35,760 INFO  - Started HiveMQ Edge in 869ms
2025-09-16 20:41:35,845 DEBUG - Creating new OPC UA subscription
2025-09-16 20:41:35,845 INFO  - OPC UA client of protocol adapter 'MQTT-to-OPC-Router-server' connected: OpcUaSession{sessionId=NodeId{ns=3, id=648348101}, sessionName=HiveMQ Edge MQTT-to-OPC-Router-server}
2025-09-16 20:41:35,851 DEBUG - Added monitored items: [ns=2;s=Devices.70B3D57BB10015A6.OpenPercentageLogical]
2025-09-16 20:41:35,855 INFO  - All monitored items synchronized successfully
2025-09-16 20:41:35,855 INFO  - Client created and connected successfully
2025-09-16 20:41:35,855 INFO  - Successfully started OPC UA protocol adapter MQTT-to-OPC-Router-server
2025-09-16 20:41:35,856 INFO  - Successfully started adapter with id MQTT-to-OPC-Router-server
2025-09-16 20:41:35,856 INFO  - Protocol-adapter 'MQTT-to-OPC-Router-server' started successfully.
2025-09-16 20:41:35,969 DEBUG - Bridge hivemq-cloud connected
2025-09-16 20:41:36,116 INFO  - Bridge 'hivemq-cloud' to remote broker 1a5f478c25724c948e00371c2eea8098.s1.eu.hivemq.cloud:8883 started in 852ms.
2025-09-16 20:41:51,269 DEBUG - Starting sampling for topic: 'test/70B3D57BB10015A6'
2025-09-16 20:41:51,285 DEBUG - No samples were found for the requested topic 'test/70B3D57BB10015A6'.
2025-09-16 20:41:52,302 DEBUG - No samples were found for the requested topic 'test/70B3D57BB10015A6'.
2025-09-16 20:41:56,851 DEBUG - Starting sampling for topic: 'test/70B3D57BB10015A6'
2025-09-16 20:47:15,424 DEBUG - Starting sampling for topic: 'test/70B3D57BB10015A6'

Maybe the in the on my config.xml has to refer to the schema that I already created under the topic filter?

Thanks,

Liam

4

Hello Liam,

We’re getting a bit further with setup.

The symptoms you describe involve the publish payload being sent to HiveMQ Edge; however the payload is not set to the OPC UA Server.
This suggests that we could be missing the southbound mapping (HiveMQ topic filter to the OPC UA Server destination tag).

Please read our documentation here on how to configure Southbound mapping in the GUI.

Kind regards,

Gil

5

Hello Liam,
​

To assist further, could you please let us know your feedback on the issue? We look forward to hearing from you.

Regards,
Gil

6

Hello Liam,

We are now closing this ticket since a solution to the request has been provided.
In case you still need our support , please reply back and we will be notified.

Regards,
Gil