> For the complete documentation index, see [llms.txt](https://docs.mclimate.eu/mclimate-lorawan-devices/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mclimate.eu/mclimate-lorawan-devices/integrations/multitech.md).

# 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**.

<figure><img src="/files/TQPqQ1x0OGm4olEgUFKH" alt=""><figcaption><p>MQTT integration</p></figcaption></figure>

#### 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**.

<figure><img src="/files/HfH4zjo4y04yS5XXiGxm" alt=""><figcaption><p>Integration creation</p></figcaption></figure>

#### 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.

{% hint style="warning" %}
If the password is lost, the integration has to be deleted and recreated, and the gateway reconfigured with the new credentials.
{% endhint %}

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

<figure><img src="/files/TCDL9KcwkEV4qvplOx09" alt=""><figcaption><p>Password screen</p></figcaption></figure>

#### 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).

<figure><img src="/files/CowoPXKCmrSCGQNQE8Wo" alt=""><figcaption><p>Parameters screen</p></figcaption></figure>

### 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**:

<figure><img src="/files/mdWVQM3hdAGNSrxPxKaF" alt=""><figcaption><p>Multitech gateway parameters</p></figcaption></figure>

#### 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`

{% hint style="info" %}
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.
{% endhint %}

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.

<figure><img src="/files/49Yjp5WL8lptp6eocszC" alt=""><figcaption><p>Connectivity status pending</p></figcaption></figure>

<figure><img src="/files/QsC2mc7m9T10KI9es91j" alt=""><figcaption><p>Connectivity status connected</p></figcaption></figure>

* 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.

{% hint style="info" %}
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.
{% endhint %}

{% hint style="info" %}
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.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mclimate.eu/mclimate-lorawan-devices/integrations/multitech.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
