v3.2.0-beta1
Pre-release
Pre-release
v3.2.0-beta1 -- preview release for community testing
This is a pre-release. The feedback window is open before the final v3.2.0; please install via HACS (enable "Show beta versions") or grab pollenprognos-card.js from the assets below and try the changes against your setup. Reports of edge cases on real installs would be very welcome.
Highlights
- New MSW adapter for hass-swissweather by @izacus. Adapter contributed by @r3turnNull (#212). Supports the seven allergens MeteoSwiss publishes (birch, grass, alder, hazel, beech, ash, oak), maps the categorical scale (
None/Low/Medium/Strong/Very Strong) to the card's level circles, and supports multi-station setups viaconfig_entry_id. MeteoSwiss only publishes current-day measurements, sodays_to_showis fixed at 1.
Structural changes (testing especially appreciated)
- Device-based entity discovery across most adapters (#202 / #205). PP, DWD, PEU, SILAM, Atmo, GPL and GP now resolve sensors via the Home Assistant device registry as the primary path, with platform scan and regex/selector fallbacks. Multi-instance setups route correctly without manual configuration; entity-ID renames no longer break detection. The
locationfield (andcityfor PP,region_idfor DWD) accepts aconfig_entry_id(Crockford-base32 ULID) in addition to the legacy slug for these seven adapters. Slug-based configs continue to work. Kleenex is intentionally not part of this migration. - Stale-config recovery. If a saved
config_entry_idno longer matches any discovered location (e.g. integration removed/reinstalled), the card auto-recovers instead of rendering empty. - Kleenex NA-zone fix (#206 / #207). Per-allergen DetailSensor fallback for EU/UK zones; clearer, de-duplicated warning for US/CA zones where the upstream API only returns category totals.
- Locale-agnostic device-label cleanup (#208 / #209). GPL/GP titles no longer leak the integration's " - (,)" suffix in any HA language.
What to look for
- Multi-instance setups (multiple cities/regions of the same integration) -- do they pick the right sensors?
- Legacy slug-based configs surviving into v3.2.0 -- do they still resolve?
- Editor location dropdowns -- correct labels, no duplicates?
- Card titles -- friendly device names, no stray suffixes?
- For Swiss users: MSW with one or more SwissWeather config entries, including renamed devices.
Reporting
If something looks off, please open an issue with:
- the integration(s) you have installed,
- whether you use the visual editor or YAML,
- a screenshot of the card and (if possible)
debug: trueconsole output.
Credits
Thanks to @r3turnNull for contributing the MSW adapter (#212), and to @izacus for the upstream hass-swissweather integration.