ing will be picked up e.g. by some index.php
>> file.
>>
>> The posting in Ecowitt protocol will always look like
>>
>>
>> http://IP-or-URL/path-from-wsview-app/index.php&PASSKEY=xxxxxx&stationtype=
>>
>> .
>>
>> the
Forwarded Message
Subject: [weewx-user] Re: Pulling my hair - one weird issue after the
other [4]
Date: Tue, 3 Aug 2021 14:28:28 +0200
From: Rainer Lang
To: Konrad Skeri Ekblad
I think this side effect is due to a recent change of Interceptor.py to
show also
e interceptor driver filters out the PASSKEY, stationtype and other not
> observation related parts of the posted string and takes only the
> observation related portions e.g. windgustmph=5.82
>
>
> Forwarded Message
> Subject: [weewx-user] Re: Pulling my hair -
That is great to know that the debug is a level setting and not a boolean
true/false!
Also Windy works now! Yay!
måndag 2 augusti 2021 kl. 23:01:19 UTC+2 skrev gjr80:
> If you have discrepancies between data being displayed by WeeWX and data
> being uploaded externally by WeeWX using the RESTfu
age ----
Subject: [weewx-user] Re: Pulling my hair - one weird issue after the
other [3]
Date: Mon, 2 Aug 2021 16:05:30 +0200
From: Rainer Lang
To: Konrad Skeri Ekblad
Did you enter a path in the WSView app ?
There must be at least a "/" - even though weewx doesn't
If you have discrepancies between data being displayed by WeeWX and data
being uploaded externally by WeeWX using the RESTful uploaders then the
first step is to set debug = 3 and restart WeeWX. This should result in
(amongst other things) the logging of the URL string being used by WeeWX
when
Data is being saved to the database and local website is being updated
(still using default skin). Just re-enabled Windy uploads. Waiting to see
if I still have the problem that WeeWX sends different data to Windy than
received from the weather station. Unfortunately, it is my experience that
W
So it’s working now?
Gary
On Tuesday, 3 August 2021 at 05:29:47 UTC+10 Konrad Skeri Ekblad wrote:
> And for those who happen to stumble on this thread: Path must be set to
> /path?
>
> måndag 2 augusti 2021 kl. 21:28:42 UTC+2 skrev Konrad Skeri Ekblad:
>
>> After searching in the issue tracker
And for those who happen to stumble on this thread: Path must be set to
/path?
måndag 2 augusti 2021 kl. 21:28:42 UTC+2 skrev Konrad Skeri Ekblad:
> After searching in the issue tracker on GitHub I found a similar problem
> when running in wu-client mode. If I understood correctly it is a firmw
After searching in the issue tracker on GitHub I found a similar problem
when running in wu-client mode. If I understood correctly it is a firmware
update on the weather station that requires a different path in its
settings. WeeWX logs looks correct at the moment. Will continue with
website se
Running WeeWX directly instead the output in /var/log/messages is this:
Aug 2 14:36:59 localhost systemd[1]: Starting SYSV: start and stop the
weewx weather system...
Aug 2 14:36:59 localhost journal[2697]: weewx[2697] INFO __main__:
Initializing weewx version 4.5.1
Aug 2 14:36:59 localhost j
Have a look in the other log files on your system, it should be there
somewhere. When running the interceptor driver directly the (WeeWX) logging
setup is somewhat abbreviated so it could be different to when WeeWX is run.
Gary
On Monday, 2 August 2021 at 20:47:01 UTC+10 Konrad Skeri Ekblad wro
I'm running Centos as a virtual server. Port 8000 is not in use by anything
else. (If it were I would get an error when running the interceptor driver
directly, e.g. when trying to run it while WeeWX is still running
configured to use the interceptor driver on that port.) Tried adding
--iface=e
Useful information but not relevant at this stage as the [Interceptor]
settings in weewx.conf are not used when running the interceptor driver
directly.
Gary
On Monday, 2 August 2021 at 20:42:54 UTC+10 lang@googlemail.com wrote:
> On a RPi you have to add the following line to your weewx.c
If I start WeeXW (still using simulator driver) I get its log messages in
/var/log/messages, however, running the interceptor driver directly does
not produce any output in this log file.
Konrad
måndag 2 augusti 2021 kl. 12:22:05 UTC+2 skrev gjr80:
> When you just ran the interceptor driver di
On a RPi you have to add the following line to your weewx.conf
device_type = ecowitt-client
port = 8000
iface = eth0 #if you are using the Ethernet port
#or
iface = wlan0 #if you are using the WiFi of the RPi
# only one of them 😉
you also have to make sure that no other app
When you just ran the interceptor driver directly there should have been
output to the console as well as log output in the WeeWX log, not sure what
log file it will be in as I am not a Centos user. Can you please post the
log output exactly as it appears in the log.
Gary
On Monday, 2 August 2
I did a complete reinstallation of the server with Centos 8. Fresh install
of WeeWX from repository using yum as described on web page. Installed
interceptor driver according to set up instructions.
Running PYTHONPATH=/usr/share/weewx python3 user/interceptor.py --debug
--port=8000 --device=ecow
You have changed many things in your setup and even though you appear to
have reverted to your original working configuration I would be starting
from scratch as per the interceptor drive readme.I would be running the
driver directly and then making sure you use the —debug command line
option.
19 matches
Mail list logo
