Hi Brian,
ver 10.37S43 full install (with later zip added)
The meteotemplate is uploading at the one minute rate that I initially set. The database is updating every 5 minute without the cron job. But I cannot get work properlyat the 5 second rate. I have tried deleting the information in the meteotemplate setup setting to off and exiting WD. Restart WD, enter info, setup to 5 seconds, turn on. Restart WD.
The data (wind speed & direction) on steeelSeries block and plugin, current block, and gauges block will remain constant for one minute, however the time display will advance every 5 seconds…
I have added the meteotemplate API to wxstatus.php (10th item down) and the file is updating every 5 seconds (click on ‘Refresh Status Data’ to confirm)…
but the not the content, other then the time, is updating at one minute rate.
Thanks,
Gus
Question for Jachym…
After selecting api in the setup menus, should the path to file be left blank?
yes, I see now, that I am using 1 minute average
but if the update rate is faster than 1 minute then I need to be using current data instead
I will get a new update up of WD to resolve that
Downloaded bld 44 zip file
Now seeing the upload problem described in this thread… http://discourse.weather-watch.com/t/63749
No auto load and manual test/update may work once after WD restart.
*** Inconsistent may or may not show success box.
Gus
Bld 44 selected one minute and it is auto and manual uploading. But not at 5 sec.
** Tried every 30 second -also did not work
one minute is the only working selection now
the auto data update (any update rate) is sent via the cronhttpget.exe
what shows in the file
sentcustomhttget.txt
where WD is located
when 5 seconds is used
what I will do is log to that file what was actually sent
but it could also be that the 5 seconds might be stomping on each other
i.e try testing the every 30 seconds
thats good
what happened was when I added more real time data for when doing faster updates I had used a wrong variable which was not formated correctly and that was throwing out the api call #-o :oops: