Skip to content

v3.2.0-beta5

Pre-release
Pre-release

Choose a tag to compare

View all tags
@krissen krissen released this 11 May 20:45
v3.2.0-beta5
bfd363f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v3.2.0-beta5 -- fifth pre-release

Carries everything from v3.2.0-beta4 plus a structural refinement to the device-based discovery helper that surfaced during pre-release review of #219.

Changes since beta4

Discovery: tier 1 + tier 2 now cooperate in mixed-registry scenarios (#220)

A Codex review on the v3.2.0 release PR flagged that discoverEntitiesByDevice short-circuited as soon as tier 1 (device-identifier match) found any device. In mixed-registry scenarios -- where some integration devices have proper identifiers metadata but others do not -- entities from the un-tagged devices were silently dropped, even though their entry.platform was correct and tier 2 would otherwise have found them.

The helper now does a single pass over hass.entities:

  • Entities whose device matched tier 1 (identifiers tagged) are classified via the relaxed tier-1 classifier.
  • Remaining entities whose entry.platform matches are classified via the strict tier-2 classifier.
  • No entity is offered to both classifiers, so the strict classifier never second-guesses a relaxed tier-1 result.

tierUsed still reports the primary mechanism (1 if tier 1 contributed any entity, 2 if only tier 2 contributed). The behavior of all eight migrated adapters (PP, DWD, PEU, SILAM, Atmo, GPL, GP, MSW) is functionally unchanged in well-tagged setups; the difference shows up only when an integration has inconsistent device-identifier metadata.

Three new contract tests cover the mixed-registry top-up, no-reclassification of tier-1 entities, and merging tier-1 + tier-2 entities into the same config_entry_id bucket.

Testing welcome

If you run any of the eight migrated adapters and have noticed sensors going missing after an integration update or device rename, this beta is the one to try. As before, multi-station / multi-city setups, renamed devices, and removed-then-readded integrations are particularly interesting scenarios.

HACS: enable "Show beta versions" and update; or grab pollenprognos-card.js from the release assets below.

Feedback window: open until v3.2.0 final.

The v3.2.0-beta3 release notes cover the full feature set (MSW adapter, device-discovery rollout, PEU level-name cleanup, Kleenex NA-zone handling, GPL/GP label normalization, DWD prefixed entity IDs, editor dropdown sort, per-scale i18n keys).

Assets 3
Loading