> 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/gateway/gateway-pro/firmware-and-hardware/gateway-pros-firmware-change-log.md).

# Gateway Pro's Firmware Change Log

**1.10.8 - July 14 2026**

Bugfixes:

* Fixed Modbus serialize input registers as standard big-endian (ABCD)

**1.10.7 - July 2 2026**

Features:

* Support for 4T sensor probe custom name change
* Asia region support

Bugfixes:

* Fixed support for 128-character WiFi password length
* Fixed Gateway connection to Cloud issue after Ethernet is disconnected
* Fixed multiple Modbus client polling issues

**1.9.7 - May 12 2026**

Features:

* Introduced display brightness and orientation controls
* Show temperature for 'CO2 and Temperature' sensor
* Modbus server supports exceptions for missing measurements

Bugfixes:

* Fixed measurement rounding mismatch issues
* Fixed PM measurement display issues in GUI and MQTT
* Fixed networking issues
* Fixed Modbus server response after invalid unit ID request

**1.8.33 - March 19 2026**

* Initial firmware version


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.aranet.com/gateway/gateway-pro/firmware-and-hardware/gateway-pros-firmware-change-log.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.