Weather Alerts Card

Weather Alerts Card

A custom Lovelace card for severe-weather alerts: severity badges, time progress bars, expandable details. Works with NWS (US), Bureau of Meteorology (Australia), MeteoAlarm (Europe), DWD (Germany), ECCC (Canada), PirateWeather, and the CAP Alerts integration โ€” auto-detected from your entity's attributes, configurable through the visual editor (no YAML required).


Note: This thread replaces the earlier NWS Alerts Card thread โ€” the card has grown beyond NWS, so the project was renamed. The underlying finity69x2/nws_alerts integration is still the recommended NWS source and the development reference integration.


Weather Alerts Card - Hero

Color themes

Four built-in themes. Left to right: severity-based (default), NWS official event colors, MeteoAlarm awareness colors, ECCC public-alert palette.

Color themes


Installation

HACS (recommended) โ€” search Weather Alerts Card in HACS โ†’ Frontend, or click the badge:

Open in HACS

Manual โ€” download weather-alerts-card.js from the latest release, copy it to config/www/, and register /local/weather-alerts-card.js as a JavaScript Module under Settings โ†’ Dashboards โ†’ Resources.


Setting up

The card ships with a visual editor โ€” most people never need to touch YAML.

  1. Install a weather-alert integration for your region (see the table below).
  2. Add Card โ†’ Weather Alerts Card on your dashboard.
  3. Pick your alert entity. For CAP Alerts, pick the device instead โ€” the card auto-discovers each per-alert sensor and re-discovers as alerts come and go.
  4. Tweak color theme, layout, sort order, and severity threshold in the editor.

Supported providers

Provider Region Integration
NWS US finity69x2/nws_alerts (HACS)
BoM Australia bremor/bureau_of_meteorology or the safepay fork (HACS)
MeteoAlarm Europe Built-in meteoalarm
DWD Germany Built-in dwd_weather_warnings
ECCC Canada michaeldavie/environment_canada_hacs (HACS) โ€” not the core integration (yet)
PirateWeather Global Pirate-Weather/pirate-weather-ha (HACS)
CAP Alerts NWS, ECCC, MeteoAlarm, WMO seevee/cap_alerts โ€” experimental integration that generates one entity per active alert; pair with device: for auto-discovery

Provider is auto-detected from entity attributes; set provider: manually if you ever need to override it.


A few representative configs

Full options table and the rest of the examples live in the README. A taste:

Most users (NWS, defaults):

type: custom:weather-alerts-card
entity: sensor.nws_alerts_alerts

Compact rows, sorted by severity, NWS official event colors:

type: custom:weather-alerts-card
entity: sensor.nws_alerts_alerts
colorTheme: nws
layout: compact
sortOrder: severity

ECCC with the official public-alert palette:

type: custom:weather-alerts-card
entity: sensor.marathon_alerts
colorTheme: eccc

CAP Alerts โ€” auto-discover every active alert under a device:

type: custom:weather-alerts-card
device: 1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d

(Use the editor's device picker so you don't have to type the device ID.)


Common questions

The card shows "No active alerts" but I expect some.
Check the underlying entity first โ€” open it in Developer Tools โ†’ States and confirm attributes contains the alert list. The card is read-only on top of that data.

