stillreporting

If you run a weather station, your readings currently go to a vendor's cloud, or into a pipeline that feeds a government system, or both. Point them here as well and they also land somewhere independent — where the data stays yours, downloadable in full, with no account and no tier.

Why bother

The sensors belong to the people who installed them. The places to send readings mostly do not. Weather Underground, Ambient, Ecowitt and Davis each run a closed cloud with its own terms and its own idea of what your history is worth. The one genuinely open option, CWOP, exists to feed NOAA's ingest system — which is fine, and worth doing, but it means the open path and the federal path are the same path.

So there is no independent place for a station owner's data to land. That is the entire gap this fills. Not a competitor to anything — an extra destination, so that if one of the others changes its mind, the record does not have a hole in it.

Uploading here does not stop you uploading anywhere else. Every station firmware we support treats custom upload as an addition, not a replacement.

What you get

• Your full history as CSV, any time, no account. /api/station/<your-id>/history.csv?days=3650
• A public page for your station showing current readings and whether it is actually reporting.
• Honest staleness. If your station stops, the page says so within two hours instead of quietly showing an old number.
• Nothing is edited. Implausible values get flagged in a flags column and stored exactly as sent. We annotate, we never correct — you cannot recover a reading that was silently altered.

Setting it up

Ecowitt (GW1000 / GW1100 / GW2000 and the many rebadges)

In the WS View Plus app or the gateway's web interface, find Customized upload and turn it on:

Prefer Ecowitt's own protocol instead? It carries more — soil moisture, PM2.5, CO2, lightning, per-sensor battery. Same screen, just set Protocol to Ecowitt and Path to /data/report/, port 80. Your station's name then comes from its PASSKEY.

Ambient Weather

Same fields, in the Awnet app under the console's custom upload settings. This needs WiFi firmware 4.2.8 or newer on the ObserverIP module — older firmware has no custom server field at all.

WeeWX

WeeWX's built-in Wunderground uploader takes a custom endpoint. In weewx.conf:

[StdRESTful]
    [[Wunderground]]
        station = your-station-name
        password = anything
        server_url = http://stillreporting.ai-ministries.com/weatherstation/updateweatherstation.php

station and password have to be filled in for the plugin to run even though the endpoint does not check them. Note WeeWX only allows one Wunderground uploader — if you already send to the real Wunderground, you will need the WundergroundLike extension for a second.

Cumulus / CumulusMX, Meteobridge, Weather Display

All of these emit the same Wunderground format and let you set the server. Use the host and path from the Ecowitt table above. If your software gets there through one of these, your Davis, La Crosse or AcuRite hardware works too — those consoles have no custom upload field themselves, but the software in front of them does.

Anything else

If something is hitting us and not being understood, it gets logged rather than silently 404'd, so it can be looked at. Misconfigured is better than invisible.

Being straight about trust

The Wunderground and Ecowitt protocols have no real authentication — the "password" and "key" fields are plain text with no signature, by design of the protocols themselves, not by our choice. Anyone who learns your station ID could post readings as you. That is a known weakness of every network that accepts these protocols, including the commercial ones.

So: pick a station ID that is not trivially guessable, treat everything here as public weather observation rather than anything private, and understand that data quality on any open sensor network is a downstream judgement. Readings are flagged, never scrubbed.

Stations reporting