> For the complete documentation index, see [llms.txt](https://help.aranet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aranet.com/aranet4/aranet4-home/manuals-and-firmware/firmware-changelog.md).

# Firmware Changelog

Aranet4 Home

{% updates format="full" %}
{% update date="2025-05-08" %}

## v2.0.7

* Initial custom threshold values now match default threshold values.
* PRO versions can now disable screen refresh and measurement display.
* Added platform support for the mioty protocol on PRO versions.
  {% endupdate %}

{% update date="2025-03-18" %}

## v1.5.44

* Improved display driver stability.
* Improved GUI: added sensor ID on screen.
  {% endupdate %}

{% update date="2024-08-26" %}

## v1.4.19

* Improved battery life
* Improved new battery detection in low battery state
  {% endupdate %}

{% update date="2023-11-28" %}

## v1.4.14

* Optimized memory management to obtain up to 30 days of on-device data history.
* Introduced CO₂ on-demand measurement for all sensor HW types.
* Fixed Bluetooth extended range functionality to support all sensor HW types.
  {% endupdate %}

{% update date="2023-06-06" %}

## v1.3.5

* Introduced CO₂ on-demand measurement support.
  {% endupdate %}

{% update date="2022-10-12" %}

## v1.2.0

* New Bluetooth service UUID.
* Measurement data included in Bluetooth advertising packet.
  {% endupdate %}

{% update date="2021-10-13" %}

## v0.4.10

* Reduced consumption of LoRa radio for PRO version HW.
* CO₂ sensor intermittent read failure fixed.
* Sensor ID shown on screen for PRO version HW.
  {% endupdate %}
  {% endupdates %}


---

# 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://help.aranet.com/aranet4/aranet4-home/manuals-and-firmware/firmware-changelog.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.
