> 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/set-led-behavior.md).

# Set LED behavior

This command controls the LEDs on the top cover of the device. You can select any of the 4 and adjust its light pattern and the time it is on for.

{% 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>02 – The command code</td></tr><tr><td>1</td><td><em>XX – LED ID</em><br>00 - LED responsible for Open<br>01 - LED responsible for Close<br>02 - LED responsible for Leakage<br>03 - LED responsible for Flood</td></tr><tr><td>2</td><td><em>XX – LED behavior</em><br>01 - ON<br>02 - Blink fast<br>03 - Blink slow<br>04 - OFF</td></tr><tr><td>3</td><td>XX - duration for the specified LED behavior in seconds. If zero, do it until next LED related command is received or the verify button is pressed.</td></tr></tbody></table>

**Example command:** 0x02020214

02\[HEX] = 02\[DEC] -> activate the Leakage LED

02\[HEX] = 02\[DEC] -> make the LED Blink fast

14\[HEX] = 20\[DEC] -> make the LED Blink for 20 seconds
{% 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/set-led-behavior.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.