[weewx-user] Re: Can't get interceptor to read data in sniff mode
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 :)
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/c4ca3d00-9f17-40a2-a4fd-c34bf51f9a10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Can't get interceptor to read data in sniff mode
My apologies. I misread the reference to "Acurite access" as meaning "access to Acurite" rather than the Access device. On Sunday, May 19, 2019 at 6:09:19 PM UTC-4, mwall wrote: > > 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 > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a765269d-0fcc-468c-953b-466c530f216a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Can't get interceptor to read data in sniff mode
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 -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ef676e71-d8b1-478f-bc58-e036c2e5e7b9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Can't get interceptor to read data in sniff mode
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 -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9277010a-a165-41c7-9d19-97081511d4ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Can't get interceptor to read data in sniff mode
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: > > 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 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=" and port 80" > I get nothing. > > However, if I do this: > ~/Downloads$ sudo tcpdump -U -i wlp2s0 src 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 '] > > > > > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dd9d09dc-d5e4-4c08-a59f-72f1993f9092%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Can't get interceptor to read data in sniff mode
the wiki page has been updated to reflect the changes at acurite: https://github.com/weewx/weewx/wiki/acuritebridge -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/fd19ea3c-8d3e-49f8-9c40-f2bfc0d7cfc3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Can't get interceptor to read data in sniff mode
See this message and the rest of the thread: https://groups.google.com/d/msg/weewx-user/0e2E3F7EG7Y/mVv7oUZ1BgAJ 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. 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 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=" and port 80" > I get nothing. > > However, if I do this: > ~/Downloads$ sudo tcpdump -U -i wlp2s0 src 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 '] > > > > > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d7af0342-4ca1-4bbf-a34d-e14ca1cdda2d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
