1.2.1-2

What's Changed

This release includes new functionality, usability improvements, and several bug fixes.

New Features

• Added a new Actions Pending binary sensor.
  The sensor turns ON whenever the integration has one or more queued write actions for the device, and returns OFF when the write queue is drained and processing is idle.

• Added a Pending attribute on writable entities.
  Writable entities (entities that support set/write operations) now expose an extra state attribute: pending: true/false. It becomes true immediately when a write is queued, and is cleared after the write has executed and a short post-execute read cycle/delay has passed—making it easy to show “value is being applied” in the UI.

• Added support for automatic device discovery during the configuration flow.

• Added Air Quality Low/Middle/High Threshold entities (disabled by default). Only available if the unit is equipped with a VOC sensor.

• Added corresponding number selectors to the set_configuration action. Since these cannot be conditionally removed based on the unit configuration, the action will raise an exception if used on units without a VOC sensor.

• Updated German translations by @divad-de.

Improvements

• Improved handling of adaptive calendar and trigger updates while operation changes are pending
• Improved coordinator update ordering for more consistent adaptive state handling
• Improved options flow persistence and reload behavior, thanks to @bdux for identifying the issue in #12

Fixes

• Fixed issue with uncontrollable controls - Thanks to @mwLabs-eu.
• Fixed cleanup during startup failures and integration unload
• Fixed stale values for unchecked options
• Fixed pending-state handling for operation changes