> 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/updating-firmware.md).

# Updating Firmware

Starting with Aranet Home app version v2.0, a firmware update can be done as follows:

{% columns %}
{% column valign="middle" %}
Locate the sensor you need to perform the update on. Then click on the three-dot icon and find *Device Settings.*

Scroll down and find the *Firmware Update* option and press it.

In the next window, if there is an update, you will be able to perform one. If not, then a message *Up to date* will be displayed.
{% endcolumn %}

{% column %}

<div data-with-frame="true"><figure><img src="https://3323570029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsryVHhsQqwlIEVjGZzRx%2Fuploads%2FhAKzmMCb56oWGaO2DO1y%2FWhatsApp%20Video%202026-10-14%20at%2014.03.13.gif?alt=media&amp;token=2d4b0afc-76a8-4d4b-88d5-afef7c4fc697" alt="" width="135"><figcaption></figcaption></figure></div>
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
Sometimes there might be an issue where the sensor is stuck during some operation, for example, a firmware upgrade.
{% endhint %}

If you are stuck in the update process, it is advised to open the Aranet Home app and try to add a new sensor. In most cases, this sensor will be discovered, paired back to the app, and working again. If the issue still persists, please contact <support@aranet.com> or refer to the information in another topic: [Firmware Update Issues](https://help.aranet.com/aranet4/aranet4-home/manuals-and-firmware/firmware-update-issues.md)


---

# 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/updating-firmware.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.
