Can't get interceptor to read data in sniff mode

[Ray Pfaff]

I've been trying to get the 0.41 version of weewx interceptor working with my Acurite access and haven't had any luck.  I can read packets to wunderground if I do a tcpdump and I've even written a python script to extract the data and put it in a database.  But when I run interceptor stand alone, I get nothing on screen or in the syslog.  The relevant parts of weewx.conf  is so:

    # Set to type of station hardware. There must be a corresponding stanza

    # in this file with a 'driver' parameter indicating the driver to be used.

    station_type = Interceptor

[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 = wu-client

    port=80

    mode=sniff

    iface= wlp2s0

    pcap_filter= src <access_ip_address> and dst port 80

wu

I've tried 'acurite-device' and 'wu-client' for the device type both in the configuration and on the command line.  --deivce='wu-client' isn't a valid input on the command line.   When I run the interceptor:

~/Downloads$ sudo PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py --mode=sniff --iface=wlp2s0 --filter="<access_ip_address> and port 80"

I get nothing.

However, if I do this:

~/Downloads$ sudo tcpdump -U -i wlp2s0 src <access_ip_address> and port 80 | ./weather.py

I get:

['2019-05-19 08:03:11', '30.04', '99', '66.2', '0', '225', '0', '45', '65.9', '0.02', '0.00 ']

['2019-05-19 08:13:23', '30.04', '96', '67.6', '1', '203', '2', '203', '66.4', '0.02', '0.00 ']

['2019-05-19 08:32:53', '30.05', '95', '68.0', '0', '203', '0', '203', '66.5', '0.02', '0.00 ']

[RobbH]

See this message and the rest of the thread:

https://groups.google.com/d/msg/weewx-user/0e2E3F7EG7Y/mVv7oUZ1BgAJ

[mwall]

the wiki page has been updated to reflect the changes at acurite:

https://github.com/weewx/weewx/wiki/acuritebridge

[Ray Pfaff]

Am I missing something?  Both of those apply to the bridge, not the access.  I do have access to a server that receives my data as myacurite.com (and for that matter wunderground.com) both receive data from it.

On Sunday, May 19, 2019 at 8:52:51 AM UTC-4, Ray Pfaff wrote:

[mwall]

On Sunday, May 19, 2019 at 5:44:55 PM UTC-4, Ray Pfaff wrote:

Am I missing something?  Both of those apply to the bridge, not the access.  I do have access to a server that receives my data as myacurite.com (and for that matter wunderground.com) both receive data from it.

sorry about that, i missed the 'access' bit.

with the device type as wu-client, could you set debug=1 in weewx.conf then post the log output from the time weewx start until the first reporting cycle?

m

[mwall]

On Sunday, May 19, 2019 at 8:52:51 AM UTC-4, Ray Pfaff wrote:

I've been trying to get the 0.41 version of weewx interceptor working with my Acurite access and haven't had any luck.

could you try using 0.45?

the device_type of wu-client was not added until 0.43

also, there were some significant pcap changes in 0.42

[RobbH]

My apologies. I misread the reference to "Acurite access" as meaning "access to Acurite" rather than the Access device.

[Ray Pfaff]

Okay, using 0.45 and I turned debug on.  I also manually turned the interface into promiscuous mode since it seemed to be resetting it.  I have this in the logs:

May 20 14:43:54 owner-ThinkPad-X131e kernel: [3031522.732566] device wlp2s0 entered promiscuous mode

May 20 14:44:59 owner-ThinkPad-X131e interceptor[6593]: interceptor: MainThread: mode is sniff

May 20 14:44:59 owner-ThinkPad-X131e interceptor[6593]: interceptor: MainThread: sniff iface=wlp2s0 promiscuous=0

May 20 14:44:59 owner-ThinkPad-X131e interceptor[6593]: interceptor: MainThread: sniff filter 'src <ip> and port 80'

May 20 14:44:59 owner-ThinkPad-X131e interceptor[6593]: interceptor: MainThread: pylibpcap (unknown)

And now I'm seeing this, but I don't think this is right (???)

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

identifiers: {}

[Roelof Schuiling]

Just chiming in because I am stuck with the same result running the interceptor driver directly: identifiers {}. My question is here:
https://groups.google.com/forum/m/#!topic/weewx-user/DHDNdfX6ZVw

If you learn anything I'd love to hear about it :)