> 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/devices/mclimate-t-valve-lorawan/t-valve-lorawan-communication-protocol/enable-disable-device-flood-sensor.md).

# Enable/Disable device flood sensor

This command sets whether the flood sensor is enabled or disabled.

{% hint style="info" %}
If you don't intend to use the flood sensor functionality it is recommended to disable it to reduce battery drain and prolong operational time.
{% endhint %}

{% tabs %}
{% tab title="SET" %}
The command explanation is in the table below.

<table data-header-hidden><thead><tr><th width="137">Byte index</th><th>Hex value - Meaning</th></tr></thead><tbody><tr><td><strong>Byte index</strong></td><td><strong>Hex value - Meaning</strong></td></tr><tr><td>0</td><td>0A – The command code</td></tr><tr><td>1</td><td>XX[0] - Set it to 1 to enable device flood sensor. Set it to 0 to disable device flood sensor.<br><strong>Default value is 1 (enabled)</strong><br>XX[7:1] - Reserved</td></tr></tbody></table>

**Example command:** 0x0A00

00\[HEX] = 00\[DEC] -> Disable the flood sensor
{% endtab %}

{% tab title="GET" %}
The command explanation is in the table below.

<table data-header-hidden><thead><tr><th width="137">Byte index</th><th>Hex value - Meaning</th></tr></thead><tbody><tr><td><strong>Byte index</strong></td><td><strong>Hex value - Meaning</strong></td></tr><tr><td>0</td><td>13 – The command code</td></tr><tr><td>1</td><td>XX[0] - Set it to 1 to enable device flood sensor. Set it to 0 to disable device flood sensor.<br>XX[7:1] - Reserved</td></tr></tbody></table>

**Example response:** 0x1301

01\[HEX] = 1\[DEC] -> Enable flood sensing
{% endtab %}
{% endtabs %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mclimate.eu/mclimate-lorawan-devices/devices/mclimate-t-valve-lorawan/t-valve-lorawan-communication-protocol/enable-disable-device-flood-sensor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.