hi evan,
the operating system does not matter - the paths matter. assuming that you
installed weewx to /home/weewx/bin, you should use this form:
PYTHONPATH=/home/weewx/bin python -m user.gw1000 --test-driver
however, that assumes that there is an executable called 'python' in your
PATH. if
Hi Matt,
Thanks for the answer. I guess I'm not understanding something about this
command. I installed weewx to '/home/weewx/bin', and my python is python3
and is installed at the path you mentioned, '/usr/local/bin/python3'
So to my understanding that command should become
'PYTHONPATH=/home/
On Friday, September 24, 2021 at 2:24:09 PM UTC-4 Evan Kimberly wrote:
> So to my understanding that command should become
> 'PYTHONPATH=/home/weewx/bin /usr/local/bin/python3 -m user.gw1000
> --test-driver'
>
> but when i enter that command i receive 'PYTHONPATH=/home/weewx/bin:
> Command not
actually, i get the same behavior with either bash or ksh, at least on an
old macos system (10.14.6) - the semicolon is necessary. same thing on a
modern debian system.
so i guess the semicolon is necessary! all the many times i have done that
before i must have been in the PYTHONPATH directo
I actually wasn't sure, haha. I am currently working out of the shell built
into the GUI of TrueNAS. I just checked using 'ps -p$$ -ocommand=' and it
came back as csh.
But you are correct! I put the semicolon in and I got output. So thank you
for that! I wasn't aware it was missing.
As for the
On Friday, September 24, 2021 at 3:02:30 PM UTC-4 Evan Kimberly wrote:
> I actually wasn't sure, haha. I am currently working out of the shell
> built into the GUI of TrueNAS. I just checked using 'ps -p$$ -ocommand='
> and it came back as csh.
>
csh *definitely* has a different syntax than k
On Friday, September 24, 2021 at 3:02:30 PM UTC-4 Evan Kimberly wrote:
> Using configuration file /home/weewx/weewx.conf
>
> --- Logging error ---
>
> Traceback (most recent call last):
>
> File "/usr/local/lib/python3.8/logging/handlers.py", line 934, in emit
>
> self.socket.send(msg)
>
> OSErr
We have seen lots of instances saying you need to run 'some' kind of logger
in modern versions of weewx. I just typically install rsyslog and
everything seems to work fine after that. The issue typically pops up when
running a very minimal os or VM or container.
--
You received this message
I installed rsyslog to check it out and it popped up the following message:
Message from rsyslog-8.2104.0:
--
To start using rsyslogd(8), stop syslogd(8) if it's running and
add the following lines to rc.conf(5):
syslogd_enable="NO"
rsyslogd_enable="YES"
It's recommended to copy syslog.co
On Friday, September 24, 2021 at 1:57:04 PM UTC-7 Evan Kimberly wrote:
> Is syslog not already a logger? Is it not adequate and rsyslog more
> capable?
>
Hard to say, I'd like to say they are equivalent, but perhaps not
necessarily.
I got a lot of rsyslogd whining about my config files when I
> this doesn't seem to be written with freebsd in mind
Correct. Call in unintentionally intentional if you like but I don't use
BSD and nor do I see any other driver/extension including specific BSD
instructions. That said I am happy to get a freebsd VM up and running if
need be to deal with an
Gary - this seems to be a freebsd limitation
(see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241937)
On Friday, September 24, 2021 at 6:02:06 PM UTC-7 gjr80 wrote:
> > this doesn't seem to be written with freebsd in mind
>
> Correct. Call in unintentionally intentional if you like but I d
Gary,
Thanks so much! That's cleared the error. Now when I run the driver test, I
get no block of text, just the following message:
'Using configuration file /home/weewx/weewx.conf
Interrogating GW1000 at 192.168.0.200:45000'
Still not sure why I'm not seeing any activity, but at least the err
So now that I have the driver working, I decided to poke through some of
the options. I was able for the driver to see the IP, port, MAC address,
firmware version, and calibrations off of my GW1000. However, when I try to
see the sensors I get this error:
Interrogating GW1000 at 192.168.0.200:4
Sorry Ewan, but I don't have any time to look at this further today as I am
out the door in 20 minutes. In the interim a couple of questions for you:
1. can you run the commands you have been using but this time with the
--debug=3 command line option, eg:
$ PYTHONPATH=/home/weewx/bin python -m
Oh, and one other thing, what firmware version is your GW1000 using?
Gary
On Saturday, 25 September 2021 at 14:05:21 UTC+10 gjr80 wrote:
> Sorry Ewan, but I don't have any time to look at this further today as I
> am out the door in 20 minutes. In the interim a couple of questions for you:
>
>
I am pretty sure the semicolon is *not *what you want with Bourne shell
syntax.
1. with no semicolon, the variable is placed in the environment of the
program being executed
2. with a semicolon, it is a simple assignment to a variable in the
environment of the current shell and is *
Hi Gary,
It’s no trouble at all. I sincerely appreciate all the help you are
providing and am not in a rush. Truthfully, my time is fairly limited for
this. I’ve been trying to respond to everyone as timely as possible. I have
a three year old and a 4 month old, so my day time hours to tink
Evan,
Ah, of course, your truncated log is going to truncate all of the hex data
I was after! No matter, I think I have the problem sorted. Could you try
the v0.3.2 of the driver. You can download it with:
$ wget
https://raw.githubusercontent.com/gjr80/weewx-gw1000/master/bin/user/gw1000.py
J
Haha, yes I figured that was what was happening with the truncated debug
output, but I thought I'd show it to you regardless.
Hey that did it!!! Thanks so much, Gary! I can see the sensors with the
sensor input on the drivers, and I see the LOOP packets now while actively
running weewxd. The ht
20 matches
Mail list logo
