Skip to content

Pollen Levels 3.0.0rc3

Pre-release
Pre-release

Choose a tag to compare

View all tags
@eXPerience83 eXPerience83 released this 11 Jul 11:43
v3.0.0rc3
9da4977
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Pollen Levels 3.0.0rc3

This release candidate adds Google Maps Pollen API compliance improvements, clearer refresh failure reporting, public legal documentation, and updated repository tooling.

Highlights

  • Updated visible attribution to:
    "Google Maps — Source: Includes pollen data from Google"
  • Kept forecast attributes available in live Home Assistant state while excluding future forecast-derived attributes from Recorder persistence.
  • Limited stale Google Pollen forecast payload reuse to a maximum of 24 hours.
  • Improved "pollenlevels.force_update" so failures handled internally by Home Assistant's "DataUpdateCoordinator" are still reported.
  • Healthy locations continue refreshing when another location fails.
  • Added public Terms of Use and a Privacy Policy.
  • Expanded documentation for API-key handling, data sent to Google, Recorder persistence, and Google Maps Platform retention requirements.
  • Replaced Black with Ruff formatter for linting, import ordering, and formatting.

Manual validation

The following manual scenario was completed successfully:

  • Upgrade from "3.0.0rc2" to "3.0.0rc3" using the exact release commit.

The following scenarios were not manually repeated for this release candidate:

  • Clean installation.
  • Migration from Pollen Levels 2.x.

The v3 migration implementation was not changed between RC2 and RC3. Automated tests, Ruff validation, hassfest, HACS validation, package validation, CodeQL, Gemini review, and CodeRabbit review passed before release.

Upgrade notes

Pollen Levels 3.x uses one parent config entry per Google API key and one config subentry per location.

Before upgrading from Pollen Levels 2.x:

  • Create a complete Home Assistant backup.
  • Keep the backup until the migration and all entities have been verified.
  • Downgrading from 3.x to 2.x is not supported without restoring a backup.

This RC does not change migration behavior, entity IDs, unique IDs, device identifiers, entity count, forecast offsets, service schemas, translation keys, or the parent/subentry architecture.

Assets 3
Loading