K, so resetting the rig was never going to help, and did not.
I switched capture strings, hoping that something about teeing the output
was the problem, and it was not.
I went and looked at the tee'd output, and the POSTs it is intercepting
appear correct:
~~~
T 192.168.1.73:4909 -> 54.228.205.188:80 [AP]
mac=0004a369e0d6&id=c2&pv=0&lb=0&ac=0®=1809&lost=0000&baro=1012&ptr=0&wfor=3&p=1
T 192.168.1.73:4916 -> 54.228.205.188:80 [AP]
mac=0004a369e0d6&id=c2&pv=0&lb=0&ac=0®=1809&lost=0000&baro=1012&ptr=0&wfor=3&p=1
~~~
But by the time interceptor is done with it, it seems to be lacking the
wfor arg. Ten, as I'm sitting there watching it, it starts to behave:
Tee'd packet:
T 192.168.1.73:4924 -> 54.228.205.188:80 [AP]
mac=0004a369e0d6&id=c2&pv=0&lb=0&ac=0®=1809&lost=0000&baro=1012&ptr=0&wfor=3&p=1
Interceptor log:
ec 10 09:09:55 raspberrypi weewx[563]: interceptor: ServerThread: POST:
mac=0004a369e0d6&id=c2&pv=0&lb=0&ac=0®=1809&lost=0000&baro=1012&ptr=0&wfor=3&p=1
Dec 10 09:09:55 raspberrypi weewx[563]: interceptor: ServerThread: POST:
mac=0004a369e0d6&id=c2&pv=0&lb=0&ac=0®=1809&lost=0000&baro=1012&ptr=0&wfor=3&p=1
Dec 10 09:09:55 raspberrypi weewx[563]: interceptor: MainThread: raw data:
mac=0004a369e0d6&id=c2&pv=0&lb=0&ac=0®=1809&lost=0000&baro=1012&ptr=0&wfor=3&p=1
Dec 10 09:09:55 raspberrypi weewx[563]: interceptor: MainThread: raw
packet: {'lost.:.0004a369e0d6': '0000', 'ac.:.0004a369e0d6': '0',
'wfor.:.0004a369e0d6': '3', 'ptr.:.0004a369e0d6': '0', 'lb.:.0004a369e0d6':
'0', 'baro.:.0004a369e0d6': 1012.0, 'dateTime': 1481389796,
'id.:.0004a369e0d6': 'c2', 'p.:.0004a369e0d6': '1', 'pv.:.0004a369e0d6':
'0', 'reg.:.0004a369e0d6': '1809', 'usUnits': 17, 'mac.:.0004a369e0d6':
'0004a369e0d6'}
Dec 10 09:09:55 raspberrypi weewx[563]: interceptor: MainThread: mapped
packet: {'usUnits': 17, 'dateTime': 1481389796}
Dec 10 09:09:55 raspberrypi weewx[563]: interceptor: MainThread: raw data:
mac=0004a369e0d6&id=c2&pv=0&lb=0&ac=0®=1809&lost=0000&baro=1012&ptr=0&wfor=3&p=1
Dec 10 09:09:55 raspberrypi weewx[563]: interceptor: MainThread: raw
packet: {'lost.:.0004a369e0d6': '0000', 'ac.:.0004a369e0d6': '0',
'wfor.:.0004a369e0d6': '3', 'ptr.:.0004a369e0d6': '0', 'lb.:.0004a369e0d6':
'0', 'baro.:.0004a369e0d6': 1012.0, 'dateTime': 1481389796,
'id.:.0004a369e0d6': 'c2', 'p.:.0004a369e0d6': '1', 'pv.:.0004a369e0d6':
'0', 'reg.:.0004a369e0d6': '1809', 'usUnits': 17, 'mac.:.0004a369e0d6':
'0004a369e0d6'}
Dec 10 09:09:55 raspberrypi weewx[563]: interceptor: MainThread: mapped
packet: {'usUnits': 17, 'dateTime': 1481389796}
I'll watch this a bit longer today and see if I can't unravel this.
-SR
On Saturday, December 10, 2016 at 8:34:32 AM UTC-8, Sam Roza wrote:
>
> Ah yeah. It wasn't obvious earlier what was missing, but there it is:
>
> Dec 4 10:40:04 raspberrypi weewx[17396]: interceptor: ServerThread: POST:
> mac=0004a369e0d6&id=c2&pv=0&lb=0&ac=0®=1809&lost=0000&baro=1015&ptr=0&wfor=2&p=1
>
> Let me reset the rig and see what happens. I don't recall any changfes
> being made to it 6 days ago that would have led to this occurring.
>
> -SR
>
> On Saturday, December 10, 2016 at 8:27:37 AM UTC-8, Sam Roza wrote:
>>
>> Hi Matt,
>>
>> I am on weewx 3.6.2, interceptor .20 as of yesterday with no change. I
>> might reboot all and see if that fixes things.
>>
>
>
>
--
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.
