Trying to figure out why rain data does not agree. Why would pwsWD not be receiving good data?
The values pwsWD uses are downloawded from WeatherFlow server and saved in jsondata/weatherflow.txt
These are all precipitation values in that file, they are metric so in mm :
[precip] => 0
[precip_accum_last_1hr] => 0
[precip_accum_local_day] => 0
[precip_accum_local_day_final] => 0
[precip_accum_local_yesterday] => 0.337787
[precip_accum_local_yesterday_final] => 1.030595
[precip_analysis_type_yesterday] => 1
[precip_minutes_local_day] => 0
[precip_minutes_local_yesterday] => 16
[precip_minutes_local_yesterday_final] => 16
There are two “rain-yesterday” values in the file, the measured values by your weather-station, which we use in pwsWD as we want to know what our device measures.
And the “recalculated” values from a weatherflow server algorithm based on other weather-stations / metars in your area.
Your station measured 0.337787 mm rain, those are shown on the pwsWD dashboard.
The weatherflow server detected higher values from other sources in your area and adjusted your measured rainfall to 1.030595 mm.
The weatherflow website shows their recalculated values, not the real values measured.
Hope this explains it,
Wim
It depends on what you yourself want to be the “good data”
Currently the rain-data used is: → the rain amount measured by your station
If you want to have your weather-website to show the same amount as the “enhanced” value on the tempest website we just modify lines 740 and 742 in the livedata script to use the enhanced value.
Otherwise we can set this topic to “solved”.
Regards,
Wim
I stopped running WD and switched pwsWD to use WF-API to collect data. Would this affect the rain data? I don’t remember having this issue when I was using the WD clientraw file…
Hopefully I made this change…will see how it responds.
Here’s the changes I made:
if (array_key_exists (‘precip_accum_local_yesterday_final’,$item) )
{ $weather[“rain_yday”] = convert_precip ($item[‘precip_accum_local_yesterday_final’],$from,$to); }
Would making these changes affect or cause this?
Seems strange that I get the red mark when everything says ok…
A “synchronisation problem”
PWS_load_files is run every 5 minutes by the cron-job which also saves the values of that execution for the pop-up
PWS_load_files is also run for every active visitor, in your setup every 90 seconds. If it detects a stalled file it displays the red !.
But it can not update the data for the pop-up.
It can therefor happen that one file is too old for a visitors situation and the red exclamation shows.
But for the pop-up the file is OK as that data was from some time ago, from the last time the cron-job ran.
Regards,
Wim
Well the red ! is gone today. I’ve never had a problem with this indicator being “wrong” so this seemed out of character. Thanks for the simple explanation.
Still waiting on rain to see if my change makes a difference before marking it solved.
I give up. I can’t troubleshoot or fix this when I don’t know where the numbers are coming from…I think the BIG problem is Tempest altering the rain amount after the fact.
What Tempest shows:
What pwsWD shows:
I think the haptic rain sensor is totally useless…it doesn’t correctly measure rain amounts, and, depending on the size of the rain drops, it doesn’t even get a passing grade on detecting rain. And then the Tempest folks “correct” the amount, after the fact, to what they think you received for rain.
I recommend folks stick to the Davis VP2 for reliable and accurate measurements.