Community. Driven. Weather. Data. | Always Ad-Free | Developer FriendlyChecking statusDiscord
WxAlerts.org, Community Driven Weather Data
Support us
Sign in
Volunteer-run · no ads, no data sales

Built by the people who use it

Nobody here is paid. The docs are written by the people who did the setup first, the integrations exist because someone wanted them on their own network, and the bad polygon you noticed at 2 AM is a bug report nobody else was going to file. There is a lot to do and most of it does not need you to write code.

Join the DiscordBrowse the code
Where to start

Five things that actually help

In rough order of how much difference they make against how long they take.

Report a bad alertA polygon in the wrong place, a garbled narrative, an alert that arrived late or never arrived at all. It is the single most useful bug report we get.Build on the feedWire alerts into something you already run, then write up how you did it. The guides here are community-written, and your setup notes save the next person an evening.Bridge a meshRun the MeshMonitor bridge and put NWS warnings onto your local Meshtastic or MeshCore mesh, where they reach people with no cell signal at all.Get your county on boardEmergency managers, 911 centers and spotter nets reach people we never will. An introduction to your local EOC spreads this faster than any ad we could not afford anyway.Host a relayRun a broker for your club, county or mesh and take a chunk of the fan-out off the origin. Still being designed, so come and help shape it.
Report a bad alert

Tell us what you saw

A polygon drawn somewhere it should not be, text that came through garbled, a warning that reached you ten minutes after the NWS issued it, or one that never reached you at all. We watch the ingest, but we cannot see what your phone did with it. You can.

Reports go to Discord so whoever is around can pick them up. There is no form yet on purpose: a half-filled form tells us less than a sentence and a screenshot.

Report it in Discord
The CAP idOpen the alert on the live map and copy the CAP id from the detail panel. It identifies the exact product and saves an hour of guessing which one you meant.
What was wrongPolygon in the wrong place, text garbled or truncated, wrong county list, alert never arrived, or it arrived long after the NWS issued it.
When, with a timezoneFor a late or missing alert this is the whole report, and it is what we match against the ingest logs.
How it reached youPush, email, SMS, MQTT, the live map or an integration. Delivery bugs and ingest bugs look identical from the outside and this is what separates them.
A screenshotEspecially for anything that renders wrong. One picture settles what a paragraph cannot.
Emergency management

Get your county on board

A county EOC, a 911 center or a spotter net reaches people we never will, and the ones who most need a warning are rarely the ones who go looking for an app. If you volunteer with an agency, or you just know the person who runs the local net, an introduction is worth more to this project than most of what we could build in the same week.

What we can offer an agency, at no cost and with no contract:

  • The full alert feed over MQTT, with documented payloads and no rate limit worth worrying about.
  • A broker of their own if they would rather not depend on ours; see below.
  • Help wiring alerts into whatever they already run, from a dashboard to a mesh to a siren controller.
  • A straight answer about what we do and do not guarantee, because we are not an official source and will never pretend otherwise.
Email us
Being designed

Host a relay

A relay is a broker you run that subscribes to our feed once and serves everyone on your side of it: a radio club, a county, a mesh, a campus. Fewer connections to the origin, less egress on a bill that donations pay for, and a broker your people can reach even when we are having a bad day.

Email us

Why it is not a signup form yet

A relay sits between a tornado warning and a person, and a broken one can drop, delay or alter that warning with nobody downstream any the wiser. That is not a footnote on a life-safety feed, so two things have to land before we hand out relay credentials to anyone who asks:

Signed payloadsSo a client can verify an alert came from the origin unaltered, no matter how many hops it took to arrive.
Published relay healthSo a relay that has silently fallen behind is visible as stale rather than trusted, and clients can fall back to the origin.

Until then, relays are set up one conversation at a time with groups running them for their own people. If that is you, or you want a say in how this works, come and say so. The design is genuinely still open.

Open source

The code

The integrations people actually run are public, and they are the friendliest place to start: small, self-contained, and used by someone who will notice if you improve them.

All repositories
WxAlerts-HAThe Home Assistant integration. Live NWS alerts and GOES GLM lightning as entities, pushed over MQTT.Pythonwxalerts-meshmonitorThe mesh bridge. Puts NWS watches and warnings onto a Meshtastic or MeshCore mesh through MeshMonitor.PythonEverything elseRadar and model processing, the GLM ingest and the tools around them. Some are private while they settle down.
Elsewhere

Where to find us

DiscordWhere reports get triaged, integrations get debugged and storms get watched together. Start here.The whole community, in one placeGitHubThe apps, the integrations and the ingest. Issues and pull requests welcome.github.com/wxalertsXRelease notes and the occasional outage post.@wxalerts_orgFacebookSame announcements, for the people who live there instead./wxalert