HWS-template (WD34) July version available

I believe it is line#141

Thanks Wim, you made my weekend perfect :slight_smile: :smiley:

It is in my script, but I am not using the latest version. . . :slight_smile:

It is line 138 in the latest version, which puts back the UV estimate in front of rain, but correcting it might affect something else further down?


138 $break = '.
';

EDIT: Having looked at it again, I think it’s OK to delete the point in the latest version too.

This is the version date mine has:
$scrpt_vrsn_dt = ‘w34_util_ccn.php|00|2019-04-25|’; #icons w34

And me. . . but latest version is

$scrpt_vrsn_dt = ‘w34_util_ccn.php|00|2019-06-29|’; # added UV | icons w34

See HWS-template (WD34) July version available - #32 by pwsdashboard - PWS Dashboard 2012 - Weather-Watch Forum

Wow, I missed that one. Thanks

hello
i uploaded the latest version of the template
http://valdefench57sgz.franceserv.com/pwsWD/index.php
live data running with the WL 2.0 API
for graphs, my setup parameterized with WU
on the other hand the monthly charts are “out” and the annual ones are all stopped at 25; 07.2019 ??
Regards

That is a severe problem with WU. They are working on it, maybe they solve it or they kill it altogether.

Most stations have intermittent gaps in the .CSV downloads as they often contain partial data only. Your yearly data is only available until July 25.
https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=ILORRAIN49&graphspan=year&year&format=1
Yout “this month” data is empty file https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=ILORRAIN49&graphspan=month&year&month&format=1

Your other weather-websites are affected also, example => July 25
http://valdefench57sgz.franceserv.com/realtime/weather28/index.php?p=wsReports&lang=en&wp=MB#data-area

There are dozens of discussions about all WU problems at the WX-forum, most important one: Weather Underground Issues and Bug Tracking - Check here before posting

WIM

Have you heard anything from WU? Nothing has changed on my site.

I had a problem like this about 1 year ago. They never responded to my requests and about 3 months later, it was fixed

I contacted WU support
the answer :

" [i]The URL you are using has been retired. It will not return reliable data.
If you are uploading data, you have access to the PWS API. You can download data via the API. Go to

Bit late now, but I can’t help wonder why the Dark Sky rain forecasts should be so drastically different between the Jan and July versions.

Same place, same time, same API key.


Jan.png

July.png

There was (maybe still is) some confusion about what the amount shown in the DarkSky file means.

=> SI units are as follows:
==> precipIntensity: Millimeters per hour. (also for UK2 units rain is in mm)

=> A data point object contains various properties, each representing the average of a particular weather phenomenon occurring during a period of time
==> precipIntensity: The intensity (in inches of liquid water per hour) of precipitation occurring at the given time.
So it is now assumed that for a day forecast the intensity is the average for 24 hours in mm, not in inches.
The scripts display the value from the day-record but multiplied with 24 to get the daily value.

Wim

[quote author=meteolive57 link=topic=68132.msg549442#msg549442 date=1566221834]
I contacted WU support
the answer :

" [i]The URL you are using has been retired. It will not return reliable data.
If you are uploading data, you have access to the PWS API. You can download data via the API. Go to

I had a look at the current documentation, and I agree that the data point objects are all defined in Imperial units - the default. However, it seems obvious that, if you request a response in uk2, you should get UK units returned. So there should be no confusion. I presume this is what you are assuming now.

So what was being assumed in January? I can not see any easy conversion factor.

EDIT: It has been pointed out that July rain ~ 6 x January rain :?

re_thanks for the explanations ok so it is possible to work around the malfunction WU by running cron tasks following the installation instructions of the template? but do you also have to edit the files “34_cron_addtoyear.php” and “w34_cron_stationcron.php”? … for live data I use the WL 2.0 api
thank you in advance
Regards

You should run the w34_cron_stationcron.php every 5 minutes and the 34_cron_addtoyear.php at 23:55
The files will be created the first time the crons run.
The data will be loaded into the day file by the station cron.
The addtoyear will add 1 line to the yearly file and 1 line to the month file.

You normally never have to change any scripts.
In this case you should change your easyweather setting as in this screenshot.

Wim

Wim


charts.jpg

thnx ok i just did cron job scheduling …
I find a file “today.txt” in my folder ./chartsmydata
I’m waiting for the execution of the cron at “23:55” to see
normally it should work :wink:
Regards


today.txt (254 Bytes)

A quick look at the scripts showed that the January release was using the single value “precipIntensityMax” instead of the current “24 * precipIntensity”. . . problem solved.