v3.3.0

v3.3.0

Theming you can actually reach, tap actions, and a tenth provider.

This release folds in everything from the 3.3.0 alpha series. Headline additions: a --wac-* surface token API with transparency by default, configurable tap_action per alert row including a built-in per-alert detail pop-up, and a NINA (German civil protection) provider.

Added

• Transparency by default, plus a --wac-* surface token API. The outer <ha-card> is now the single painted surface and each alert box defaults to a transparent fill that reveals it. A translucent theme (--ha-card-background: rgba(...)) renders its alpha exactly once instead of compounding into a "solid" look on the alert bodies. A small, stable set of custom properties covers backgrounds, borders, corners, shadows and the progress wash — settable from theme YAML, card-mod, or a dashboard style: block, with no card config. Unset, every token falls back to the value the card has always used, so the default look is unchanged. (#215, #216)

  

• Per-alert detail pop-up. tap_action: { action: details } opens the tapped alert in a modal instead of expanding it in place. No add-ons, and it's genuinely per-alert for every provider: an aggregate sensor holding five warnings gives you five distinct pop-ups. Shows the whole alert — icon, title, headline, area, badges, progress bar, metadata, and the full description and instructions. Works in both layout: default and compact. (#224)

  

• Configurable tap_action per alert row. The standard Home Assistant action set on an alert row: details, more-info, navigate, url, toggle, call-service / perform-action, fire-dom-event, none. For more-info and toggle the entity resolves per tapped alert, so per-alert providers (CAP Alerts, NSW RFS) open that alert's own sensor while aggregate providers fall back to the aggregate. Setting it replaces the inline expand affordance; leaving it unset keeps today's behavior exactly. (#221)

• NINA provider (German civil protection). Reads the built-in nina integration — one binary_sensor per region per message slot, so point the card at the NINA device and slots are picked up as warnings land in them. Carries DWD weather, LHP flood, and MoWaS / KATWARN / BIWAPP civil-protection messages alike, with real CAP severity and working onset/expiry. (#240)

• Bubble-style whole-row progress fill. progressFill: background fills the entire alert row with a low-opacity tint of the alert color, growing to the current progress point behind the content, in place of the thin track. Tune or disable the wash with the --wac-progress-fill-* tokens. (#220)

• Per-phase progress decoration and icon-ring border. progressStyle takes solid / striped / shimmer / pulse per phase, and iconBorderStyle takes dashed / solid. Defaults reproduce the existing look, so nothing changes unless you ask it to. (#219)

• Tap action in the visual editor. A Tap action dropdown in the Behavior section, with "Detail pop-up" among the options; choosing Navigate or URL reveals its parameter field. perform-action and fire-dom-event payloads stay YAML-edited, and the editor preserves them untouched rather than dropping them. (#236)

• Simplified Chinese and Dutch translations, auto-detected from your Home Assistant locale. (#225, #247)

Fixed

• Editor dropdowns on Home Assistant older than 2026.02. The editor emitted only the newer component's event shape, which left every dropdown inert on older cores: the menu opened, but nothing could be picked. The card now detects the registered component set at render time and speaks to whichever is present. This covered all 18 dropdowns, not just the three that regressed originally. (#249)

Documentation

• A documentation site, at seevee.github.io/weather_alerts_card — getting started, the full configuration reference, theming, per-provider notes and pop-up recipes. (#233)
• Surface the broken-source badge and mini-map, and correct the zone-filtering scope. (#214)
• Qualify the visual-config claim with the settings that stay YAML-only. (#237)

Known limitation

NINA support has a known expiry. The nina integration is deprecating its entire entity attribute surface in HA 2026.11 (core#161882), and the replacement puts description and recommended_actions behind a nina.get_details action that a dashboard card can't call while rendering. So this adapter is correct through HA 2026.10 and stops working after. cap_alerts#66 is the route past it, reading BBK's CAP feed directly — which also carries polygons, certainty, urgency, eventCode and multilingual bodies that the integration never exposed. Follow that issue if you're on NINA.

New Contributors

• @MF-142 made their first contribution in #225
• @BaszzV made their first contribution in #247

---

Supported providers: NWS (US), BoM (Australia), MeteoAlarm (Europe), DWD (Germany), NINA (German civil protection), MeteoSwiss (Switzerland), ECCC (Canada), NSW RFS (Australian bushfire), PirateWeather, and CAP Alerts (multi-region).

Install / update via HACS → search "Weather Alerts Card".

Full changelog: v3.2.0...v3.3.0