> 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/release-notes.md).

# Release notes

{% hint style="success" %}
MClimate is devoted to keeping our products up to date with the latest advances in the space of IoT. Thus, we push updates for the purpose of introducing New Features or in order to improve Existing Functionality. We are committed to making our products better!

We have made the option to update the firmware of your device (check improvements each version brings below) via a remote update. Learn on how to initiate the update in the [FUOTA section](/mclimate-lorawan-devices/firmware-upgrade-over-the-air-fuota.md) of our documentation.
{% endhint %}

**Would you like to receive news about new firmware updates for our products?**\
**Subscribe to our newsletter via the link below.**

{% embed url="<https://mclimate.eu/pages/firmware-updates-newsletter>" fullWidth="false" %}

### Firmware version 1.1

**Release date:** \
20 Oct 2025

* Initial firmware release


---

# 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/release-notes.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.
