Again nonsense values from api calls

  • 3
  • Problem
  • Updated 2 years ago

Since tonight the api calls deliver strange values. Again. The api problems exist since 3 months now... Maybe someone can finally solve this?!
Photo of Gert Ulott

Gert Ulott

  • 31 Posts
  • 2 Reply Likes

Posted 2 years ago

  • 3
Photo of John Wright

John Wright

  • 1 Post
  • 0 Reply Likes
Same problem here: empty forecasts, errant conditions. Started last night then was corrected. Started again this morning and has been going on for hours. To be clear, I'm getting values returned. Some of them are proper. Most are not (empty or incorrect). 
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
We are seeing the same thing.  It has to do with when a server comes online but isn't ready to serve data yet.  We are working on fixing it now.
Photo of Paul Volcko

Paul Volcko

  • 1 Post
  • 0 Reply Likes
Also seeing this in my app. Out of range values, such as temperatures of 9999. Empty current_observations objects. current_observations with timestamps and data from minutes to days ago. I'm lucky to get 2 good responses per hour.
Photo of Andy Roberts

Andy Roberts

  • 1 Post
  • 0 Reply Likes

I am having problems signing up for a developer account... just says "server error"


Photo of Will

Will

  • 3 Posts
  • 0 Reply Likes
Andy how does this have anything to do with the errant values coming back from the API?
Photo of Will

Will

  • 3 Posts
  • 0 Reply Likes
Brendan this is still occurring and causing problems. Is there any update on when we can expect this to stop? I have to drop data that has wildly out of bound results or it throws everything else off. 
Photo of Gert Ulott

Gert Ulott

  • 31 Posts
  • 2 Reply Likes
I could post once more the same f...... picture as above! Nothing changes!
Is there any realistic chance that the api will work like it did before Nov/16???