Has WU changed its API Key length

464 views
Skip to first unread message

Paul Oversmith

unread,
Apr 1, 2019, 6:43:14 PM4/1/19
to weewx-user
Have been using Weather Underground to download forecasts for several years. 
Stopped working with a key error end of March, 2019.  So I  got a new API key, but now getting the following messages:
Apr  1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: download forecast from 'http://api.wunderground.com/api/XXXXXXXXXXXXXXXXXXXXXXXXXXXXcbc1/hourly10day/q/34231.json'

Apr  1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: error in response: keynotfound: this key does not exist

Seeing that the last 4 characters are outside the block out text, I was wondering if they increased the key length and that is what is preventing getting the forecast. Or perhaps I need to delete some of the API key. my key is: d7xxxxxxxxxxxxxxxxxxxxxxxxxcbc1

Uploads to WU work.

Tried to download a current version of the forecasting code, but the site seems to be down.

Any suggestions on how to fix?


Paul Oversmith

unread,
Apr 1, 2019, 8:06:23 PM4/1/19
to weewx-user
I did some more checking and the WU API keys and calls have changed.  If you upload to WU you can get a new key. But until the forecasting code is updated they will not work because they change the API calls.

Any timeline for issuing a new forecasting addon WeewX?

For those that have not seen the WU notice, here it is:

If you have a personal weather station that uploads to Weather Underground and have been waiting to get a key for the new API, here are the instructions.

Please note that if you do NOT download data from the Weather Underground API, you probably don't need a key.  Uploading data to Wunderground from your PWS is not the same thing.

****

Dear PWS uploaders, thank you for your continued loyalty and patience!

The gateway for the new API keys for PWS uploaders is open.

Cut and paste this URL into your browser:  https://www.wunderground.com/member/api-keys

If you are not logged in, you will be asked to.  The system will also verify that you have a PWS uploading to the system.

You will then see a blank box below “Your API keys”.  Agree to the new Terms and Conditions by clicking in the small box next to “I agree”, click on the blue “GENERATE” box, and your new key will be created.  

The key will be masked on the screen, but you can use the “Show” link below the box to see it.  There is also another blue box, which, when clicked, copies the key to your clipboard.

If you have any problems, log out and log back in again.  If that does not resolve the problem, please email me at victoria...@ibm.com.

Next, once you have your new key, you can use it in the NEW (not old!) API’s commands.  The documentation for those commands is here:  https://docs.google.com/document/d/1eKCnKXI9xnoMGRRzOL1xPCBihNV2rOet08qpE_gArAY/edit

The new API should work immediately once you have the new key in the new commands.

Remember that the new keys work on the new API only, and the old keys work on the old API only.

Old API keys that are associated with a PWS will be kept working until March 22, 2019.  However, that will be the very last day for those API keys to work, so you should transition as quickly as you can to the new API.  

Victoria Gardner
Weather Underground API customer service

Stefan Kear

unread,
Apr 1, 2019, 10:02:23 PM4/1/19
to weewx-user
I've noticed this too but with the Amazon Echo devices. The new WU API key is 32 characters in length whereas the old key was 16. I tried to set the new API key with the current Weather Underground Alexa skill and "she" would only accept the first 16 characters. I'm unable to get the skill to work again since the new key is too long. It was a pretty cool skill when it was working.
Uploading to WU from my PWS works with no issues.

Stefan

V. Kelly Bellis

unread,
Apr 2, 2019, 9:09:45 AM4/2/19
to weewx-user
Hi Paul,

Thank you for starting this thread. I was holding off saying anything as I too discovered that the new longer WU API key and forecast.py (v3.4.0rc1) didn't work. The primary reason in holding off in mentioning the WU issue was another problem I've been having with getting XTide to work with the forecast extension (which is what prompted Matt to create forecast.py v3.4.0rc1).

The other tangential item I've held off in broaching - perhaps the topic of another future thread - has to do with how forecast and NWS play together as the old NWS 3-letter forecast office identifier (foid, also referred to as HADS) and 6-character location identifier (lid)are being phased out; this is the NWS so-called PFM product. It has been replaced with the Point-n-Click product (quasi-official product name) allowing for more localized forecasts from a gridded database. More on that here: https://www.weather.gov/mdl/ndfd_home

[Forecast]
  [[needed_fixes]]
  •     WU new API keys and commands
  •     NWS new Point-n-Click product
  •     new tide v.2.15.2

On Monday, April 1, 2019 at 6:43:14 PM UTC-4, Paul Oversmith wrote:
Reply all
Reply to author
Forward
0 new messages