WundergroundStationForwarder

Station Forwarder

This code is built to be hosted on the free Google Apps Script platform. It takes in weather station data from:

• IBM Wunderground,
• MyAcurite,
• Davis WeatherLink,
• WeatherFlow Tempest,
• Ambient Weather,
• Ecowitt,
• aprs.fi (CWOP),
• The Things Network (LoRaWAN sensors like Dragino LHT65), or
• a custom data source in RTL_433 JSON format,

and periodically sends it on to

• IBM Wunderground,
• Windy.com,
• Aeris PWSWeather,
• WeatherCloud,
• OpenWeatherMap,
• WindGuru,
• WOW-BE Reboot (RMI),
• Temperatur.nu and/or
• NOAA CWOP.

Setup

1. Create a new Google Apps Script project and give it a name
2. Overwrite the default Code.gs file with code.gs from the latest release in this repository
3. Configure the script for you:

• Choose your datasource:

  IBM Wunderground

  Uses the IBM Wunderground API.

  Note: Unfortunately, it looks like the new Wunderground API keys have started expiring 6 months after being generated, so you may need to replace the key if that happens.

  • Set the datasource to ibm on line 10
  • Set your ibmAPIKey on line 12
  • Set your ibmStationID on line 13
  MyAcurite

  Experimental. Uses the undocumented MyAcurite private API.

  • Set the datasource to acurite on Line 10
  • Set your acuriteUsername on Line 15
  • Set your acuritePassword on line 16
  • Set your acuriteHubName (the user-set name on the internet-connected receiver) on line 17
  • Set your acuriteStationName (the user-set name of the outdoor sensor/station) on line 18
  Davis Weatherlink

  Uses the Davis Weatherlink API v2.

  • Set the datasource to davis on line 10
  • Set your davisApiKey on line 20
  • Set your davisApiSecret on line 21
  • Set your davisStationName on line 22
  Weatherflow Tempest

  Uses a Weatherflow Tempest Personal Use Token.

  • Set the datasource to weatherflow on Line 10
  • Set your weatherflowPUT on line 24
  • Set your weatherflowSationID on Line 25
  Ambient Weather

  Uses the Ambient Weather API.

  • Set the datasource to ambient on Line 10
  • Set your ambientWeatherStationName on line 27
  • Set your ambientWeatherApiKey on Line 28
  Ecowitt

  Uses the Ecowitt.net API.

  • Set the datasource to ecowitt on Line 10
  • Set your ecowittAPIKey from your Ecowitt.net Private Center on Line 30
  • Set your ecowittApplicationKey from your Ecowitt.net Private Center on Line 31
  • Set your ecowittMacAddress (find in your Device List) on Line 32
  aprs.fi (CWOP)

  Uses the aprs.fi API to fetch APRS packet data from a CWOP station.

  • Set the datasource to aprs on Line 10
  • Set your aprsStationID on line 34
  • Set your aprsApiKey on Line 35 from your aprs.fi account
  The Things Network (TTN)

  Uses the TTN Storage Integration API to fetch data from LoRaWAN sensors like Dragino LHT65.

  Prerequisites:

  • Your TTN application must have the Storage Integration enabled
  • Create an API key with Read application traffic rights in your TTN Console

  Configuration:

  • Set the datasource to ttn on Line 10
  • Set your ttnCluster to your regional cluster (eu1, nam1, or au1) on line 40
  • Set your ttnApplicationID on line 41
  • Set your ttnDeviceID on line 42
  • Set your ttnAPIKey on line 43
  • Set your station’s latitude and longitude on lines 37 and 38 in decimal degrees

  Supported sensor fields:

  • Dragino LHT65: TempC_SHT, Hum_SHT, TempC_DS, BatV
  • Dragino LHT65N-E5: ILL_lx (illuminance)
  • Generic: temperature, humidity, pressure, illuminance, battery
  Custom Data Source

  Send weather station readings from any system in RTL_433 JSON format.

  • Set the datasource to custom on Line 10
  • Set your station’s latitude and longitude on lines 37 and 38 in decimal degrees
  • Click Deploy ▼ → New deployment → ‘⚙’ → Web app, and change ‘Who has access’ to ‘Anyone’ and press ‘Deploy’
  • Begin HTTP POSTing JSON data to the https://script.google.com/macros/... URL provided in the confirmation dialog

