I have a weewx-sdr driver receiving data over usb from rtl-sdr from an
rtl-sdr radio receiver dongle. The radio receiver gets outdoor data from
an Acurite Atlas. The inside weather data comes from an arduino over usb.
The weewx server is on a raspberry pi. I modified the weewx-sdr driver
Im trying to install the weewx-inteceptor extension with some questions.
When I actually get to downloading the wget from the internet do i need to
put it into the weewx file or just on the home page?
also it wont let me unzip it to where id be even able to install it and run
it. it keeps
Here is the dump of traffic:
weewx@raspberrypi:~ $ sudo tcpdump host 192.168.50.9
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
19:49:15.918021 IP L7-F5C2FC.17834 > RT-AC68U-30F8.domain: 53873+
That worked with getting the driver to load. Here is the error I get once
I have it running:
weewx@raspberrypi:~ $ sudo PYTHONPATH=/usr/share/weewx python
/usr/share/weewx/user/interceptor.py --device=wu-client --mode=sniff
--iface=eth0 --filter="src 192.168.50.9 and dst port 80"
Tom - buried in his messages were this - note it is a non-privileged
installation, so it might very well be what you noted as a potential
installation user error.
weewx@raspberrypi:~ $ pip3 list --verbose | grep pcap
pypcap1.3.0 /home/weewx/.local/lib/python3.9/site-packages
Tom - what's happening is he's not finding the pcap python module when
running as root, but 'is' finding it when running as a non-privileged user,
so my guess (guess) is there are multiple python interpreters installed,
although he has so many old variants of a pip installed (or attempted
I'm not following this exchange closely, so it's entirely possible I don't
know what's going on.
What I will note is that both the shell path and PYTHONPATH are completely
different if the python interpreter is run with "sudo". If you installed
pypcap using pip, this could make you vulnerable.
2023-02-21-raspios-bullseye-arm64.img
weewx@raspberrypi:~ $ uname -a
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023
aarch64 GNU/Linux
weewx@raspberrypi:~ $ which python
/usr/bin/python
weewx@raspberrypi:~ $ sudo which python
[sudo] password for weewx:
Lets see the following:
- uname -a
- which python
- sudo which python
- echo $PATH
- sudo bash -c 'echo $PATH'
It looks like you're running a 64-bit os perhaps ? Which one specifically ?
Other than some odd 32-bit vs. 64-bit thing happening, I can only conclude
that you
weewx@raspberrypi:~ $ dpkg -l | grep pcap
ii libpcap0.8:arm64 1.10.0-2
arm64system interface for user-level packet capture
ii libpcap0.8-dev:arm64 1.10.0-2
arm64development library and header
>From a clean RaspiOS that works
pi@pi4jr:~ $ dpkg -l | grep pcap
ii libpcap0.8:armhf 1.10.0-2
armhfsystem interface for user-level packet capture
pi@pi4jr:~ $ pip3 list --verbose | grep pcap
pypcap1.3.0
weewx@raspberrypi:/usr/share/weewx/user $ python --version
Python 3.9.2
weewx@raspberrypi:/usr/share/weewx/user $ python3 --version
Python 3.9.2
weewx@raspberrypi:/usr/share/weewx/user $ ^C
weewx@raspberrypi:/usr/share/weewx/user $ sudo PYTHONPATH=/usr/share/weewx
python
Again, your python is messed up or you have python (2) and python3
installed.
This worked on a clean raspios. Same as your command just with an absolute
path to interceptor.py
sudo PYTHONPATH=/usr/share/weewx python
/usr/share/weewx/user/interceptor.py --device=wu-client --mode=sniff
sudo PYTHONPATH=/usr/share/weewx python interceptor.py --device=wu-client
--mode=sniff --iface=eth0 --filter="src 192.168.50.9 and dst port 80"
Traceback (most recent call last):
File "/usr/share/weewx/user/interceptor.py", line 2671, in
device =
mike@raspberrypi:/usr/share/weewx/user $ PYTHONPATH=/usr/share/weewx python
interceptor.py --device=wu-client --mode=sniff --iface=eth0 --filter="src
192.168.50.9 and dst port 80"
Traceback (most recent call last):
File "/usr/share/weewx/user/interceptor.py", line 2671, in
device =
On Monday, April 24, 2023 at 9:34:36 AM UTC-7 Michael wrote:
I am trying to install WeeWx on my Raspi with Interceptor with a WU-Client
coming from 192.168.50.9. So far I am ending up with the following error
message when trying to run the driver directly and no results in WeeWx.
Thank you, appreciated.
> On 19 Apr, 2023, at 16:28, matthew wall wrote:
>
>
>> On 19 Apr 2023, at 15:32, Karen K wrote:
>>
>> I realized the Maxbotix Wiki page, and from my location no picture is found.
>
> karen found the maxbotix guide while it is still in draft form. pictures and
>
> On 18 Apr 2023, at 17:49, weatherl...@gmail.com
> wrote:
>
> Matthew, do you have a site showing the details of how you have connected up
> the Maxbotix nd associated devices?
the maxbotix recipe is now online:
https://github.com/weewx/weewx/wiki/maxbotix-recipe
i still consider this a
> On 23 Apr 2023, at 14:56, Cat22 wrote:
>
> I have a C program (Linux) that gets the forecast and inserts it index.php,
> it needs to run right before the rsync report. The trouble is i cant get it
> patched into rsyncupload.py properly
it sounds like you tried to modify the
19 matches
Mail list logo
