API does not work properly

  • 3
  • Problem
  • Updated 1 year ago
The API stopped working properly recently.
Current Observation returns mostly empty values sometimes NULL which causes crashes in my apps.

One of the problematic crashing calls:

https://api.wunderground.com/api/<APIKEY>/pws:0/geolookup/conditions/q/45.20000076,0.81999999....

https://api.wunderground.com/api/<APIKEY>/pws:0/geolookup/conditions/q/Perigueux,france.json

It may have something to do with that if personal weather stations are disabled 

Please fix it as soon as possible

Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes

Posted 1 year ago

  • 3
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
It definitely has something to do with personal weather stations
If PWS:1 the weather condition string is empty
If I PWS:0 everything is empty and temperatures and dewpoints are null! Which is totally unexpected and causes my apps to crash!

For example this weather station: IAQUITAI113

A couple of other urls:
http://api.wunderground.com/api/<APIKEY>/pws:0/conditions/q/DE/Eppelsheim.json (everyhing is empty or null)

https://api.wunderground.com/api/<APIKEY>/pws:0/geolookup/conditions/q/Perigueux,france.json (eveything empty or null)

https://api.wunderground.com/api/<APIKEY>/lang:LI/pws:0/geolookup/astronomy/conditions/hourly1...

https://api.wunderground.com/api/<APIKEY>/lang:LI/pws:0/geolookup/conditions/q/pws:IAQUITAI113... 

Please fix it ASAP and keep us posted! Thanks!
Photo of Actiaweb Sandro

Actiaweb Sandro

  • 20 Posts
  • 0 Reply Likes
The problem is higher since yesterday ... name of cities changed ... lang:XX not avaiable for others cities !
Hope the correction arrive soon ...
Photo of Bill Myers

Bill Myers

  • 8 Posts
  • 1 Reply Like
I have noticed the same as the comments above.

The current conditions, text and icon is not been produced in the API, just comes in blank.
Also on the WU site itself cities have different names or designations.

This should be a priority to fix.
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
Dear weather underground, could you let us know what is happening and how long it takes to fix it. Thank you!
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
The update that was made was just around city names to make them better and in the right spot, but in some cases moved those locations too far from the weather observation that should be matching.  We are taking each one of these and investigating the issues 
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
Well, localizations  stopped working entirely for major metropolitan areas such as New York. 
It does not return anything!
This is a massive bug!

Try this for New York, NY
https://api.wunderground.com/api/<key>/lang:SP/geolookup/conditions/forecast10day/q/new%20york...


I can't believe  it left unfixed for days!

Photo of Bill Myers

Bill Myers

  • 8 Posts
  • 1 Reply Like
This is not just an API problem. The widget for an android device and websites do not have current conditions icon or other current condition data.
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
Good to know! It is system wide issue than. It should be a very high priority fix.
Photo of Andrew Keyser

Andrew Keyser

  • 4 Posts
  • 0 Reply Likes
This is also affecting Edmonton, Alberta stations: when location is set to my own station, pws:IALBERTA612, I get an empty current_observation.weather value. Been this way since Oct 19... It's funny to note, however, that the 'icon' value does seem to be accurate (as accurate as the basic icons can be)
(Edited)
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
I was checking a couple of locations and some returned empty data for a few minutes at least.
such as this one Albuquerque, NM
https://api.wunderground.com/api/key/lang:EN/pws:1/geolookup/astronomy/conditions/hourly10day/foreca...
Budapest, HU
https://api.wunderground.com/api/key/lang:EN/pws:1/geolookup/astronomy/conditions/hourly10day/foreca...

This massive bug has been going on for 5 days and nobody doing anything! I can't believe it wasn't fixed overnight! 
Photo of Actiaweb Sandro

Actiaweb Sandro

  • 20 Posts
  • 0 Reply Likes
The new response of the support :

The issue with the dual city return when using a language request is a bug. We will fix that, but using the "l" code is a workaround. 

...

Wait and see :)
Photo of Tiff

Tiff

  • 1 Post
  • 1 Reply Like
Indeed. I am too having the error for trying to request hourly forecast on cities like Toronto and Vancouver.
http://api.wunderground.com/api/[key]/hourly/settings/q/ca/toronto.json

I really hope it does get fixed, quickly. Thanks!
Photo of WeatherVor

WeatherVor

  • 38 Posts
  • 4 Reply Likes
Any update on this? Clearly nothing has been fixed.