> For the complete documentation index, see [llms.txt](https://docs.chirpwireless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirpwireless.io/connectors/mqtt-connector/cloud-mqtt.md).

# Cloud MQTT

The simplest MQTT path — Chirp hosts the broker, you paste the credentials into Zigbee2MQTT and go.

Cloud MQTT gives your home an MQTT connection using a broker managed by Chirp. The **broker** is the server that receives messages from your devices or bridge and passes them on. Chirp gives you its address and login details, so you do not need to run that server yourself.

For Zigbee sensors, you still need Zigbee2MQTT and a compatible coordinator in your home. Point the bridge at the supplied broker, then register and [map the devices](https://docs.chirpwireless.io/connectors/mqtt-connector/topics-and-device-routing.md) in Chirp. Creating the connection alone does not create sensor readings.

## When should I choose Cloud MQTT?

* You don't already have an MQTT broker.
* Your devices live on a home network behind NAT, and you'd rather not poke a hole through your router or rent a VPS.
* You want the simplest possible setup that works.

## How do I create a Cloud MQTT connector?

1. Open **Connectors** in Chirp's sidebar.
2. Tap **Add connector**.
3. Pick **Cloud MQTT** from the connector type list.
4. Give it a **Name** — something memorable like `Home Zigbee Hub` or `Garden Sensors`.
5. Tap **Add**.

Chirp provisions a broker endpoint and shows four values:

| Field            | What it is                                                                                                                                                                                                                                               |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Broker URL**   | The complete address of Chirp's broker for this connector. Uses TLS on port 1884 (not the default 1883). Copy it as-is — including the `mqtts://` scheme.                                                                                                |
| **Topic prefix** | Every message published through this connector must start with this path. It's how the broker keeps your data separate from everyone else's. Looks like `iot/{org}/{connection}` — two unique segments identifying your organization and this connector. |
| **Username**     | Generated by Chirp. Copy it exactly — case and characters matter.                                                                                                                                                                                        |
| **Password**     | A long random secret. **Shown once.** Copy it immediately and save it somewhere you can find later. If you close the dialog without saving the password, you'll need to rotate the credentials and reconfigure your devices.                             |

There's no recovering the original password later — Chirp doesn't keep it readable. Rotation is the only path back if you've lost it.

## How do I connect Zigbee2MQTT to a Cloud MQTT connector?

In Zigbee2MQTT's `configuration.yaml`, the four credentials map to:

```yaml
mqtt:
  base_topic: iot/{your-org-segment}/{your-connection-segment}/zigbee2mqtt
  server: mqtts://mqtt-iot.chirpwireless.io:1884
  user: {username from Chirp}
  password: {password from Chirp}
```

A few things to notice:

* **`base_topic` adds `/zigbee2mqtt` to the Topic prefix.** Z2M automatically appends `/{friendlyName}` for each device, so your living-room sensor ends up publishing to `iot/{org}/{connection}/zigbee2mqtt/LivingRoomSensor`. Chirp strips the prefix internally, leaving the device-level topic as `zigbee2mqtt/LivingRoomSensor` — which is what you'll match in the Device ID Topic field when registering the device.
* **`server` uses `mqtts://` and port 1884.** The `mqtts://` scheme tells Z2M to use TLS automatically. You don't need to provide a CA certificate — the broker uses a publicly-trusted certificate.
* **The username and password are the ones from Chirp**, not anything Z2M generates.

For the full Zigbee2MQTT setup including the Docker Compose template and `configuration.yaml` example, see [Setting up Zigbee2MQTT](https://docs.chirpwireless.io/connectors/mqtt-connector/zigbee2mqtt.md).

## How do I connect other MQTT devices to Cloud MQTT?

Anything that publishes MQTT can use the same credentials — an ESP32 you wrote firmware for, a Tasmota smart plug, an MQTT-publishing weather station. Configure the device's MQTT settings:

* **Broker / server URL:** the Broker URL value from Chirp, including the `mqtts://` scheme and port 1884.
* **Username / Password:** the credentials Chirp generated.
* **Topic to publish to:** must start with the Topic prefix. So if you'd normally publish to `weather/outside`, with Chirp you publish to `{Topic prefix}/weather/outside`.

When you register the device in Chirp, the Device ID Topic field uses the device-level portion only — Chirp strips the prefix automatically.

## How do I verify the Cloud MQTT connection?

After Z2M (or your device) starts up:

1. Open the connector's detail page in Chirp.
2. Look at **Last data received**. Within a few seconds of Z2M connecting, this field updates with a timestamp.

The first message Z2M publishes is its own bridge status (`{base_topic}/bridge/state`) — it's how you know the broker accepted the connection, even before any sensor has reported. If **Last data received** stays empty for more than a minute, see [Troubleshooting](https://docs.chirpwireless.io/connectors/mqtt-connector/troubleshooting.md).

## How do I rotate Cloud MQTT credentials?

If the password is compromised or you've lost it:

1. Open the connector in Chirp.
2. In edit mode, use the regenerate option for the password.
3. Update the password in your device or Z2M `configuration.yaml`.
4. Restart the device or Z2M.

The username and Topic prefix don't change on rotation — only the password.

## Are there limits on Cloud MQTT?

Cloud MQTT connectors are unlimited per home. If you want separate connectors for different device groups (one for the indoor Zigbee mesh, one for the garden sensors, one for the workshop), create as many as you need — each gets its own credentials and topic prefix.

Setting up the individual devices is the next stage, and [MQTT Devices](https://docs.chirpwireless.io/devices/mqtt-devices.md) guides you through it: choosing the identifier, filling in the connection fields, mapping readings to measurements, and checking that the history is retained.
