> 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/commands-cheat-sheet.md). # Commands cheat sheet ## Messages explanation
Command code, [hex]Firmware versionCommand nameSent from
Command code, [hex]Firmware versionCommand nameSent from
01AllKeep-aliveEnd device
02AllSet keep-alive periodServer
04AllRead device hardware and software versionServer/ End device
10AllSet network join retry periodServer
11AllSet uplink messages typeServer
12AllGet keep-alive periodServer/ End device
19AllGet network join retry periodServer/ End device
1BAllGet uplink messages typeServer/ End device
1CAllSet device radio communication watch-dog parametersServer
1DAllGet device radio communication watch-dog parametersServer/ End device
31≥2.2Set measured temperature compensationServer
32≥2.2Get measured temperature compensationServer/ End device
33≥2.2Set measured humidity compensationServer
34≥2.2Get measured humidity compensationServer/ End device
A4≥2.1LoRaWAN RegionServer/ End device
A9≥3.0Set D2D communication general stateServer
AA≥3.0Get D2D communication general stateServer/ End device
AB≥3.0Set D2D communication periodServer
AC≥3.0Get D2D communication periodServer/ End device
*Table 2* --- # 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/commands-cheat-sheet.md?ask=&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.