> 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/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="" fullWidth="false" %} ### Firmware version 2.2 **Release date:**\ 03 February 2024 * Uplink is being sent on button press. * Added possibility for temperature and humidity offset using [radio commands](/mclimate-lorawan-devices/devices/mclimate-ht-sensor-lorawan/ht-sensor-lorawan-device-communication-protocol/temperature-and-humidity-compensation.md). ### Firmware version 2.1 **Release date:**\ 5 Feb 2024 * SHTC3 H\&T sensor is now supported. * Handle properly invalid humidity values got by HDC2010 and don't discard the temperature value in such cases. * Radio command to get the LoRaWAN region implemented. ### Firmware version 2.0 **Release date:**\ 2 February 2023 * FUOTA mechanism released {% hint style="info" %} The FUOTA functionality differs from the FUOTA that's being used by the LoRa Alliance. In order to update the firmware version of devices, they should be connected to MClimate's cloud. It takes around 1500 downlinks to perform FUOTA. Due to duty-cycle limitations of the gateways, we recommend staging the FUOTA in smaller batches in case your installation is sizeable. Feel free to reach out to to acquire more details on the process. {% endhint %} * Join-retry period changed to 10m. * Removed logic for device restart after 5 unsuccessful joins. * Devices now send full configuration information with the first uplink after the Join procedure. * Bugfix: Watch-dog period for unconfirmed uplinks now correctly updating after changing the keepalive period. ### Firmware version 1.7 **Release date:**\ 9 Feb 2023 * Decrease the H\&T sensor operating temperature range to -20 to 60 Celsius and reset the sensor in case temperature outside that range is read. ### Firmware version 1.6 **Release date:**\ 23 May 2022 * Improvements on testing logic (production level). ### Firmware version 1.5 **Release date:**\ 25 Nov 2021 * Introduction of RTC time based measurement. * Improvements on the T\&H measurement logic. * Device mode check LED indication changed.. * HDC2010 sensor support. ### Firmware version 1.4 **Release date:**\ 25 Aug 2021 * Start next temp. measurement after radio Tx done event. * Periodic battery level measurement. * RGB LED test indication at power-up added. --- # 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://docs.mclimate.eu/mclimate-lorawan-devices/devices/mclimate-ht-sensor-lorawan/release-notes.md?ask=&goal= ``` `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.