Some badges are italic with a tilde, like ~Moderate.
That marks values inferred by the card from other fields (e.g. BoM doesn't ship a CAP severity, so the adapter derives one from the alert type and group). Plain non-italic badges came straight from the provider.

Auto-detect picked the wrong provider.
Set provider: explicitly โ€” nws, bom, meteoalarm, dwd, eccc, pirateweather, or cap.

ECCC core integration isn't working.
The bundled environment_canada integration doesn't currently expose alert details. Use the HACS environment_canada_hacs component until PR #164481 lands upstream.

Wall-mounted display / kiosk:
expandDetails: true shows details without a tap, hideNoAlerts: true removes the empty-state banner, and showSourceLink: false drops the link out of kiosk mode. fontSize: large (or x-large) is also worth trying at viewing distance.

NWS alert text has awkward mid-sentence line breaks.
That's the legacy 69-character teletype wrap from the NWS source feed. reformatText: true (the default) strips it while preserving paragraph breaks โ€” leave it on unless you specifically want the raw text.


Help & bug reports

  • Questions, dashboard tips, screenshots, theme requests: reply on this thread.
  • Bugs and feature requests: open an issue on GitHub โ€” they get lost in forum scroll.

Support

If the card's useful, consider tipping at Ko-fi :coffee: or โ€” better โ€” donating to The Y'all Squad, a rapid-response program providing direct aid, chainsaws, and supplies to families hit by severe weather.


GitHub: GitHub - seevee/weather_alerts_card: Weather alerts dashboard card with severity indicators and progress timelines ยท GitHub

9 Likes

This is the best looking card in my entire HA layout. I don't suppose you'd be interested in creating a Home Assistant Theme to match it, so everything else can look as clean and professional as this card does? :slightly_smiling_face:

1 Like

Thank you for the high praise!

The card primarily consumes your configured theme for all text and background colors, and severity colors in the default mode. The original goal was to minimize visual friction by respecting your theme as closely as possible. Neither the event-coded NWS theme nor the MeteoAlarm/ECCC severity themes have any real utility outside of weather alerting purposes.

With respect to the accent bar, pills, and progress bar - I briefly trialed a card-mod theme but dropped the effort, as it would require extensive per-card configuration to provide any real value. Realistically, I would need to maintain something like a card collection if I wanted to use those elements in an arbitrary entity context.

I can share the rough card-mod theme I sketched if anyone wants to tinker. I would investigate this further myself, but my partner says no until I finish a few more of my active projects. Frankly, they're right. :slight_smile:

Noting that UIX 7.4.0 now allows for local theme override for cards. So if you do publish your theme, it is now very easy to have a user apply at a card level.

1 Like

This is a very clever project, and it does remove the CSS-authoring burden I was most concerned about. The potential for state-driven coloring support via forge is particularly appealing to my vision for such a theme.

Thank you for including extensive documentation with uix; I'll have to dive more into it to see what is possible. A proper theme is still on the someday list.

1 Like

Congrats on a great card. Along with the BoM weather information for Australia, another integration for NSW, Australia could be Hazards Near Me app | NSW Government

1 Like

This is absolutely amazing, thank you! I had sucked a hacked way to show alerts with a mix of conditional and markdown cards, and this replaces 100% what I have with just a few clicks. Even the little touches like being able to hide when there are no active alerts is epic. Keep up the great work!

1 Like

Thank you, I'm glad you like it!

I must admit, I hadn't realized that fire warnings were issued separately from BOM. After checking the app at your link and poking around a bit, it looks like it uses SES and RFS feeds - BOM sources already provide the "wet" weather portions (SES is derived from BOM), and it may be possible to get the fire feed from an existing integration: nsw_rural_fire_service_feed.

There will be some quirks in supporting this integration, as the original data source does not publish useful end dates/times, so the progress bar becomes less meaningful. I do think this is still worth adding, so expect to see an implementation for my next provider pass.

EDIT: opened this issue to guide dev work. Feel free to comment with suggestions or follow along for progress.

You're most welcome! Your scenario is quite literally the situation I found myself in before I started this project. Limitations of the markdown card (particularly the details section behavior on re-renders) forced me to move to a typescript approach to get this working well enough for my own purposes.

I've mentioned before that this card began life as a markdown card, thanks in no small part to @finity's documentation guidance for NWS Alerts; some of my favorite features like hideNoAlerts and excludeEventCodes are also direct results of user feedback. This really has been a group effort in more ways than one.

Thank you for the encouragement, and thank you to everyone who has contributed feedback, bug reports, ideas, and code thus far. I greatly appreciate it!

I'm no developer, but if there's anything I can ever do to help please let me know!

1 Like

Since you asked :slight_smile:

I would love to see more screenshots of the card in the wild. I've added so many configuration options, it's hard to get a sense of how it is fitting into actual layouts; most of what I see during active development is a massive grid of cards and tens to hundreds of alerts.

I suppose I want ideas for elevating my production setup as well. What I run is pretty barebones, just one location per view with weather-radar-card underneath.

I have it set to over the top block on my weather dash here. The chip icon on the top left also shows a :warning: instead of the current condition when a weather alert is active.

1 Like

Cheers seevee, I will follow with interest.

1 Like

thanks! with this, I can replace a lot a template sensors and card visibility conditions.

as suggestions, please add the following configuration options:

  • have a straight line (not diagonal dashes) for the active range
  • allow to un-hide (manually or after x hours) manually hidden alerts
1 Like