Highlights
This maintenance release focuses on two key areas:
- Fixing a regression in remote sensor handling (issue #474).
- Improving the operating/fallback logic for hybrid and multi‑stage systems.
Remote sensor stability (fixes #474)
- Always sends the remote temperature to the Mitsubishi unit whenever a new sample is received, even if the value did not change.
- Adds a
NaNguard to ignore invalid remote temperature values instead of propagating them. - Ensures the unit keeps using the external sensor and does not silently fall back to the internal sensor just because the temperature is stable.
This addresses the behaviour where some units would revert to the internal sensor if they did not receive an updated remote temperature packet approximately every 30 seconds.
Operating / stage‑based fallback
- Refines
setActionIfOperatingToto implement a true fallback strategy:- Primary: use
currentStatus.operatingwhen the compressor is running. - Fallback: if
use_stage_for_operating_status_is enabled and the current stage is not IDLE, treat the system as actively heating/cooling (e.g. gas heating in a 2‑stage system). - Otherwise, report
IDLE.
- Primary: use
- Adds more detailed logging so you can see:
- whether
operatingis true, - whether stage‑based fallback is enabled,
- the current stage and whether it is considered active.
- whether
This makes the reported climate_action more accurate for hybrid or multi‑stage installations.
Dual setpoint examples and docs
- Cleans up and simplifies the dual setpoint example YAML files.
- Updates README and comments to better explain:
- when to enable
use_stage_for_operating_status_, - how the remote temperature integration behaves.
- when to enable
Upgrading
- No breaking changes are expected for existing configurations.
- Users relying on the remote temperature feature or stage‑based operating fallback are strongly encouraged to upgrade to v1.5.1.