If the Current Sky block shows offline, check the “Airport” popup.
The times from the metar (in UTC) is the correct time to check
Maybe the calculation of your local time is not correct.
Then install the attached update script.
Wim
P.S.
Metar use the UTC or Z timezone.
In the past the human readable date-time item was “observed”:“2021-05-25T11:50Z”
But since a few days the Z has disappeared from the downloaded checkwx json file. It now reads: “observed”:“2023-02-13T09:20”
The PHP strtotime function will use the local timezone to calculate the time when there is no Z or UTC in the string…
Stations in a timezone east of “Greenwich” will have x hours "older’ data.
West of “Greenwich” will not detect stalled data and display a “future time” in the block heading.
We will have to wait and see if chckwx will add the Z again.
Tried to run updates. Downloaded, unzipped, and ftp’d all of them to njweathercat.com/pwsWD. Received prompts from my hosting site confirming overwrite of the older files. Now I’m getting a “404” when I launch pwsWD. Dumped local browser cache. Same error.
See attached screenshot, no error messages just a question to open PWS_easyweathersetup.php
and hit the save-button.
Probably there is a conflict with a Darksky setting.
I have nop idea what you refer to with “the Current Sky error which you’re aware of”
The error-message should not occur at your website as you are not be using darksky.
I can not test all combinations of all forecasts/current conditions a.s.o.
Nor can i check your settings without a password.
AFAICS you added an (invalid / old) API-key for DarkSky. ==> should be replaced
You also set DarkSky & alternatives to nu. ==> OK
Please replace the darksky API-key with ADD YOUR API KEY
That should solve the problem in the sky-block.
If you think there is an error in the scripts sent me a PM with your easyweather password, I will take a look.
Wim
P.S. All passwords for ftp or easyweather are removed from my computer after 24 hours.
That occurs when there has been no end-of-year roll-over, these are values from 2022 displayed in this year.
The history has to be updated by using the PWS_hist_update.php
Wim,
Current Sky block shows “offline”. The reference to the Dark Sky API has been removed(by you). Checked metar api which appears to be correct. The airport drop down info appears correct too i.e. time, temp.
It was OK yesterday, so it can also be a stalled file, or a problem at the checkwx.com website.
I loaded your website at 07:00 UTC
There was old data in some blocks.
I used the debug-console . . /PWS_module_test.php button “load files” and a few files were reloaded.
The “Current Sky” block is now OK.
You can check the used file with the debug-console or directly . . . rcat.com/pwsWD/PWS_listfile.php?file=jsondata/metar34KPHL.txt&type=json observed] => 2023-02-14T06:54:00
[raw_text] => KPHL 140654Z 31011KT 10SM CLR 09/M06 A2983 RMK AO2 PK WND 32026/0603 SLP102 T00891061
Maybe the Meteobridge (cron-job) is not set to run 24/7 ?
Or the modem was off-line for a short period ?
Or checkwx.com was having another problem?
Let us wait and see if the problem reoccurs later today?
If so you can do some checks yourself.
=== error removed
There were also error messages about a typing-error in the user language file.
I removed the typing error and set your language to en-us
=== to do
The weather-warnings are generated by the original set of scripts maintained by saratoga-weather.
You have to adept those scripts yourself with these instructions => . . . hercat.com/pwsWD/nws-alerts/NWS-alerts_read_me.html
Sorry, switched to using DarkSky. I have re-enabled the metar code so you can see the 1-hour difference I mentioned.
Attempting to run https://travelingrvwx.com/pwsWD/PWS_hist_update.php gives a “Sorry - not possible” response. I don’t remember having to do this end-of-year script before so I am probably not doing it correctly.
===
There is no end-of-year script.
The end-of-year housekeeping is done by the cron-job.
Sadly if that fails in the night “Dec 31 23:00 ->Jan 1 02:00” you have to do it manually and for that you use PWS_hist_update.php
Yesterday the template was running fine.
Today I downloaded and installed the latest scripts and get an error message
“Darksky script failure”
even if I select METAR in easyweathersetup.
