MQTT Client channel can't connect to our existing broker on another server

[PlantInsight]

Our IT team already runs a Mosquitto broker on a Linux server that collects data from some IoT sensors (humidity, compressor room temperature). I wanted to bring these values into Omnivex SCADA, so I created an MQTT Client channel, entered the broker's IP, port 1883, user name and password, and added a frame with the topic.
The tags never update. From my laptop I can subscribe to the same topic with an MQTT tool and see messages every few seconds, so the broker and topic are fine. Is there something special about the MQTT channel configuration?

[Technical Support]

Thanks for the detailed description. The point to check first is the broker location. In the current Omnivex SCADA documentation, the MQTT Client setup assumes that the MQTT broker and the SCADA server run on the same computer. A broker on a separate Linux server is outside that documented setup, which explains why your channel doesn't connect even though the broker itself works.
Option 1: Local broker on the SCADA server (documented setup)
1. Install Mosquitto on the SCADA server.
2. In the configuration, set the listener on port 1883 (the default) and the access settings described in the documentation.
3. Start it from an administrator Command Prompt with net start mosquitto.
4. Point the MQTT Client channel's IP and Port to this local broker.
To get the sensor data there, your IT team can configure a bridge from their Linux broker to the local one for the topics you need. This keeps their broker unchanged.
Option 2: Discuss your architecture with us
If a local broker isn't acceptable for your IT policy, please open a support request with your broker details, and we'll look at the options for your version.
Checklist once connected
- Channel: Client ID must be unique on the broker, User Name/Password as configured.
- Frame: the Topic must match exactly (topics are case-sensitive).
- Tag: check MqttSubPub (subscribe for reading), MqttTagName and Data Type.
A note on security: if you enable anonymous access on the local broker, limit the listener to the local machine or a trusted network.
Documentation: https://greensoft.ai/documentation/o...ion-protocols/