Pirateweather status?

Let's Chat
, , ,
1

Noticed this today, not sure what is going on with them…today is 2023-11-21

Pirateweather Forecast for: Lakewood, NY, USA
Updated: 2023-11-18 03:00 EST

2

It’s not completely broken, e.g. https://merrysky.net/

3

Hi dcrooks,

If i check your website, your Pirateweather forecast is too old, indeed.
It is a Saratoga script , so when using “force” to refresh, the html shows errors

<!-- Error: Operation timed out after 4000 milliseconds with 76635 out of 83446 bytes received -->
<!-- HTTP stats:  RC=200 dest=107.23.99.108 port=443 (from sce=131.153.37.3)
      Times: dns=0.000 conn=0.057 pxfer=0.766 get=3.234 total=4.000 secs -->
<!-- RC=, bytes=0 -->
<!-- bad return from https://api.pirateweather.net/forecast/bXK5dBOo7h6BiFEVgTdyv9czMBwLlcvg5atrvjrM/42.0893224,-79.3263012?exclude=minutely&extend=hourly&units=us

The strange thing is that almost all expected data is received (76635 out of 83446 bytes received) but then it stops.
I think that @ktrue (saratogaWX) can better help.
Maybe post this also on the wxforum?

Questions:

  1. Did you change anything on your website on November 18?
  2. Do you use the same API-key for Saratoga and pwsWD, or do you have two keys?

Succes,
Wim,

4

Hi,

I checked your PWS_Dasboard website.

You are using PirateWeather as a replacement for DarkSky
The forecast data is current .

Please compare the pwswd forecast with a forecast for your area using the link form the @administrator post above.

When I use it for https://merrysky.net/forecast/Lakewood,%20NY,%20USA/us the forecast is comparable with the one in your PWS_Dashboard pop-ups.

Also when I use, in any browser, the link form your Saratoga website HTML, the correct data is returned within 2 seconds.
No timeouts.

Wim

5

Running a view-source on PW-weather.php?force=1 on your site shows:

<!-- PW-forecast.php (ML) Version 2.52 - 24-Feb-2023 on PHP 7.4.16 -->
<!-- timeFormat='Y-m-d H:i T'. timeline hours displayed as am/pm -->
<!-- temps in F -->
<!-- loading from https://api.pirateweather.net/forecast/bXK5dBOo7h6BiFEVgTdyv9czMBwLlcvg5atrvjrM/42.0893224,-79.3263012?exclude=minutely&extend=hourly&units=us. -->
<!-- curl fetching 'https://api.pirateweather.net/forecast/bXK5dBOo7h6BiFEVgTdyv9czMBwLlcvg5atrvjrM/42.0893224,-79.3263012?exclude=minutely&extend=hourly&units=us' -->
<!-- Error: Operation timed out after 4000 milliseconds with 59227 out of 83447 bytes received -->
<!-- HTTP stats:  RC=200 dest=107.23.99.108 port=443 (from sce=131.153.37.3)
      Times: dns=0.012 conn=0.070 pxfer=0.439 get=3.561 total=4.000 secs -->
<!-- RC=, bytes=0 -->
<!-- bad return from https://api.pirateweather.net/forecast/bXK5dBOo7h6BiFEVgTdyv9czMBwLlcvg5atrvjrM/42.0893224,-79.3263012?exclude=minutely&extend=hourly&units=us
false
 -->
<!-- reloaded stale cache ./PW-forecast-json-0-us.txt temporarily -->

so your webserver is having an issue contacting api.pireateweather.net site so the old cache file is loaded instead. when the connectivity issue is resolved, the script should work again on your website

You can also increase the timeout time by changing $numberOfSeconds=4; to $numberOfSeconds=8; and see if that allows you to get a full forecast with a slow connection.

6

Thanks guys. I noticed my pws site using the same source and api was working. I will try upping the time and see if that helps. Will try it tomorrow and let you know how I get along…

add: Unfortunately the Pirate forecast was working this morning so will have to wait for it to fail again before making any changes…argh…

add2: Made the change to numberofseconds=8 and when I reloaded the forecast it did update the time stamp. So will leave this change and see how it goes…

7

Since making this change I have not had any more issues.