MQTT

The following article describes how to set up and export to your MQTT broker.

Configuration

This integration can be configured on the Export Configs tab in the Netmore Connect Portal.

For MQTT export, these fields can be configured:

URL

• Definition: Specifies the MQTT broker endpoint where the platform will publish messages.

• Components:

  • Protocol (mqtt:// or mqtts://):

    • mqtt:// is unsecured.

    • mqtts:// is secured over TLS/SSL.

  • Broker address (e.g., mq.netmoregroup.com)

  • Port (e.g., 8883 for secure MQTT, 1883 for non-secure MQTT)

• Usage: Must match the MQTT broker’s listening interface. For TLS connections, use mqtts:// with port 8883.

Topic

• Definition: The MQTT topic to which messages will be published.

• Usage: Topics define routing paths in MQTT. Devices subscribed to this topic will receive the published data.

• Best Practice: Use structured topics (e.g., device/{deviceId}/data) to support hierarchical access and filtering.

Username

• Definition: The MQTT username used for authenticating with the broker.

• Usage: Required if the broker enforces authentication. Often paired with a password (not shown in this form).

• Security Tip: Ensure this is stored securely and not exposed in client-side logs.

Certificate

• Definition: Client-side certificate used for mutual TLS authentication.

• Usage: Required if the broker enforces client certificate validation.

• Format: Usually in PEM format including the certificate and optionally the private key.

• Note: Only used when mqtts:// is selected.

Certificate Authority (CA)

• Definition: Root or intermediate CA certificate used to validate the MQTT broker’s TLS certificate.

• Usage: Ensures the client trusts the broker’s identity during TLS handshake.

• Format: PEM format.

• Required: When using self-signed or private CA-signed broker certificates.