Does OPC UA PubSub support multiple MQTT connections to the same broker and custom broker integration? #3208
Replies: 1 comment
-
Yes, you can create multiple pub sub connections that point to the same MQTT broker, each handling a separate topic.
The specification defines the following PubSub transport profiles [PubSub UDP UADP, PubSub MQTT UADP, PubSub MQTT JSON, PubSub AMQP UADP, PubSub AMQP JSON] and the current implementation supports the first three of them, see https://profiles.opcfoundation.org/profilefolder/320 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Type of issue
Current Behavior
Question
I'm using the OPC UA PubSub implementation in the .NET Standard stack and have two related questions:
1. Multiple MQTT Connections to the Same Broker
Can we configure multiple
PubSubConnection
entries that point to the same MQTT broker, with each handling a separate topic?Example:
PubSubConnection1
→ mqtt://broker.example.com → topic:sensor/temperature
PubSubConnection2
→ mqtt://broker.example.com → topic:sensor/humidity
Will these operate as independent MQTT connections? Or is it recommended to use a single connection with multiple WriterGroups?
2. Custom Broker Support
Is it possible to integrate a custom broker (e.g., Kafka, ZeroMQ, Redis Streams) into the PubSub model?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions