> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/changelogs/archive/changelog-24.md).

# Changelog (24)

{% hint style="info" %}
Newest first. See also Changelog [2026](/changelogs/changelog-26.md), [2025](/changelogs/archive/changelog-25.md), [2023](/changelogs/archive/changelog-23.md) and [2022](/changelogs/archive/changelog-22.md).
{% endhint %}

### <i class="fa-microchip">:microchip:</i> Cronus Zen™ firmware <a href="#firmware" id="firmware"></a>

<details open>

<summary><strong>v2.2.10</strong> — December 19, 2024</summary>

**Fixed**

* Minor bugs

</details>

<details>

<summary><strong>v2.2.9</strong> — December 18, 2024</summary>

**Added**

* Haptics detection (on/off) in `get_rumble`. Use identifier `26` for left and `27` for right

**Fixed**

* DualShock®4 output protocol issue
* Xbox® One wireless dongle issue
* Factory reset issue

</details>

<details>

<summary><strong>v2.2.8</strong> — December 4, 2024</summary>

**Added**

* Support for GameSir G7 SE

**Fixed**

* Touchpad issue
* Touchpad fingers issue
* Output protocol cycle 16 ms issue
* Rumble not resetting to `0`
* Zen Link™ Remote Play connection starting without connected devices
* Xbox® One polars issue
* PS5® legacy rumbles issue

</details>

<details>

<summary><strong>v2.2.7</strong> — October 22, 2024</summary>

**Added**

* `ZENLINK_STATUS` constant for `get_info` — returns `1` if connected, `3` if connected and linked to a PS5®

**Fixed**

* `PS5_MUTE` with `event_press` and `event_release`
* Legacy rumbles when Zenet is connected

**Improved**

* Faster flash content synchronization
* PS5® driver CPU usage

</details>

<details>

<summary><strong>v2.2.6</strong> — September 26, 2024</summary>

**Improved**

* Device synchronization

</details>

<details>

<summary><strong>v2.2.5</strong> — September 18, 2024</summary>

**Added**

* Groundwork for the upcoming Cronus Zen™ Marketplace integration

</details>

<details>

<summary><strong>v2.2.4</strong> — September 5, 2024</summary>

**Added**

* Zen Link™ support

**Fixed**

* Minor issues

</details>

<details>

<summary><strong>v2.2.3</strong> — April 22, 2024</summary>

**Fixed**

* `set_ps4_lbar` now uses BRG order, matching the Cronus player LED order and the manual
* DualShock®4 Bluetooth® lightbar
* Various bugs related to Remote Play, Bluetooth®, audio, haptics, RGB, and rumbles
* Various mouse and keyboard bugs
* Various DualSense Edge™ bugs
* Various Device Monitor bugs
* Crossover of legacy rumbles and lightbar to a DualSense™ from a console other than a PS5®
* Xbox® Share button spamming from DualSense™ and DualShock®4 gyros
* Xbox® Share button always registering as pressed on connection for Series X and the Adaptive Controller

**Improved**

* Sony to Xbox® audio crossover process when plugging in headphones

</details>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://guide.cronuszen.com/changelogs/archive/changelog-24.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 `build a script that syncs our docs to a CMS` 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.