> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/2023.1/toolbox/communication/mqtt/mqttstop.md).

# MQTT Stop

## Overview

![The MQTT Stop Node.](/files/YLUuLDZ79Zs44Fz5YcOR)

The **MQTT Stop Node** stops the **MQTT** connection.

It is important to note that while the **MQTT Stop Node** stops a **MQTT** connection, it may not completely finish disconnecting from said connection when the **Node** is executed. This could lead to the **Logic** attached to its **Output Pulse** to not work even though there is technically nothing wrong. In order to avoid this, it is highly suggested to use the [**On MQTT Stop Node**](/incari-studio/2023.1/toolbox/communication/mqtt/events/onmqttstop.md) instead. This way, the **Logic** will only execute once the **MQTT** connection has definitely been disconnected from. This way, it is assured that the **Logic** will execute once the connection to the **MQTT** connection has been terminated.

Again, the user must first use the **MQTT Stop Node** to close the connection. Separately, the **On MQTT Stop Node** can be used to execute the desired **Communication Logic**.

![MQTT Stop and On MQTT Stop Configuration.](/files/MVXRrV6v2Eb1xIDiO1yM)

[**Scope**](https://github.com/cgi-studio-gmbh/incari-doc/blob/2023.1/toolbox/communication/overview.md#scopes): **Project**, **Scene**.

## Attributes

![The MQTT Stop Node Attributes.](/files/z9llTxZLF4iPrZYpXOmB)

| Attribute       | Type          | Description                                        |
| --------------- | ------------- | -------------------------------------------------- |
| `Configuration` | **Drop-down** | The connection, or signal name, that will be used. |

## Inputs

| Input             | Type      | Description                                                           |
| ----------------- | --------- | --------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse** | A standard **Input Pulse**, to trigger the execution of the **Node**. |

## Outputs

| Output             | Type      | Description                                                                                                                            |
| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse** | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |

## See Also

* [**MQTT Start**](/incari-studio/2023.1/toolbox/communication/mqtt/mqttstart.md)
* [**MQTT Subscribe**](/incari-studio/2023.1/toolbox/communication/mqtt/mqttsubscribe.md)
* [**MQTT Publish**](/incari-studio/2023.1/toolbox/communication/mqtt/mqttpublish.md)


---

# 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.incari.com/incari-studio/2023.1/toolbox/communication/mqtt/mqttstop.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.