Edited my last post.... It has been deleted.

After further researching the duplicates I think they are coming from the 
bridge both broadcasting to the accurate api, and then immediate 
broadcasting to the weather underground api. Not sure I can get around that 
using the tcpdump command line...

GET 
/weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E06B15C&mt=5N1x31&sensor=00002179&windspeedmph=0&winddir=113&rainin=0.00&dailyrainin=0.55&humidity=50&tempf=59.2&dewptf=41&baromin=29.35&battery=normal&rssi=3
 
HTTP/1.1
Host: hubapi.myacurite.com
User-Agent: Hub/224
Connection: close

GET 
/weatherstation/updateweatherstation.php?ID=KCATHOUS110&PASSWORD=XXXXXXXX&dateutc=now&action=updateraw&realtime=1&rtfreq=36&id=24C86E06B15C&mt=5N1x31&sensor=00002179&windspeedmph=0&winddir=113&rainin=0.00&dailyrainin=0.55&humidity=50&tempf=59.2&dewptf=41&baromin=29.35&battery=normal&rssi=3
 
HTTP/1.1
Host: rtupdate.wunderground.com
Connection: close


On Friday, November 4, 2016 at 9:45:30 PM UTC-7, Brad Tucker wrote:
>
> Mwall,
>
> Thanks for getting back to me so quickly.
>
> Im not sure if the bucket tips where within an hour of these logs. I went 
> up to work on the sense and triggered the tips. I came back in and started 
> fiddling with weewx after. I think it was roughly an hour later... Cant be 
> exact though.
>
> Ill have to check if the bucket tips show up in "rainin" I have to assume 
> they do, however I didn't have debug on to see them. The problem is they 
> aren't making there way to the database. They make there way to weather 
> underground and to myacurite so I think it safe to say they are being 
> broadcast. Happy to bring the station in and do bucket tips while I check 
> the logs if you'd like to me in the morning. Don't want to get back up on 
> the roof tonight in the dark ;)
>
> "dailyrainin" is being triggered by the bucket drops. I hit it a few times 
> and thats why you are seeing the .55" in the previous logs.
>
> Im not sure where the duplicate data is coming from. One says 
> *"ServerThread: POST:"* and the other says *"MainThread: raw data:"*  Are 
> those really duplicate or just 2 ways of displaying the same data?
>
> Thanks again for your help,
> Brad
>
>
>
>
>
> On Friday, November 4, 2016 at 9:26:05 PM UTC-7, mwall wrote:
>>
>> On Friday, November 4, 2016 at 10:42:37 PM UTC-4, Brad Tucker wrote:
>>>
>>> For some reason Rain is not being logged to the system w/ the 
>>> interceptor model. I accidentally tripped the rain seƱor while working on 
>>> the unit today, and the acurite display is reporting .55 inches however my 
>>> plots show 0 as do the stats. I took a look at the database to make sure 
>>> nothing is being logged and there are all zeros in the rain fields. Does 
>>> anyone have any ideas?
>>>
>>
>> brad,
>>
>> is the output you posted from immediately after the bucket tip, or more 
>> than an hour after the bucket tip?
>>
>> if you do some bucket tips, do they show up for both rainin and 
>> dailyrainin, or only dailyrainin?
>>
>> wu defines the 'rainin' parameter is amount of rain in the past hour - a 
>> sliding window.  it defines the 'dailyrainin' parameter is the amout of 
>> rain since the start of the day.  i assume that the acurite bridge is using 
>> the same definitions, since it is posting to wu.
>>
>> weewx expects 'rain' to be the amount of rain in the last interval, 
>> whether that interval is a LOOP packet or an archive record.  so it needs 
>> to calculate the difference between consecutive dailyrainin values.
>>
>> the interceptor was using rainin instead of dailyrainin for the delta.  
>> this has been fixed at commit 231fa14.
>>
>> btw, your POSTs contain duplicate data.  it is harmless, but you might 
>> want to figure out where that is coming from.
>>
>> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to