Thanks to all! This is the command that finally worked to show the Interceptor help message:
PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py --help This is on Debian, with Weewx installed using dpkg. (I see now that that's no longer a recommended way to install.) So now I think I'm finally ready to try to capture some packets from the Bridge.... as soon as I have a working bridge. Can I safely assume that there are no known unbricking strategies, and I should start looking for another? On Wednesday, March 7, 2018 at 10:09:41 PM UTC-5, mwall wrote: > > > > On Wednesday, March 7, 2018 at 9:20:31 PM UTC-5, RobbH wrote: >> >> >> Meanwhile, I've encountered another issue, that I think is independent of >> the hardware issues. Installation of the Interceptor appeared to be >> successful, but I am unable to run the driver directly, following the >> directions in the readme file. This command: >> >> PYTHONPATH=bin python bin/user/interceptor.py --help >> >> produces this error: >> >> python: can't open file 'bin/user/interceptor.py': [Errno 2] No such file >> or >> directory >> >>> >>> > when using relative paths, the directory in which you invoke the command > matters: > > cd /home/weewx > PYTHONPATH=bin python bin/user/interceptor.py --help > > or you can use absolute paths to do it from anywhere: > > PYTHONPATH=/home/weewx/bin python /home/weewx/bin/user/interceptor.py > --help > > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
