ℹ Using release notes from: release_notes/v2.30.1.md
Highlights
v2.30.1 is a two-fix patch targeting the cover duplication flow. The source list now filters out building profile entries — previously they appeared alongside physical covers, and selecting one led to an abort with no explanation. The duplicate_configure step also had its field labels broken: the translation keys entities and azimuth didn't match the schema field names group and set_azimuth, so Home Assistant rendered the raw key strings as labels instead of the translated text. Both are fixed.
Fixed
-
Building profiles excluded from duplicate-from source list (#732, #735): New helper
_cover_entries(hass)inprofile_link.pyreturns only physical cover config entries — those whose policy reportscontrols_cover == True. Bothasync_step_userandasync_step_duplicate_selectnow call_cover_entries(hass)instead ofhass.config_entries.async_entries(DOMAIN), so building profile entries are excluded from the duplicate source list. The "Duplicate existing" menu option is also hidden when no physical cover entries exist. -
duplicate_configurefield labels corrected (#733, #736):duplicate_configure.datainen.json,de.json, andfr.jsonused keysentitiesandazimuth, but the schema fields are namedgroupandset_azimuth. Home Assistant renders the raw key as the label when the key doesn't match, so users were seeing "entities" and "azimuth" as field labels instead of the translated strings. Keys corrected togroupandset_azimuthacross all three translation files. New regression testtest_duplicate_configure_translation_keys_match_schemalocks this.
Changed
- Issue lifecycle (#737): Stable releases now close referenced issues immediately instead of waiting 14 days for reporter confirmation. Reporters can reopen a closed issue by commenting "still happening" or
/reopen.
Testing
5292 tests passing.
Compatibility
Requires Home Assistant 2026.3.0+. The companion Lovelace card (jrhubott/adaptive-cover-pro-card) is a separate repo with its own release cycle.