> 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-ht-sensor-lorawan/ht-sensor-lorawan-device-communication-protocol/d2d-communication.md).

# D2D communication

## 1. D2D communication general state

The command enables or disables D2D communication.

{% tabs %}
{% tab title="Set" %}

| Byte index | Hex value – Meaning                                                                                     |
| ---------- | ------------------------------------------------------------------------------------------------------- |
| 0          | `A9` – Command code.                                                                                    |
| 1          | <p><code>01</code> – Enables D2D.<br><code>00</code> – Disables D2D.<br><strong>(Default).</strong></p> |

**Example command:** `0xA901` – Enable D2D.
{% endtab %}

{% tab title="Get" %}

| Byte index | Sent request             | Received response                                                              |
| ---------- | ------------------------ | ------------------------------------------------------------------------------ |
| 0          | `AA` – The command code. | `AA` – The command code.                                                       |
| 1          |                          | <p><code>01</code> – D2D is enabled.<br><code>00</code> – D2D is disabled.</p> |

**Example request:** `0xAA`

**Example response:** `0xAA00` – D2D communication is disabled.
{% endtab %}
{% endtabs %}

## 2. D2D communication period

The command determines how often temperature data is being sent to the Vicki the HT is connected to. It affects the battery life, so longer periods are suggested.

{% tabs %}
{% tab title="Set" %}

| Byte index | Hex value – Meaning                                                                                                                                              |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 0          | `AB` – Command code.                                                                                                                                             |
| 1          | <p><code>XX</code> – Send period in minutes.<br>Min. allowed value – 1;<br>Max. allowed value – 8<strong>;</strong><br><strong>(Default value – 8).</strong></p> |

**Example command:** `0xAB06` – Sets 6 minutes D2D communication period.
{% endtab %}

{% tab title="Get" %}

| Byte index | Sent request             | Received response                                                    |
| ---------- | ------------------------ | -------------------------------------------------------------------- |
| 0          | `AC` – The command code. | `AC` – The command code.                                             |
| 1          |                          | Communication period, as described in the corresponding set command. |

**Example request:** `0xAC`

**Example response:** `0xAC08` – D2D communication period is 8 minutes.
{% 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-ht-sensor-lorawan/ht-sensor-lorawan-device-communication-protocol/d2d-communication.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.