Skip to content

v0.11.2 - Fan Speed Control & Reliability Improvements

Choose a tag to compare

@swingerman swingerman released this 22 Feb 21:22
142dc4f

🎉 What's New in v0.11.2

This release brings native fan speed control to Fan-Only mode, along with a set of important reliability fixes that affect dual-mode and two-stage heating systems, and resolves long-standing issues for Fahrenheit users in the configuration UI.


✨ New Features

🌀 Native Fan Speed Control

Fan-Only mode now lets you set the fan speed directly from the thermostat card.

The thermostat automatically detects whether your fan entity supports speed control and exposes the appropriate modes:

  • Preset mode fans: uses the fan's native preset modes (e.g. Low, Medium, High, Turbo)
  • Percentage fans: maps to Auto / Low / Medium / High
  • Switch-based fans: no change — continue working exactly as before

Your selected fan speed is remembered across Home Assistant restarts, so you don't need to re-set it after a reboot.


🐛 Bug Fixes

🔧 Heater & Cooler Turned Off Too Early

Fixed a bug where a running heater or cooler would switch off as soon as the temperature reached the target, completely ignoring the configured hot_tolerance / cold_tolerance.

Example: With target 20°C and hot_tolerance 0.5°C, the heater should stay on until 20.5°C — but it was turning off at exactly 20°C. This is now fixed.

🔧 Secondary Heater Wouldn't Turn Off in Dual-Stage Mode

In dual-stage (two-stage) heating setups, the secondary heater could get stuck on even after the primary heater turned off, causing the system to overheat. This is now resolved.

🌡️ Tolerance UI Fixed for Fahrenheit Users

The Runtime Tuning / Options flow (the Configure dialog) was rejecting valid small tolerance values for Fahrenheit users, showing errors like "Value X is too small".

The root cause was that tolerance fields were incorrectly using absolute temperature conversion (turning 0°C into 32°F) instead of delta scaling (0.3°C → 0.54°F). All affected fields are now fixed across the config flow and options flow.

🔧 Target Humidity Not Initialized for YAML Configs

Thermostats configured via YAML without an explicit target_humidity value could produce errors on startup. The value is now properly defaulted.


📊 By the Numbers

  • 1 new feature — native fan speed control
  • 4 bug fixes — tolerance, dual-stage, and YAML compatibility
  • 1,355 tests — all passing
  • 100% backward compatible — no configuration changes needed

🔄 Migration Guide

Drop-in replacement. No configuration changes required.

If you were previously experiencing the Fahrenheit tolerance UI bug, simply open the Configure dialog after upgrading — the fields will now accept small delta values correctly.


💝 Support This Project

If this integration makes your home more comfortable, consider supporting development:

Donate


Full Changelog: v0.11.1...v0.11.2


💙 Enjoying this integration? Help others by:

  • ⭐ Starring the repository
  • 🐛 Reporting issues you encounter
  • 💬 Sharing your success stories
  • 📣 Recommending to the Home Assistant community