How to Set Up Severe Thunderstorm Alerts for Your Smart Home

Start with the layer that does not depend on a speaker

A dependable smart-home severe thunderstorm alert stack starts with two independent sources: phone WEA, which auto-fires only for destructive-tagged severe thunderstorm warnings, and a SAME-coded NOAA Weather Radio, which catches the full warning stream. That matters because a severe thunderstorm warning can begin at 1.00-inch hail or 58 mph winds, while the destructive tier starts at 2.75-inch hail or 80 mph winds, so a household can be under a real warning and still get nothing from a phone alert unless the event crosses the destructive threshold [1][2].

Watch and warning are not interchangeable here. A watch means conditions are favorable; a warning means the hazard is happening or imminent. For setup purposes, the warning is the event that should trip radios, phone alerts, and home automations [3].

Use that table as the operating model. The rest of the setup is redundancy with labels on it, not a promise that any one device will catch every alert.

Set the baseline first

On the phone side, leave Wireless Emergency Alerts enabled. No signup is required, but the destructive-only behavior is the part that usually surprises people: base severe thunderstorm warnings and the intermediate considerable tier do not automatically trigger a WEA blast [2]. That is why a person can reasonably be under a warning and still say the phone stayed silent.

On the radio side, program a NOAA Weather Radio for the relevant county using SAME. The practical inputs are the SVR event code, the 6-digit county code, and the 1050 Hz attention tone. Once that is set, the radio is the always-on baseline that does not care whether a cloud account, app update, or speaker integration is behaving today [4].

If the household needs a single sentence to remember, it is this: WEA handles the worst tagged events on the phone, and SAME covers the county-level warning feed on a dedicated radio.

Add one convenience layer for the ecosystem you already use

This is where smart speakers and home automations belong. They are useful because they make the warning harder to miss inside the house, but they should be added after the baseline is working.

Alexa / Echo

Alexa can announce severe weather alerts and is the simplest spoken-alert layer for many mixed households. A commonly cited setup path is to ask for severe weather alerts, then verify weather notifications in the Alexa app under More > Settings > Notifications > Weather; because app screens shift, that path should be re-checked against the live app before relying on it or after a major update [5].

Treat Alexa as a convenience broadcast inside the home. It is useful when someone is upstairs, cooking, or not looking at a phone, but it still rides on app settings and account state, so it needs periodic re-verification [5].

Google Home / Nest

Google’s critical-alert path requires notification permissions in both the Google Home app, under Home settings > Notifications > General notifications, and the phone’s system settings [6]. That is the part worth confirming first, because the Nest Hub can answer weather questions without necessarily behaving like a local warning siren. A Google Nest Community moderator has stated that Nest speakers and displays do not natively broadcast local weather alerts, so any setup that assumes that behavior should be treated as unverified until tested on the current firmware and app versions [7].

For a Google household, the practical move is to enable every supported notification path, then prove the result with a real alert or the closest supported test flow. Do not infer coverage from the device being able to speak about weather.

Home Assistant

Home Assistant is the strongest redundant layer when you want the house to react instead of merely speak. The official NWS integration provides alert sensors, though they may be disabled by default, and community integrations can pull alerts.weather.gov using zone codes such as WIZ038 or county codes such as WIC087, with config-flow setup and updates that are typically per minute or on a default 90-second interval depending on the integration [8][10][11].

That makes Home Assistant the best place to translate a warning into household behavior: a hallway light turns red, a wall tablet shows the alert, and speakers announce the message in rooms where people are likely to miss a phone buzz. The key is to keep the automation narrow and explicit. Trigger on the weather alert sensor, map the state to a visible cue, and preserve the original warning text rather than replacing it with a vague status lamp.

IFTTT + smart lights

IFTTT is the lightest-weight automation path when you mainly want a visual cue. As of Aug. 25, 2026, its NOAA alert applets are RSS-polling based, with 5-minute polling on Pro and Pro+ and hourly polling on Free, so the latency ceiling is built into the product [9]. That is acceptable for redundancy, not for primary warning duty.

The practical mapping is simple: severe thunderstorm warning in, red light out. A color cue is useful because it survives across rooms and noise, and it pairs well with a spoken announcement from Alexa, Google Home, or Home Assistant. It should still be documented as a workaround layer, since polling delay is part of the design [9].

Keep the setup honest

The main failure mode in this category is overclaiming. A smart display that can answer weather questions is not the same thing as a local warning system. A speaker that can announce alerts is not the same thing as a county radio feed. And a light that turns red is not the same thing as the warning itself.

That is why a practical household stack looks like this: WEA enabled on every phone that should receive it, a SAME-programmed NOAA Weather Radio for the relevant county, then one smart-home layer that matches the ecosystem already in the house. Alexa is the simplest voice layer for many homes. Google Home can work once notifications are actually enabled, but the Nest speaker/display limitation needs to stay in view. Home Assistant is the most flexible place to combine alerts with lights and dashboards. IFTTT is the easiest way to get a basic red-light cue, with latency that should be accepted up front [2][4][6][7][8][9].

If you extend the stack later, keep the same standard for other automations: define the trigger, verify the source, then decide what the house should do without hiding the original warning.

A note on image-based guides: screenshots without dates age quickly in this category. A dated setup note and a quick retest after app or firmware updates are worth more than a polished walkthrough from last year.

References

1. [Severe Thunderstorm Warnings Update](https://www.weather.gov/lot/SevereThunderstormWarningsUpdate) - National Weather Service Chicago

2. [Wireless Emergency Alerts (WEA)](https://www.weather.gov/wrn/wea) - National Weather Service

3. [Thunderstorm Watch vs Warning](https://www.weather.gov/safety/thunderstorm-ww) - National Weather Service

4. [Using SAME with NOAA Weather Radio](https://www.weather.gov/nwr/usingsame) - National Weather Service

5. [Severe weather alert discussion](https://www.amazonforum.com/s/question/0D56Q00009HjBwqSAF/severe-weather-alert) - Amazon Forum

6. [Google Home critical alerts support](https://support.google.com/googlehome/answer/9244826) - Google Support

7. [Weather alert notifications](https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Weather-alert-notifications/m-p/215565) - Google Nest Community

8. [weatheralerts GitHub repository](https://github.com/custom-components/weatheralerts) - GitHub

9. [Get NOAA weather alerts via IFTTT notifications](https://ifttt.com/applets/BrHikhxJ-get-noaa-weather-alerts-via-ifttt-notifications) - IFTTT

10. [National Weather Service integration](https://www.home-assistant.io/integrations/nws/) - Home Assistant

11. [nws_alerts GitHub repository](https://github.com/finity69x2/nws_alerts) - GitHub