Mitsubishi Climate Proxy 2026.11.1
Fixes the HACS integration regression shipped in GitHub release 2026.11.0 (#764).
Home Assistant Core 2026.11.0 refused existing mitsubishi_climate_proxy config entries with Migration handler not found. The config flow was already at version 2 and the component had no migration handler, so the climates stayed unavailable.
async_migrate_entry now moves entries stored at version 1 to version 2. entry_id, data, options, and the entity registry are left unchanged. Home Assistant updates the entry version and modified_at only. Restart Home Assistant after installing the update.
No ESP firmware flash is required. Tag 2026.11.0 is unchanged. manifest.json in this release is 2026.11.1.
Downgrade
Rolling back to 2026.5.1 or 2026.5.2 is safe only before this migration has run: a failed 2026.11.0 startup does not write the entry, so it is still version 1.
After Home Assistant has started on 2026.11.1, the stored entry version is 2.
- Reinstalling 2026.11.0 still loads that entry. That package already advertises config-flow version 2, so it does not undo the migration.
- Rolling back to 2026.5.x (config-flow version 1) refuses the entry (
version 2 is higher than the current version) and the climate stays unavailable. The stored data remains readable by that code. To roll back anyway, stop Home Assistant and set eachmitsubishi_climate_proxyentry'sversionback to1in.storage/core.config_entries. Do not delete the entry.