For the complete documentation index, see llms.txt. This page is also available as Markdown.

Multitech

Connection between a Multitech gateway and MClimate Enterprise

In order to properly create a Multitech Conduit integration with MClimate Enterprise you need to create an MQTT gateway integration on the Enterprise platform and configure your Conduit to connect to the MClimate MQTT broker.

Unlike LNS integrations, no server or public IP address is required on your side — the gateway connects outbound to MClimate, so it works from any network, including behind NAT or a mobile connection, with no firewall changes.

The integration is bidirectional: uplinks from your MClimate devices reach the Enterprise platform, and downlink commands (settings, target temperatures, FUOTA) are delivered back through the same connection.

Creating the MQTT gateway integration

Head over to the link https://enterprise.mclimate.eu/ and log into your account. Go to the Integrations section and scroll down to MQTT gateway integrations, then click New MQTT integration.

MQTT integration

Step 1 — Create

Fill in the requested fields, where:

Username - the login your gateway will use. 3–64 characters: lowercase letters, digits and hyphens. It also becomes the topic namespace of your integration.

Note (optional) - a label to recognize the integration later, e.g. the site or gateway name.

Click Create integration.

Integration creation

Step 2 — Save the password

The generated password is displayed only throughout the creation process and cannot be recovered afterwards. Copy it and store it in a safe place now — you will enter it into the gateway in the next step.

Confirm with I have saved the password and click Continue to gateway setup.

Password screen

Step 3 — Configure gateway

The wizard now shows every value your Conduit needs. Keep this window open (you can always reopen it later via View instructions — except the password, which is never shown again).

Parameters screen

Configuring the Multitech Conduit

Log into your Conduit's web interface and open Apps → Cloud Connector. You need to fill in 2 sections, Configuration and Message Configuration. Copy each value exactly as shown in the wizard:

Multitech gateway parameters

Configuration

Server URL - mqtt://lorawan-mqtt.mclimate.eu

Client ID - mclimate-mqtt (use any ID you like)

Username - the integration username from Step 1

Password - the password you saved in Step 2

Message Configuration

Cloud Service - MQTT Broker

Encode Payload as HEX - enabled

Override Topics for All Apps - enabled

Uplink Topic - the value from the wizard, e.g. lorawan/<username>/%(gwuuid)s/%(appeui)s/%(deveui)s/up

In this example it would be lorawan/mclimate-mqtt/%(gwuuid)s/%(appeui)s/%(deveui)s/up

Downlink Topic - the value from the wizard

In this example it would be lorawan/%(gwuuid)s/down

The %(gwuuid)s, %(appeui)s and %(deveui)s placeholders are substituted automatically by the gateway itself. Copy them character-for-character — do not replace them with actual values.

Submit the changes and SAVE & APPLY them so they take effect.

Verifying the integration

After saving, the gateway connects automatically — there is nothing else to configure on the MClimate side.

  • The integration's status in the Enterprise Integrations page changes from Connection missing to Connected configuration once the gateway has delivered its first message.

Connectivity status pending
Connectivity status connected
  • Your MClimate devices appear on the platform after their first uplink (for most devices this is within their keep-alive interval, typically a few minutes).

  • Downlink commands towards the devices are enabled automatically at the same moment — no extra steps are needed.

If you have configured everything as per our instructions, the traffic from your MClimate sensors will be connected with the MClimate Enterprise platform now.

Managing the integration

  • View instructions — reopens the gateway configuration values at any time (the password is not displayed again).

  • Delete — revokes the gateway's credentials and removes the integration. The gateway disconnects immediately and its devices stop communicating with the platform. This cannot be undone; historical device data is kept.

Troubleshooting

The status stays "Connection missing". The gateway has not reached the broker yet. Verify the address and port (lorawan-mqtt.mclimate.eu, 1883), that the username and password match the wizard exactly, and that the gateway has internet access. After correcting anything, save the configuration again so the gateway reconnects.

Devices don't appear. Devices must be joined to the Conduit's built-in network server first (they will show under LoRaWAN → Devices on the gateway). Confirm the Uplink Topic was copied exactly, including the %(...)s placeholders, and that Override Topics for All Apps is enabled.

Uplinks work but downlink commands don't arrive. Save the gateway's LoRaWAN configuration once more (or restart its LoRa services) so it reconnects and re-registers for downlinks, then retry the command.

This guide assumes your MClimate devices are already provisioned on the Conduit's built-in network server (LoRaWAN → Key Management / Devices). If they are not, please refer to the official Multitech documentation, as this is out of the scope of this document.

Verified with a Multitech Conduit MTCDT-210A on mPower 6.3 with the LoRa Cloud Connector (api_version 1.1). Other Conduit models running mPower with the MQTT cloud service are configured identically.

Last updated

Was this helpful?