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

# MQTT

MQTT is the most popular IoT cloud protocol. YuDash IoT device acts as MQTT client which sends data to various IoT platforms in a seamless manner. Two-way communication for receiving command from cloud is also available.

**Following are the steps to use MQTT as cloud protocol.**

### Selection of MQTT As Cloud Protocol in YuDash IoT Device

<figure><img src="/files/ZxgNh1RXxgitlFWU1DU7" alt=""><figcaption></figcaption></figure>

### MQTT Credentials

Following are the settings in LYNX to configure connection to MQTT server:

<figure><img src="/files/zEnA4E8hCbG8wJQjElh5" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="230">MQTT Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>MQTT Server (Broker)</strong></td><td>The URL of MQTT broker is accessible on network. Alternately, unique IP address can be provided. This may be required for a local deployment.</td></tr><tr><td><strong>MQTT Port</strong></td><td>The IP port running MQTT server. Typically 1883</td></tr><tr><td><strong>MQTT User name</strong></td><td>Client user name for MQTT broker - Based on server, it may be blank or Access Tokens are used as user name.</td></tr><tr><td><strong>MQTT Password</strong></td><td>Client password for MQTT broker. Based on server, it may be blank or Access Tokens are given in password. </td></tr><tr><td><strong>MQTT Client Name</strong></td><td>Client name for MQTT broker. It may be simply blank is most cases, unless specified by server.</td></tr><tr><td><strong>MQTT Publish Topic</strong></td><td>The MQTT topic to publish data to. In many cases, it will contain and API name and may include unique serial number of device or variable.</td></tr><tr><td><strong>MQTT Platform Name</strong></td><td>MQTT Platform Name: Generic platform name. It is for information or display purpose only. It is not used in communication.</td></tr></tbody></table>

{% hint style="info" %}
Depending on API and authentication mechanism in MQTT broker of IoT platform, some of entries may be blank.
{% endhint %}

Following is the example for MQTT integration with popular Tago.io IoT platform:

<figure><img src="/files/EP20gNEe3BrYVCMW1sIn" alt=""><figcaption></figcaption></figure>

### MQTT with SSL/TLS secure layer

YuDash IoT devices support SSL/TLS based secure communication. Please refer to [SSL/TLS for MQTT](/device-to-cloud-api/cloud-protocols/ssl-tls.md#enabling-ssl-tls-for-mqtt) documentation for enabling the security layer.


---

# 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.yudash.com/device-to-cloud-api/cloud-protocols/mqtt.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.