Skip to main content Skip to footer

Search Crosser Knowledge Base

Replacement of MQTT Broker Modules

With the release of Node version 4 we will also change the implementation of the integrated MQTT Broker to the .NET native MQTT Broker. One side effect will be that the MQTT Sub Broker and MQTT Pub Broker modules can no longer be used with that Node.

For those of you who use these modules we recommend to adjust your flows now according to the below guideline:

Replace ‘MQTT Pub Broker’ with ‘MQTT Pub Client’

Crosser MQTT modules

 

Settings on ‘MQTT Pub Client’

Keep all settings as before, set ‘Host’ to ‘localhost’ or ‘127.0.0.1’.


Crosser Example 

Replace ‘MQTT Sub Broker’ with ‘MQTT Sub Client’

Crosser Modules

 

Settings on ‘MQTT Sub Client’

Keep all settings as before, set ‘Host’ to ‘localhost’ or ‘127.0.0.1’.


Tip: Run your flow in a remote session to verify that everything works. Once done you can already update your flows now to be prepared for a flawless upgrade of the new Node.

About the author

David Nienhaus | Senior Solution Engineer

David is a Senior Solution Engineer at Crosser. He has over 10 years experience working with software integration and digitization projects for critical infrastructure.
His engineering background gives him the understanding and focus needed to solve customer use cases in the most efficient and successful way.