Smart home did not announce tornado warning

Five failure points

When a smart home stayed silent during a tornado warning, the failure was usually in one of five places: a notification switch left off, a platform that never had native alert support, the wrong integration, a dead-end automation path, or a hub that lost power or internet before the warning could arrive. Sort the setup by those five points first. That is the fastest way to separate a fix you can do now from a limitation you need to stop treating like a bug.

Alexa: check the notification switch first

Alexa is the fastest case to verify because the failure is often just a disabled notification path. Open `Settings > Notifications > Weather` in the Alexa app and turn on `Severe Weather Alert`. If that switch is off, the speaker will stay silent even if every other part of the setup is healthy. Check the exact account and device that should announce, then retest after any app or profile change.

• Open `Settings > Notifications > Weather`.
• Turn on `Severe Weather Alert`.
• Confirm the announcement target is the right device, room, or account.
• Retest after any change to the app or linked services.

Home Assistant: make sure you installed the alert integration

Home Assistant is where a lot of smart home tornado warning alerts look configured but never actually reach a speaker. The built-in `National Weather Service (NWS)` integration is easy to confuse with the alert path people expect, but the community `custom-components/weatheralerts` component is the one that creates alert sensors and can trigger automations.[1] As of `v2026.5.x`, it installs through HACS config flow and polls `alerts.weather.gov` every 30-600 seconds.[1]

• `National Weather Service (NWS)` is the weather-data path, not the alert-sensor path.
• `custom-components/weatheralerts` is the component that creates actionable alert entities.[1]
• If the alert entity never changes, the speaker has nothing to announce.[1]
• If you wired the weather feed into a speaker automation, you built the right-looking wrong thing.

Google Nest: a limitation, not a misconfigured setting

Google Nest speakers are a different kind of failure. As of July 2026, the practical problem is not a hidden setting but a platform boundary: there is no native NWS-style emergency broadcast path on the speaker itself. The workaround is to send the alert through another automation engine, then have Nest speak it with text-to-speech. That is a workaround, not a repair to a missing built-in feature.

SmartThings: treat the old paths as unverified

SmartThings is the least clean diagnosis because the older SmartWeather and IFTTT-style routes do not map to a clearly maintained tornado-alert path anymore. Treat this one as Investigating unless you can verify a current maintained SmartApp or equivalent in your own account. If the path depends on an old forum post or a deprecated channel, treat it as unverified.

Backup power is the last line

If the hub, router, or speaker goes dark, the best automation in the world will still miss the warning window. Keep the hub and router on battery backup, and make sure the alert device itself can stay awake long enough to receive the message. Cloud-only paths are especially fragile during storm-time outages. A separate battery-backed weather radio remains the simplest way to avoid depending on one more online link in the chain.

References

1. custom-components/weatheralerts GitHub README, GitHub