Weather Alerts Card

seevee · July 14, 2026, 1:35am

Weather Alerts Card v3.2.0 is out

This release adds two new regions and makes multi-source setups more honest when something breaks.

MeteoSwiss (Switzerland)
If you run the hass-swissweather integration, the card now auto-detects its weather_warnings_at_<postcode> sensor and shows MeteoSwiss warnings with the usual severity colors, progress, and expandable detail.

NSW RFS — Australian bushfire alerts
New provider for the built-in NSW Rural Fire Service feed. It surfaces live bushfire, grass-fire, and hazard-reduction incidents, colored by the Australian Warning System (Emergency Warning / Watch and Act / Advice).

Because that integration creates one entity per incident (without a parent device) and those come and go, there’s a new sources config option that just collects them all for you — no need to hand-list volatile geo_location.* entities:

type: custom:weather-alerts-card
sources:
  - nsw_rural_fire_service_feed

Degraded-source indicator
If you OR several alert sensors into one card and one of them goes unavailable, the card used to quietly show “No active alerts” — hiding the fact that a source had gone dark. Now it shows a badge naming the broken source instead, and stays on screen even with hideNoAlerts by default. You can tune this with unavailableBehavior: message | compact | hide.

Also in this release

Zone filtering now reads CAP geocodes for better matching
Alerts from sensors in unknown/unavailable state are no longer dropped
Affected-area mini-map renders its geometry as a proper basemap
Bundle downleveled to ES2019 so it loads on older Android WebViews
“Ongoing” metadata verbiage for open-ended warnings

Update via HACS (search “Weather Alerts Card”). Full notes on GitHub:

As always, bug reports and feature/provider requests welcome on GitHub.

seevee · August 3, 2026, 3:45pm

v3.3.0-alpha.3 — tap actions, detail pop-ups, progress styling

There’s a lot in this one, and three of the four features started as requests in this thread. It’s a pre-release, so you’ll need “show beta versions” enabled for the card in HACS.

Release v3.3.0-alpha.3 · seevee/weather_alerts_card · GitHub

Tap an alert, open it in a pop-up

Alert rows can now do something other than expand in place. The built-in option needs no add-ons at all:

type: custom:weather-alerts-card
entity: sensor.nws_alerts_alerts
layout: compact
tap_action:
  action: details

Tapping a row opens that alert in a modal with the whole thing in it: icon, title, headline, area, badges, progress bar, metadata, description and instructions. It’s genuinely per-alert for every provider, so an aggregate sensor holding five warnings gives you five separate pop-ups rather than one shared panel listing everything.

The full Home Assistant action schema works too, so more-info, navigate, url, toggle and the rest all do what you’d expect on a row. If you use Bubble Card, navigate to a pop-up hash still works and is documented in the README.

All of it is configurable from the visual editor — there’s a Tap action dropdown in the Behavior section. That part only landed this morning, so if you tried alpha.2 and went looking for it, it genuinely wasn’t there.

@ezio.armando — the straight progress bar

You asked back in June for a straight line instead of the diagonal dashes on the active range. It’s in, and it turned into a per-phase setting rather than a single toggle, so each phase of an alert’s life can carry its own treatment:

progressStyle:
  preparation: solid
  active: solid
  ongoing: solid

solid, striped, shimmer and pulse are the options, and there’s a matching iconBorderStyle for the ring around the alert icon. Both are in the visual editor. If plain everywhere is what you were after, the config above is it.

Your second request, un-hiding dismissed alerts on a timer, hasn’t been built yet. Restore-all in the editor is still the manual answer.

Bubble-style whole-row progress

Instead of a thin progress bar, the row itself can fill:

progressFill: background

A low-opacity wash grows across the row as the alert progresses, behind the text, with the thin track hidden. It picks up the alert’s severity color and dims on expired rows. Tunable through the --wac-* tokens if the default strength isn’t right for your theme.

@dbatting — on the theme question

