Oh, forgot to mention:
The station is not very old yet: Is it possible it posts the 9999 yearrain because it simply has not calculated it yet?!? Just theorizing :) Fred On Thursday, July 13, 2017 at 5:29:59 PM UTC+2, Fred wrote: > > Hi, > > First of all: Thank you for writing this software! Its great :) > > This is the section you requested (Full file is in my original post, but > maybe you missed it) > > [Interceptor] > # This section is for the network traffic interceptor driver. > > # The driver to use: > driver = user.interceptor > > # Specify the hardware device to capture. Options include: > # acurite-bridge - acurite internet bridge > # observer - fine offset WH2600/HP1000/HP1003, aka 'observer' > # lw30x - oregon scientific LW301/LW302 > # lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge > device_type = observer > mode = sniff > iface = enxb827eb718db1 > pcap_filter = src 192.168.2.165 and dst port 80 > > > Thanks! > > > Fred > > > On Thursday, July 13, 2017 at 5:19:35 PM UTC+2, mwall wrote: >> >> >> >> On Wednesday, July 12, 2017 at 2:38:28 PM UTC-4, Fred wrote: >>> >>> Anybody have any idea what is going wrong? >>> >>> >> fred, >> > > > >> >> please post the [Interceptor] section of your weewx configuration. >> >> it looks like your station is always sending a junk value (-9999) for >> yearrainin. yearrainin is the observation that the interceptor driver uses >> to determine the rainfall. so when your station always reports -9999, the >> driver maps that to 'None', and voila! you have no rain reported. >> >> i used yearrainin in order to minimize the effects of counter rollover, >> and because i was not seeing consistent use of rainin (is it rain since >> last sampling? in a certain time period? it seems to vary depending on >> the manufacturer and/or the firmware) >> >> it looks like your rainin is a counter, but counting since when? when >> does rainin reset? and why is there no value for your yearrainin? >> >> your station is also reporting absbaromin. this value would be preferred >> to baromin, which i assume is a derivation of absbaromin with >> altitude/temperature compensation. i'll have to see about making the >> driver prefer absbaromin if it exists. >> >> btw, at some point the wu-based portions of the interceptor probably >> belong in a separate driver that simply captures data bound for wu, either >> by sniffing or by listening. that driver *should* work with any >> manufacturer's hardware/firmware as long as they adhere to the wu protocol. >> >> m >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
