> 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-+-pir-lite/ht-+-pir-lite-device-communication-protocol/uplink-types.md).

# Uplink types

### **Set uplink messages type command explanation.**

This command is used to set the device sent uplink message type. The command is described in the table below.

<table data-header-hidden><thead><tr><th width="128.33333333333331">Byte index</th><th width="124">Bit index</th><th>Hex value – Meaning</th></tr></thead><tbody><tr><td><strong>Byte index</strong></td><td><strong>Bit index</strong></td><td><strong>Hex value – Meaning</strong></td></tr><tr><td>0</td><td>-</td><td>11 – The command code.</td></tr><tr><td>1</td><td>-</td><td><p>00 – The device sends unconfirmed uplink messages;</p><p>01 – The device sends confirmed uplink messages. <strong>Default</strong> message type for the device</p></td></tr></tbody></table>

**Example command:** 0x1101 – The server sets device uplink message type to confirmed.

### **Get uplink messages type command explanation**

<table data-header-hidden><thead><tr><th width="107">Byte index</th><th width="91">Bit index</th><th width="180">Sent request</th><th>Received response</th></tr></thead><tbody><tr><td><strong>Byte index</strong></td><td><strong>Bit index</strong></td><td><strong>Sent request</strong></td><td><strong>Received response</strong></td></tr><tr><td>0</td><td>-</td><td>1B – Command code.</td><td>1B – The command code.</td></tr><tr><td>1</td><td>-</td><td></td><td><p>00 – The device operates with unconfirmed uplinks;</p><p>01 – The device operates with confirmed uplinks.</p></td></tr></tbody></table>

**Example command:** 0x1B

**Example response:** 0x1B00 => Device uplinks are unconfirmed.


---

# 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-+-pir-lite/ht-+-pir-lite-device-communication-protocol/uplink-types.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.