• and choose one or more forwarding destinations:

  IBM Wunderground

  To send to Wunderground:

  Your Station ID and Station Keys are on your Wunderground Stations list.

  • Set updateWunderground to true on Line 47
  • Set your wundergroundStationID on Line 48
  • Set your wundergroundStationKey on line 49
  Windy.com

  To send to Windy.com:

  The Station ID and Station Password is found on your station’s detail page in My Stations. This is different than the API keys found at their API Key management page.

  • Set updateWindy to true on Line 51
  • Set your windyStationPassword on Line 52
  • Set your windyStationID on line 53.
  Aeris PWSWeather

  To send to PWSWeather:

  • Set updatePWSWeather to true on Line 55
  • Set your pwsWeatherAPIKey from your station’s profile page on line 56
  • Set your pwsWeatherStationID on Line 57
  WeatherCloud

  To send to WeatherCloud:

  Retrieve your station’s ID and API Key by going to your Devices, then clicking Settings → 🔌 Link on your station.

  • Set updateWeatherCloud to true on Line 59
  • Set your weathercloudAPIKey on Line 60
  • Set your weathercloudID on Line 61
  • Set whether or not you have a WeatherCloud Pro or Premium account with hasWeatherCloudPro as true or false on line 62
  OpenWeatherMap

  Creation of a new OpenWeatherMap station must be done by API, not on the OpenWeatherMap website. More information is available in the OpenWeatherMap Station API documentation. The basic concept for what must be done is available in the createNewOWMStation_() function. Remove the _ character from the name of that function to make it selectable from the ▷ Run button in the toolbar. If you do so, make sure you note your new station’s ID and other details in the log (available in the Executions tab in the sidebar after running!), then:

  • Set updateOpenWeatherMap to true on Line 64
  • Set openWeatherMapAPIKey to your API Key on Line 65
  • Set your openWeatherMapStationId to your OpenWeatherMap station’s external_id on line 66
  WindGuru

  Send to WindGuru:

  Start by registering a new “Other / Upload API” station, then:

  • Set updateWindGuru to true on Line 68
  • Set windGuruStationUID to your chosen station UID on Line 69
  • Set your windGuruStationPassword to your chosen station API password (note, not your account’s password) on line 70
  WOW-BE Reboot (RMI Belgium)

  Send to WOW-BE Reboot, the successor to MET UK WOW operated by the Royal Meteorological Institute of Belgium:

  Start by registering a new station. During registration, one of the fields in your Site’s options is “Authentication Key” (PIN). Choose any 6-Digit number. Then:

  • Set updateWOWBE to true on Line 72
  • Set wowBESiteID to the generated Site ID on Line 73
  • Set wowBEAuthKey to your chosen 6-Digit Authentication Key (PIN) on Line 74

  Note: WOW-BE Reboot replaces MET UK WOW, which is retiring in 2026. If you previously used MET UK WOW, you will need to re-register your station on WOW-BE as existing station IDs are not transferable.

  Temperatur.nu

  Send to Temperatur.nu:

  Start by registering a new “Reporting URL/Hashcode” station. Then:

  • Set updateTemperaturNu to true on Line 76
  • Set temperaturNuHash to your Hash Code on Line 77
  NOAA Citizen Weather Observer Program (CWOP)

  Send to CWOP. Start by registering for a new station, then when you receive your email:

  • Set updateCWOP to true on Line 79
  • Set cwopStationIDOrHamCallsign to your assigned CWOP station ID that you received via email on Line 80
  • If you are using your ham radio callsign as your station ID and you have received a validation code from NOAA CWOP support, set cwopValidationCode to your validation code on Line 81

4. Run the “Schedule” function (not the “doPost” function) by selecting “Schedule” in the dropdown and pressing the ▷ Run button in the toolbar. You’re done! You can see it periodically running in the ☰▶ Executions tab on the left sidebar. This code is executed on Google’s servers and does not require a computer to remain on.

If you ever make changes to the API keys or enabled services, just run the Schedule function again.

How to Update

1. Copy the code from code.gs in this release over your Code.gs file.
2. Make sure your API Keys and settings at the top of the file are correct and 💾 Save.
3. Run the Schedule function again with the ▷ Run button in the toolbar.

License

Feel free to take a look at the source and adapt as you please. This source is licensed as follows:

Station Forwarder is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Found this helpful? Buy me a tea!