Almighty

Contribute › Weather stations

Connect a weather station

Send your station's readings to Almighty as well as to anywhere you already share them. They show on the Contributor weather layer for everyone.

1. Register in the Almighty app (More › Contribute) and add a station to get its key

There's no sign-up on this website. In the app, open More › Contribute, sign in, accept the Contributor Terms and tap Add a station. Choose Weather station, give it a name and put a pin where it stands (only you see the exact place).

The app then shows two things you need below:

App Store (iPhone, iPad, Mac) Google Play · coming soon Web app

Almighty only accepts readings from stations added this way. Below, STATION_ID and STATION_KEY stand for yours. A key looks like alm_st_ followed by 43 letters, digits, - and _.

2. Ecowitt

For Ecowitt gateways and consoles (GW1100, GW2000, HP2550, HP2560, WS2910 and the like). Use the WS View Plus app on your phone (newer devices: the Ecowitt app, which has the same settings under the device's Others › DIY Upload Servers), with your phone on the same Wi‑Fi as the gateway. Your Ecowitt.net upload keeps working alongside.

  1. Open WS View Plus, pick your device and swipe or tap Next until you reach Weather Services.
  2. Go to the Customized page and set Enable.
  3. Fill in the fields as below and tap Save.
Protocol Type Same As
Ecowitt
Server IP / Hostname
api.almighty.live
Path
/v1/contribute/weather/ecowitt/STATION_KEY
Port
80
Upload Interval
16 seconds or more (60 is plenty)

If the Path box won't take the whole thing (it is 81 characters long), use the short form, which does the same: /v1/cw/STATION_KEY (57 characters).

the Customized screen in WS View Plus, with Enable on, Protocol Type Same As set to Ecowitt, Server IP / Hostname api.almighty.live, Path /v1/contribute/weather/ecowitt/ followed by the key, Port 80 and Upload Interval 60, and the Save button at the bottom.

Ecowitt protocol: the key goes at the end of the path, nothing else to fill in.

Your console also sends its own fixed PASSKEY with every upload. Almighty remembers it from the first upload and refuses uploads with a different one for this station, so a copied key alone is not enough to send as your station. Changed gateway? Make a new key in the app.

Alternative: Weather Underground protocol

If your firmware doesn't offer the Ecowitt protocol on the Customized page, or you prefer it, choose Wunderground instead:

Protocol Type Same As
Wunderground
Server IP / Hostname
api.almighty.live
Path
/v1/contribute/weather/wu/updateweatherstation.php? (with the question mark)
Station ID
STATION_ID (if the field is too short, its first 8 characters)
Station Key
STATION_KEY
Port
80
Upload Interval
16 seconds or more

the same Customized screen with Protocol Type Same As set to Wunderground: two more fields, Station ID and Station Key, appear under Path.

Weather Underground protocol on an Ecowitt console.

3. Ambient Weather

For Ambient Weather consoles and WiFi bridges that show a Customized server page in the awnet app (WS‑2902, WS‑5000 and others with recent firmware). Your AmbientWeather.net uploads carry on as before.

  1. Open awnet with your phone on the same Wi‑Fi as the console, pick your device and go to the Customized page (after the Weather Server pages).
  2. Set Enable, fill in the fields below and tap Save.
Protocol
Ambient Weather
Server IP / Hostname
api.almighty.live
Path
/v1/contribute/weather/ambient?key=STATION_KEY& (ending in &)
Port
80
Upload Interval
16 seconds or more

the Customized screen in awnet: Enable switched on, Protocol set to Ambient Weather, Server IP api.almighty.live, Path /v1/contribute/weather/ambient?key= followed by the key and an ampersand, Port 80, Upload Interval 60.

The console adds its readings straight after the path, which is why it ends in "&".

If your awnet only offers Wunderground as the protocol, use the Weather Underground settings above instead (same fields).

4. Davis (WeatherLink)

To be straight with you: Davis consoles, WeatherLink Live and the WeatherLink cloud can't send to a server you choose. WeatherLink can only forward to Weather Underground itself. So a Davis station needs a small computer or box in between that reads the station and uploads in the Weather Underground protocol. Two common ways:

WeeWX (free, on a Raspberry Pi or any Linux computer)

WeeWX reads Vantage Pro2 and Vantage Vue consoles over their data logger, and WeatherLink Live with the community WeatherLink Live driver. Once WeeWX is reading your station, use its built-in Weather Underground uploader pointed at Almighty. In weewx.conf, under [StdRESTful]:

[StdRESTful]
    [[Wunderground]]
        # Almighty, through WeeWX's Weather Underground uploader
        enable = true
        station = STATION_ID
        password = STATION_KEY
        server_url = https://api.almighty.live/v1/contribute/weather/wu/updateweatherstation.php
        rapidfire = False

Leave the question mark off server_url (WeeWX adds it). Then restart WeeWX (sudo systemctl restart weewx). It uploads after every archive record, usually every 5 minutes. Keep rapidfire = False.

Already uploading to the real Weather Underground from WeeWX? This section takes its place. To keep both, use another uploader for one of them (for example a second copy of the uploader through a WeeWX extension); we can't promise a particular extension works.

a text editor showing weewx.conf scrolled to [StdRESTful], with the [[Wunderground]] block above filled in and the server_url line highlighted.

The only change in WeeWX: the uploader's server address and your station's ID and key.

Meteobridge

Meteobridge boxes read Davis consoles and WeatherLink Live. Its Weather Networks page sends to Weather Underground's own server, so use an HTTP request in Services › Events (every minute) with a URL in the Weather Underground protocol, built from Meteobridge's template values converted to the units it needs:

http://api.almighty.live/v1/contribute/weather/wu/updateweatherstation.php?ID=STATION_ID&PASSWORD=STATION_KEY&action=updateraw&dateutc=now&tempf=[th0temp-act=F.1]&humidity=[th0hum-act.0]&dewptf=[th0dew-act=F.1]&baromin=[thb0seapress-act=inHg.2]&windspeedmph=[wind0avgwind-act=mph.1]&windgustmph=[wind0wind-max10=mph.1]&winddir=[wind0dir-act.0]&rainin=[rain0rate-act=in.2]&dailyrainin=[rain0total-daysum=in.2]&solarradiation=[sol0rad-act.0]&UV=[uv0index-act.1]

Leave out any value your station doesn't measure. Check the template names against your Meteobridge's own template list (they can differ between versions and sensors).

Meteobridge's Services tab, Events, with a new HTTP request on the "every minute" event and the long URL above in its URL field.

Meteobridge: an HTTP request every minute instead of the built-in Weather Underground upload.

5. Other stations and programs (Weather Underground protocol)

Almost every weather station program and many consoles can upload in the Weather Underground protocol. Anything that lets you change the server address it uploads to can send to Almighty with these settings:

Upload URL
http://api.almighty.live/v1/contribute/weather/wu/updateweatherstation.php (https:// works too, when the device can)
Station ID
STATION_ID (or its first 8 characters, if the field is short)
Password / key
STATION_KEY
Interval
16 seconds or more

A complete upload looks like this (any of the readings can be left out):

http://api.almighty.live/v1/contribute/weather/wu/updateweatherstation.php?ID=STATION_ID&PASSWORD=STATION_KEY&dateutc=now&tempf=61.3&humidity=72&baromin=30.02&windspeedmph=4.5&windgustmph=9.0&winddir=230&rainin=0&dailyrainin=0.12&solarradiation=310&UV=2&action=updateraw

Almighty answers success, as Weather Underground does.

Program or consoleWhere to look
Cumulus MXIts Weather Underground settings use Weather Underground's own server, so use Settings › Third Party Uploads › Custom HTTP with a URL like the one above, filling the readings with Cumulus web tags. The protocol needs °F, mph, inHg and inches: the tags give Cumulus's display units, so this suits a station shown in those units.
Weather DisplayIts Weather Underground upload settings, if your version lets you change the server or URL; otherwise its custom HTTP upload with a URL like the one above.
MeteobridgeAn HTTP request event, as in the Davis section. This works with every station Meteobridge reads, not just Davis.
ObserverIP and similar consoles (Ambient ObserverIP, Fine Offset / Froggit / Bresser Wi‑Fi consoles that are set up from a web page or WS View)The Weather Network or Customized server settings: choose the Wunderground protocol and fill in the server, path, ID, key and port as in the Ecowitt Wunderground settings.
WeeWXThe [[Wunderground]] block with server_url, as in the Davis section. This works with every station WeeWX reads.

Menus change between versions. If you can't find a way to change the server address, the program can't send to Almighty directly: WeeWX or Meteobridge in between always can.

6. Check it's working

the app's More › Contribute screen listing "Back garden" as a weather station with a green Online label and "Last reading 20 s ago".

Your station in the app once its readings arrive.

7. Good to know

8. Troubleshooting

What you seeWhy, and what to do
401 "invalid key"The key is wrong or was replaced. Copy it again from the app (no spaces at either end), or make a new one. For the Weather Underground protocol, check the Station ID too.
Station stays OfflineCheck the server is api.almighty.live, the port is 80 and the path is exactly as above (including the ? or & at the end). Is the Customized page switched to Enable and saved?
The station shows "Disabled"It was switched off, by you in the app or by us (for example after reports of wrong readings). The station's page in the app says which; uploads are refused until it's switched back on.
Uploads accepted, but no new readingsReadings older than 2 hours or in the future are dropped. Check the console's clock and time zone (or let it set the time from the internet).
Some uploads missingUploads more often than every 16 seconds are dropped: raise the interval.
Ecowitt: refused after changing gatewayThe station is tied to the first gateway's PASSKEY. Make a new key in the app and put it in the new gateway's path.
Online, but not on the mapThe checks found its readings far from its neighbours'. Look at where the sensors are (shade, 1.5–2 m above grass for temperature) and at the station's page in the app. It comes back once it agrees again.
Readings look wrong (e.g. pressure)Set the console to send relative (sea-level) pressure, and check its calibration offsets.

Still stuck? Contact us with your station ID (never the key).