> 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-vicki-lorawan/vicki-lorawan-device-communication-protocol/appendix-examples.md).

# Appendix (examples)

A collection of examples how to compose/decode messages.

## Command examples.

Example containing more than 1 command for sent/received server packet uses alternate colors for each command (and optional command data) for ease of understanding.

### Command example 1

 This example shows sent and received server message. The sent message contains 2 commands for Vicki:

* Read software and hardware version (Command code `0x04`);
* Set motor position to 300 steps and display digits/target temperature to 29 Celsius degrees (Command code `0x31`).

 The next received server message will contain also 2 commands from Vicki:

* The response to command code `0x04`;
* The standard periodically sent keep-alive command with its data.

**Example command:** `0x0431012C1D`

**Example response:** `0x042321011D5A78FA2C01F080`

### Command example 2

 This example shows server packet which consists of 7 Vicki commands:

* Set keep-alive period (Command code `0x02`) to 11 minutes;
* Set temperature ranges (Command code `0x08`) to 15 and 26 Celsius degrees;
* Set device operational mode (Command code `0x0D`) to online automatic control;
* Set target temperature (Command code `0x0E`) to 24 Celsius degrees.
* Get keep-alive period (Command code `0x12)`;
* Get temperature ranges (Command code `0x15`);
* Get device operational mode (Command code `0x18`).

**Example command:** `0x020B080F1A0D010E18121518`

With the next keep-alive the server will receive and the requested data from Vicki:

**Example response:** `0x120B150F1A1801011863530000008000`


---

# 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-vicki-lorawan/vicki-lorawan-device-communication-protocol/appendix-examples.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.