Temps suddenly 0 F

[pwsdashboard]

@meteocaldas post:20

Hi Wim
First of all thank you sooooo much for all your fantastic work in updating and improving this “beauty”!

I decided to try the last version, without updating from the previous, so I made a new install 2 days ago. Everything is perfect and you made it in such a way that installation could not be easier even for dummies like me!

However, I am having the same problem as described here in this topic, as min temperature value for yesterday is recorded as zero. To make things more confusing, graphs show correct values and no zero!
The odd thing here is that, as picture 1 shows, it says that min temp today was recorded at 23:59 (of yesterday?)

Also, when I run the editor (picture 2 ) time shows 11:59 instead of 23:59. Does the editor show AM-PM times or should it show 24h times?

Am I doing something wrong?
Thanks.

https://meteolitoral.com/pwsWD

We do not process weather-values between 23:55 and 00:05
Some weather-programs upload “invalid” information around midnight. f.i. a zero for temp or min-temp

Also a time difference between the server and your cumulus station can cause this.

Therefor change lines 41-42 in PWS_cron_stationcron.php from

$no_data_after          = 2355; // Hour-minutes after wich no day data should be processed in history
$no_data_before         = 0005; // Same before

to

$no_data_after          = 2350; // Hour-minutes after wich no day data should be processed in history
$no_data_before         = 0015; // Same before

Also read the topic about this No High/Lows, where is history and graphs data used for, and ? cron ?
There you find how to update those files.

Thanks for using the dashboard.
And for your compliments :D, as it really helps me to continue giving support.

Wim

[meteocaldas]

@wvdkuil post:21

Also a time difference between the server and your cumulus station can cause this.

Therefor change lines 41-42 in PWS_cron_stationcron.php from

$no_data_after          = 2355; // Hour-minutes after wich no day data should be processed in history
$no_data_before         = 0005; // Same before

to

$no_data_after          = 2350; // Hour-minutes after wich no day data should be processed in history
$no_data_before         = 0015; // Same before

Wim

Hi Wim
Thank you sooooo much for this fantastic “realtime” support!
I have made changes in the cronjob php and that should solve the problem! As a matter of fact I have 5 hour difference between my station in Portugal and the server in U.S. and had some problems in the past with some scripts due to this difference, so I will double check if this difference is interfering or not.
Thanks!

hhtps://meteolitoral.com/pwsWD

[pwsdashboard]

@meteocaldas post:22

Hi Wim

As a matter of fact I have 5 hour difference between my station in Portugal and the server in U.S. and had some problems in the past with some scripts due to this difference, so I will double check if this difference is interfering or not.

The 5 hours would not be a problem as the scripts do everything with the exact home-timezone in Portugal.
The problem occurs when the cumulus pc is 10-15 minutes before or after the server time for you local timezone.
Then an upload which we should reject arrives in the allowed time 00:05 - 23:55
That is why we have set the timeframe wider.
Wim

[ms372591]

@wvdkuil post:21

We do not process weather-values between 23:55 and 00:05
Some weather-programs upload “invalid” information around midnight. f.i. a zero for temp or min-temp

Also a time difference between the server and your cumulus station can cause this.

Therefor change lines 41-42 in PWS_cron_stationcron.php from

$no_data_after          = 2355; // Hour-minutes after wich no day data should be processed in history
$no_data_before         = 0005; // Same before

to

$no_data_after          = 2350; // Hour-minutes after wich no day data should be processed in history
$no_data_before         = 0015; // Same before

Also read the topic about this No High/Lows, where is history and graphs data used for, and ? cron ?
There you find how to update those files.

Thanks for using the dashboard.
And for your compliments :D, as it really helps me to continue giving support.

Wim

I can attest that this works I’ve been using this for a few weeks and it’s been fine. I did change the $no_data_before to 00:10 just to test it out and that has worked as well.

PWS_Dashboard at Belcamp, MD

[meteocaldas]

@wvdkuil post:23

The 5 hours would not be a problem as the scripts do everything with the exact home-timezone in Portugal.
The problem occurs when the cumulus pc is 10-15 minutes before or after the server time for you local timezone.
Then an upload which we should reject arrives in the allowed time 00:05 - 23:55
That is why we have set the timeframe wider.
Wim

Bingo!
Problem solved and tonight rollover was perfect, after making cron file timeframe wider.
You are absolutely right because I had already noticed that my cumulus pc times and my server times are somewhat different, but I would never guessed that it could be the cause for this problem.
Thank you soooo much Wim.

https://meteolitoral.com/pwsWD