For more than a year, I was getting “uv” values returned for the Better Forecast > Current Conditions using the command down below. But just recently (maybe Jan 10 2025?), it stopped and broke my script.
Just wondering if this is on purpose? I tried looking through the API documentation, and it seems “uv” should still be supported.
https://swd.weatherflow.com/swd/rest/better_forecast?station_id=12345&units_temp=f&units_wind=mph&units_pressure=mb&units_precip=in&units_distance=mi&token=redacted
I have an app that collects observation data several times a day for my station and it stopped working as of 224-01-12.
I was able to update my code to the currently documented API but I’m curious if there was an announcement that what I was using was EOL as of this date and I just missed it or what?
The whole structure of the response is different now.
I’d like not to be caught off guard again in the future.
I haven’t heard or noticed a change in the API. Can you share more details of what has changed?
Peter - Now that I’ve spent hours “getting it to work” it looks like nothing actually changed on the API end (or my end) - I’m left scratching my head about what broke. I have a Google Cloud Function that calls the API every 5 minutes and stores the data where a web page of mine can pull and report on the conditions and forecast and charts conditions over time. It’s been working for a year with no problems and then suddenly stopped working at midnight on Jan 12. I’m now running the same code as I was a week ago and it’s working. Ugh
perhaps a change in the year caused a problem with the code you are using??
And magically on Jan 13, it started working again.
Turns out a bunch of values were not getting returned, not just “uv”.
I noticed around Jan 10 or 11 that my REST calls for Better Forecast were not returning certain values, like “uv”.
Then on Jan 13, magically it started working again.
We did nothing wrong and there seems to be silence from whomever fixed it on the Tempest side.
See my thread here: