V2.1.1

v2.1.1 Stable and upgrade guidance

v2.1.1 Stable — published 24 October 2026. Single-level dashboards and clearer update status.

Single-level configurations no longer need a dummy second level. V2 humidity and temperature chips follow effective telemetry, including saved Options. Configured unavailable inputs remain visible; missing required mappings still prevent a verified export. Use diagnostics to distinguish these cases.

Both V2 layouts use revision 13, stamp schema 1 and generator contract 1. Existing beta.4 and RC.1 revision-13 cards remain compatible with final v2.1.1. After an approved upgrade from earlier versions, refresh the in-memory card cache, export with view_cards or dump_cards, and replace the complete saved Manual-card YAML. Exports do not replace dashboard cards automatically.

The left footer status describes UI compatibility. Separate optional HACS evidence appears at the right. ↑ Update available means the provider reports an update; routine no-update text is retained in details rather than displayed in the footer. Skipped, progress and unverified states remain explicit. Downloaded and available versions do not prove loaded code or fresh release discovery. Opening View update performs only a guarded native details handoff.

Calculated temperature trends keep the latest actual reading per minute in a one-hour window, at most 61 points. Missing minutes are not filled. The changed weighting can affect slopes and slope-dependent decisions. Provided slopes, lane priority and CO protection remain unchanged. Native Outputs text/percentages and decorated issue-summary privacy filtering are also hardened.

The existing v205_release_check name accepts the v2.1.1 beta/rc/stable line in v2.1.1. For ordinary report-only verification use write_test_exports: false and require_local_hi_snapshot: false. It rebuilds the in-memory mapping/card cache and writes a private owned report and notification, but does not replace saved cards or control outputs. Preserve fixed-name reports before recollecting. Since RC.1, self-check counts use effective saved Options; earlier packages may retain the initial setup count.

Native diagnostics custom_components.humidity_intelligence.version and integration_manifest.version provide loader evidence. The integration's own manifest-backed version alone does not prove loaded code. Keep on-disk, loaded, published, provider-reported and rendered identities separate. Download diagnostics privately and review redaction before sharing.

An approved full-package installation needs a Home Assistant restart; no configuration/entity migration is required. Restart/reload clears in-memory Stability history. Back up the previous complete package and saved cards separately. Restore compatible cards with an older backend; otherwise revision 13 may truthfully show UI differs. Restoring a package does not restore score history.

See the complete release notes and UI compatibility contract for canonical source guidance. The Wiki is a supporting manual. After updating, verify the loaded integration identity separately from the version offered by HACS.

The RC-to-Stable package delta is limited to manifest identity and packaged guidance. Runtime, services, renderer/generator and card/gallery bytes remain unchanged. The final package has its own identity; earlier beta.4 live evidence and RC source checks retain their original scope. A full package restart is still needed to load the final identity.