The Ecowitt Wittboy that I got installed on my brother’s rental property high on a hill in the UK Peak District is paying dividends.
My own peak gust this evening at 21m ASL is a lowly 74km/h. On the top of the hill it’s a different matter. In the last hour or so it’s recorded a gust of 110km/h. That beats the previous record of 107km/h…set just 2 days ago!
That gust record didn’t last long. It’s 118km/h now.
I spoke too soon. The record hasn’t updated yet. 126km/h in the last 3 minutes.
What’s this km/h stuff?
Sorry, I forgot you need it in old units. That’s 210451 furlongs/fortnight.
A technical question arises. When I was looking at the PWSWD page I definitely saw a gust of 126.8km/h reported at 23:51-ish in the wind gauge block. The wind record block only shows a peak gust of 118km/h. Any idea why that would be?
What dashboard, where?
So do you work in KM or MPH?
My weather web sites are predominantly in metric. I think some recent changes have used default imperial units in the config which I haven’t changed yet but I will be doing soon.
Very nice question, answered in the first months of pwsWD. Nobody ever noticed it since 
When using a weather-program such as WD or MB or Weewx the high-lows are registered continuously. The weather-program reads the values 24/7 and will normally miss none.
It also knows when it is 23:59:59 and closes todays values, move them to yesterday values and resets todays values.
When using a weather-program to upload to a website, it would be fine to upload all high-lows values also. But sadly that is impossible
When using direct or custom upload from the weather-station itself, there are often no high-lows at all.
The PWS_Dashboard uses a 5 minute cron to update the high-lows.
In-between higher-lower values are missed in the high-lows.
They are shown at the dashboard but only the values which are read by the cron-job are used in the history.
Another problem is time synchronisation between weather-station and website.
Therefor all measurements between 23:55 and 00:05 are not used for updating the high-lows.
Lines 55->56 in PWS_cron_stationcron.php.
$no_data_after = 2355; // Hour-minutes after wich no day data should be processed in history
$no_data_before = 0005; // Same before
So your “126.8km/h reported at 23:51” value was not stored as
Wim
Hi WIM
could you change these to
$no_data_after = 2358; // Hour-minutes after wich no day data should be processed in history
$no_data_before = 0002; // Same before
?
If I understand Wim correctly data only gets into history when the cron job runs, so I don’t think changing the times would help.
Ah, okay, 78 mph . Now that means something here in America! That’s quite the gust. I haven’t experienced wind speeds that high since I lived in Florida with a few tropical cyclones.
As bitsostring already said, it is the time-frame for discarding the data.
It is necessary as often the uploads contain invalid date/times aruond midnight. Either from the weather-station console or from the local computer.
Be aware that cron-servers are busy at the exact hour, extremely busy at 00:00 and to busy at 00:00 every end-of-month day.
A lot of high-lows were invalid because of different times on station-> pc → website.
Multipele times we had to enlarge the discard-timeframe because todays max-min were emptied to early.
But you can set adept those settings yourself, if you are sure your station-computer-website time are close enough.
Succes,
wim
Sorry, should have looked at the station map 
Thanks Wim. I’m sure your “99% chance” is the correct one. If it was in the data then it would have appeared as the all-time high record. I was just fortunate to catch a fleeting glimpse of it when I should have been sleeping!
I will have reconsider my original plans. I was thinking of building a Raspberry Pi to sit with the Ecowitt gateway and gather data locally and then upload data from that. It’s not that simle though, because being so remote it suffers from relatively regular power cuts so I need to make sure that the Pi configuration is very robust. Ideally it needs to run from a SSD which is less likely to corrupt than an SD card and have a UPS to keep the GW2000 and Pi running would.
Next maintenance slot will be at the end of July so I’ve got a few months to consider my options.