logically that makes sense - a windgust 'should' be a wind speed sustained I think for 2-3 seconds in pure metereological terms. With RF it is not possible to have a windgust if uploading data every few seconds. WU probably, rightly, ignore windgust values in RF uploads but will accept it in 5 minute archive periods. I would imagine WU try and minimise the amount of data updated on RF uploads and probably update most values only on archive intervals. To me this makes sense and is logically correct, since most metereoligical values except fow windspeed and winddirection do not really change that quickly.
On Saturday, 17 August 2019 10:44:02 UTC+3, kar ss wrote: > > Hi Gary, you are right, there was no rain event during the log period > (reason for zero rain values), I did check the log during an earlier rain > event and indeed weewx was able to log the rain event as well as the rain > rate. With respect to the data being sent by weewx to WU, I don't see any > discrepancy in the data, console data matches with the WU data for rain > total, just that the data gets updated every 5 minutes in WU instead of the > expected RF updates, while WU temp, wind, wind direction all follow RF > updates, only rain total and rain rate are reported every 5 minutes. So > based on your inputs, I have to conclude that the issue is with WU. > Yesterday I turned of the RF update by modifying the weewx.conf file > (changed RF value from true to false), just to see how the WU data looks > and found an interesting observation, when RF was turned ON WU did not > report any wind gust, but after turning OFF RF updates, WU is reporting > wind gust. This is a bit strange to me. Seems WU still has some issues with > respect to the way the data is reported based on incoming data from weewx. > SS > > On Friday, 16 August 2019 02:42:39 UTC+5:30, gjr80 wrote: >> >> Ok, so we can see that WeeWX is indeed sending RF updates to WU many >> times each archive period. What we can’t see is any non-zero rain values >> being sent (assume this is because it was not raining during the log >> extract - if it was raining we have a more fundamental data issue). What >> you should do now investigate what happens when it does rain; there are two >> checks you can do here. Firstly you can do a gross error check just by >> looking at the RF entries for dailyrainin and rainin in the log; are they >> non-zero? are they sensible, do they seem to agree with the console? You >> can also do a more involved detailed analysis, this time run WeeWX directly >> while it is raining. Capture the console output for an archive period or >> two and then go back and look at the log entries for the corresponding >> period. If rainin and dailyrainin agrees with the loop rain data then the >> issue is WU. If rainin or dailyrainin does not agree with the loop data >> then there is a WeeWX/station issue. >> >> Gary > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/38a411b6-52a2-466b-973d-2dbbd84c08f5%40googlegroups.com.
