NWS Alerts Card

[seevee]

Update: Weather Alerts Card v2.0–v2.5

Hey folks, it’s been a minute since the last structured post. Wanted to share a big batch of updates.

The card has been renamed to Weather Alerts Card to reflect the biggest change: multi-provider support. It’s no longer NWS-only. The card now auto-detects your sensor’s provider and works with:

• NWS (National Weather Service, US) — same as before
• MeteoAlarm (EUMETNET, Europe) — including awareness-level color theming
• Bureau of Meteorology (Australia)
• PirateWeather (global coverage)

Other highlights and configurable features:

• Internationalization — the card and its editor now support English, French, and Spanish
• Alert filtering — excludeEventCodes lets you hide alert types you don’t care about
• Alert deduplication — duplicate alerts across zones are collapsed automatically
• Smart headlines — alerts show headlines with redundancy filtering so you get useful context without repetition
• Browser timezone option — useful if you travel but monitor alerts back home and want to monitor alerts for your current position using device tracking
• Source links — optional link back to the provider’s detail page for each alert

Feedback and bug reports welcome as always. If you’re using one of the new providers I’d especially love to hear how it’s working for you.

[finity]

@seevee

Browser timezone option — useful if you travel but monitor alerts back home

I’ll reiterate that the most useful use case for selecting the browser timezone option is for when/if you use a device tracker to get relevant alerts for your location when traveling. I don’t know if that is an option for the others but the NWS Alerts integration allows the use of a device tracker to get alerts.

[seevee]

You’re right, oversight on my part. Updated!

[seevee]

v2.6.0 is out with a couple of additions:

Compact layout gets some love — single-row alerts now with inline progress bars that expand on tap. Great for sidebar panels or space-constrained dashboards.

Set layout: compact in YAML or pick it from the visual editor.

The three color themes (severity, NWS official, and MeteoAlarm awareness) all work in compact mode too:

Also in this release: the entity picker now filters to only compatible alert sensors, so setup is a bit smoother.

Full changelog: v2.6.0 release

[seevee]

Also for @airbornetrooper82573: Took some time to think about how to wire this up. Your configuration led me to an automated solution for achieving this - check out v2.7.0-alpha.1:

this:

will now generate this:

Give it a shot and let me know if it works for you.

[chappy-2]

Love the card and is exactly what I was looking for. Is there any way to increase the font size of the text? It’s difficult to read on my tablets. I tried card mod, but could not get it to work. Any tricks that I am missing? Thanks!!

[seevee]

@chappy-2 You missed nothing; you did propose an excellent enhancement though! Implemented in v2.7.0-alpha.3:

Using the built-in fontSize option:

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

Using card-mod with --wac-scale for a custom value:

type: custom:weather-alerts-card
entity: sensor.nws_alerts_alerts
card_mod:
  style: |
    ha-card {
      --wac-scale: 1.3;
    }

The fontSize presets map to: small = 0.85, default = 1, large = 1.2, x-large = 1.4. With card-mod you can use any positive number.

[seevee]

v2.7.0 is out. Here’s what’s new:

Configurable font size - New fontSize option lets you scale the card up or down to fit your dashboard. Uses the --wac-scale CSS property under the hood, so it plays nicely with themes.

Hide empty state - Set hideNoAlerts: true to suppress the “No active alerts” banner entirely. Useful if you’re stacking cards and don’t want dead space when skies are clear.

Improved severity & certainty indicators - The detail view now shows data purity badge flair for severity and certainty, so you can tell at a glance whether those values came directly from the provider (flat text) or were inferred by the card (tilde + italics). Badges have also been fully localized.

Italian translations - Grazie to @fragolinux for adding full Italian localization. The card now supports English, French, Spanish, and Italian.

Full changelog: Release v2.7.0 · seevee/weather_alerts_card · GitHub

[seevee]

v2.8.1 is out. A quick update on what’s landed since v2.7.0:

New

• DWD (Deutscher Wetterdienst) adapter - If you’re in Germany, the card now natively supports DWD weather warnings alongside the existing NWS, MeteoAlarm, Bureau of Meteorology, and PirateWeather providers. The card auto-detects your entity, so just point it at your DWD sensor and it should work out of the box.
• German (de) localization - The card UI is now fully translated into German.
• Expired alert handling - Expired alerts are now hidden by default (hideExpired with toggle control) and receive a dimmed style + copy changes to distinguish them from active or in progress alerts. You shouldn’t see expired alerts from any of the supported integrations under normal circumstances; this is primarily to address cached/stale alert data.