You asked in the very first reply whether there’d be a Home Assistant theme to match the card, and I said a proper theme was a someday item. This isn’t that, but it’s the groundwork: the card now exposes a set of --wac-* CSS tokens for its surfaces, and alert bodies default to transparent so they inherit whatever your theme is doing rather than painting their own background.

That means a translucent or glassy theme now shows through the card instead of fighting it, and you can restyle the surfaces without reaching into internal class names:

card_mod:
  style: |
    ha-card {
      --wac-card-background: transparent;
      --wac-alert-background: transparent;
      --wac-alert-border: none;
      --wac-alert-shadow: none;
    }

The full token list is in the README under Surface theming.

This is the change I’d most like eyes on. Alert bodies used to paint a solid background and now don’t, which is a visual change that affects every user regardless of config. It’s been in the alpha channel since 20 July with no reports either way, and I’d rather hear about it now than after it ships. If you’re on a translucent, glass, or heavily customised theme, a screenshot would be genuinely useful.

Also

Simplified Chinese joins English, French, Spanish, Italian and German. And there’s a documentation site now at Weather Alerts Card — the README is still the complete reference, but the site is easier to read on a phone.

What I’m asking for

If you run this alpha, I’d like to know about three things specifically: whether the card looks wrong on your theme now that backgrounds are transparent, whether the detail pop-up behaves on mobile, and whether the tap-action dropdown in the editor does what you expect. Everything else is a bonus.

Bug reports are better on GitHub than buried in the thread:

GA follows once this has had a reasonable soak.

seevee · August 7, 2026, 3:43pm

Weather Alerts Card v3.3.0 is out

Everything from the 3.3.0 alpha series is now GA, so if you turned on “show beta versions” in HACS to follow along, you can turn it back off.

The three headline features are the ones I wrote up in the alpha post above — tap actions with the built-in detail pop-up, per-phase progress styling, and the --wac-* surface tokens — and they ship unchanged. Rather than repeat all of that, here’s what’s landed since.

The per-alert detail pop-up

NINA — German civil protection. Tenth provider, reading the built-in nina integration. It carries DWD weather warnings, LHP flood warnings, and MoWaS / KATWARN / BIWAPP civil-protection messages alike, with real CAP severity and working onset and expiry times. NINA creates one binary_sensor per region per message slot, so point the card at the NINA device and warnings get picked up as they land in the slots.

One caveat I want to be upfront about: this adapter has a known expiry date. The nina integration is removing its entire entity attribute surface in HA 2026.11 (core#161882), and the replacement hides description and recommended_actions behind an action a dashboard card can’t call while it’s rendering. So the adapter is correct through HA 2026.10 and stops working after that. The route past it is cap_alerts#66, reading BBK’s CAP feed directly, which also gets you polygons, certainty, urgency, eventCode and multilingual bodies that the integration never exposed. Follow that issue if you’re on NINA.

Editor dropdowns work again on Home Assistant older than 2026.02. The visual editor was emitting only the newer selection component’s event shape, which left every dropdown inert on older cores: the menu opened, you just couldn’t pick anything. The card now detects which component set is registered at render time and talks to whichever is there. That fixed all 18 dropdowns, not just the ones that were originally reported.

Dutch joins English, French, Spanish, Italian, German and Simplified Chinese, auto-detected from your Home Assistant locale. Thanks to @BaszzV and @MF-142 for those two.

On the transparency change: it soaked in the alpha channel for a couple of weeks and nobody reported anything either way, so it’s now live for everyone. Alert bodies no longer paint their own background, which means a translucent theme renders its alpha once instead of compounding into a solid look. If your card looks off after updating, that’s the change to suspect, and I’d like to see a screenshot.

Update via HACS (search “Weather Alerts Card”). Full notes on GitHub:

There’s also a documentation site now at Weather Alerts Card if the README is getting unwieldy on a phone.

As always, bug reports and provider requests are welcome on GitHub.