Interesting. I just spent 10 minutes watching a Davis VP2 on WU using RF
displaying and updating wind gust data. It also happened to be raining and
rainfall data was updating albeit at a slower rate (as expected given a Davis
does not update rainfall data as frequently as wind). The station
tbh it is not worth the effort!! imho WU should stop trying to cater for
rf and just sort out handling archive records correctly and consistently.
RF is largely pointless. How often do you look at the weather vane for 2
seconds and say that is the wind direction - you don't - i would put
Thanks Andrew, your explanation of the wind gust is agreeable to me. But WU
updates rain data at more frequent intervals for other stations in my
neighborhood, also when I connect the Acurite console to WU through
PC-Connect the rain data is displayed using RF. So I think WU treats my RF
rain
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
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
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
Gary, thanks for your reply. I am attaching the syslog file an
On Thursday, 15 August 2019 17:59:39 UTC+5:30, gjr80 wrote:
>
> The point of running Weewx directly was to see the loop and archive data
> that Weewx is processing and you can then reconcile this against what is
> appearing on WU.
The point of running Weewx directly was to see the loop and archive data that
Weewx is processing and you can then reconcile this against what is appearing
on WU. If you set debug=2 you will see the data posted to WU on the log. This
was never going to fix anything, rathet if will provoke a
Hi Gray,
I tried to run Weewx directly during a rain event and this also did not
help, the rain data gets updated to wunderground only at 5 minutes
interval. But I made one observation, both the weewx seasons report and the
the rain data in wunderground gets updated exactly at the same time.
Thanks Gary, I can check the rain data only during the next rain event. I
am attaching the syslog file as a text document. Hope this helps you get
some additional insight into the issue.
SS
On Thursday, 18 July 2019 15:22:42 UTC+5:30, gjr80 wrote:
>
> Ok, so you should be seeing rain info
Ok, so you should be seeing rain info posted to WU more frequently than once
every 5 minutes. If you edit weewx.conf and set debug = 2 then restart WeeWX
you will see in the log the data that is being posted to WU. It should appear
every 18 or 36 odd seconds. Is rain data being posted? Can you
Hi Gary,
The modified command pointing to the weewx.conf file works, I could now see
information about the loop packets that is being received. The partial loop
packets send rain total every 36 seconds and rain rate every 18 seconds.
I will run this command for a while to see the actual update
You will need to provide the path to weewx.conf, try something like:
$ sudo weewxd /etc/weewx/weewx.conf
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
Hi gjr80,
Thanks for the reply. I tried your suggestion, I stopped the weewx running
in deamon mode using the command: *sudo /etc/init.d/weewx stop*
and tried to run it directly as suggested by you using the command line: *sudo
weewxd weewx.conf,* but I am getting the following error message:
Thanks Andrew.
On Tuesday, 16 July 2019 16:58:18 UTC+5:30, Andrew Milner wrote:
>
> rapid fire display is in the hands of WU. If the station provides the
> data then weewx will upload it. However not all stations provide all data
> in every loop packet - and this could be what you are seeing.
rapid fire display is in the hands of WU. If the station provides the data
then weewx will upload it. However not all stations provide all data in
every loop packet - and this could be what you are seeing.
On Tuesday, 16 July 2019 14:05:49 UTC+3, kar ss wrote:
>
> Hi All,
>
> I recently
16 matches
Mail list logo