Bug fixes

• MeteoAlarm icon fix - Icon lookup now uses the English awareness_type consistently, fixing broken icons for non-English MeteoAlarm regions.
• Shimmer animation fix - The active-alert shimmer animation now resets cleanly off-screen instead of occasionally jumping.

Upgrade via HACS as usual. Let me know if you run into anything!

[WWillig]

I just set up card v 2.8.1 (waiting for an alert to happen) the sample data appears.
When I go to card config i can not enter any information after Title. I see the drop down menu but can not select or make manual entry. I cleared cache on browser, the NWS alerts integration has been installed. Suggestions? Thanks!

[seevee]

That’s a strange problem for sure, not sure what’s going on here. I assume an entity has populated, can you share a screenshot of the card editor?

Some follow up questions:

• Are you using any custom themes?
• What version of HA are you running?

I’m noticing that the catpuccin theme I had been running has unreadable form fields since the 2026.4.0 HA update, but I can still enter text.

---

EDIT: I think I just realized one potential cause for this problem:

HA 2026.2.0 introduced the WebAwesome component system (in place of MWC), which forced all these dropdown field items to migrate from ha-list-item to ha-dropdown-item. I made a commit and completed this migration, but I hadn’t released the card on the community store yet and did not think to maintain backward compatibility.

If you’re on an older version of Home Assistant, I would highly recommend you upgrade. If that’s not possible for your setup, let me know here and I will implement backwards compatibility in my next sprint (starting tonight). I am honestly and deeply surprised that nobody else has brought this one up yet, and sorry for the oversight!

[WWillig]

Here is screen shot of code editor:

type: custom:weather-alerts-card
entity: sensor.nws_alerts_2
grid_options:
columns: full
title: NWS ALERTS

System: HA OS, Core 2026.1.3 (about to update to 2026.4.0)
Supervisor 2026.03.2
OS 17.1,
Frontend: 20260107.2
No custom themes.

could I enter the info via yaml? not sure verbiage for this.

i think it might have to do with my install although no errors popped up. I did set up zones at first then went to gps coords but I doubt that has anything to do with it since I couldn’t add info there either.
Thanks for your help, you did an awsome job with it!

[stephanschleichstr13]

A Option to hide Instructions would bei nice

[IvandaVGV]

First, I’m brand, brand new to HA, so take this with many grains of salt. I’m still on HAOS 2026.3.4, but just upgraded this card. It’s been installed and showing actual alerts for a few days (after finally realizing I mindlessly threw in a space between my two zones).

FWIW, I notice that your entity is different from mine shown here:

entity: sensor.nws_alerts_alerts

[finity]

“sensor.nws_alerts_alerts” is the default entity_id that gets created when first setting up the integration if you use the default friendly name for the integration. the user can change that to anything they like after the integration gets setup.

With anything like this you always need to verify that you are using the correct entities according to your own setup.

[seevee]

@WWillig

System: HA OS, Core 2026.1.3 (about to update to 2026.4.0)

Thanks for the kind words! I’m glad you like the card!

I believe updating HA Core will resolve your issue immediately, but do let me know.

EDIT: Your yaml config looks fine to me, and you will be able to verify it yourself by switching back and forth between the visual and code editor modes - as @finity pointed out, the entity name is dependent on how you set up the NWS Alerts integration. @IvandaVGV shared the default entity name. Thanks to all of you for the help!

[seevee]

Thanks for the feature suggestion! This is going on the roadmap for the next set of updates.

[IvandaVGV]

Ah, appreciate the clarification. And these cards, very much. My fully exposed weather geek is happy. At this point in my journey, I hadn’t strayed from defaults.

I did notice a slightly quicker way to find your NWS zones of interest.

• Go to weather.gov

• Enter city, state or zip code in the box in the upper left-hand corner & click “Go”

• 

• Click “More Local Wx”
  

  

• The zone code should be in the URL
  

  

Thanks, all!

[WWillig]

I usually wait for the second release of the core but I will install the new vers now. I noticed the _alerts_alerts thing but thought it was something I did and changed it…

[WWillig]

i updated the core to 2026.4.0 and problem is solved! Thanks for the advice!