Many thanks, Vince. Much appreciated.
David.
On Wed, 27 Dec 2023 at 17:08, vince wrote:
> "except KeyError, e:" indicates that you are using python3 to run code
> that is only valid for python2.
> see https://github.com/weewx/weewx/wiki/faq-python-error
>
> Upgrade your MQTT extension to a cur
"except KeyError, e:" indicates that you are using python3 to run code
that is only valid for python2.
see https://github.com/weewx/weewx/wiki/faq-python-error
Upgrade your MQTT extension to a current version.
--
You received this message because you are subscribed to the Google Groups
"wee
UPDATE:
1. The bad news:
I tried to solve this by upgrading my OS on my Raspberry Pi from Raspbian
stretch to Raspbian buster in the hope that this might reset everyting and
solve the IP-errors, and also made python 3 the preferred python version,
as I read that this is preferred for weewx
* David Hindley [Mon, Dec 18 2023 08:09 +]:
When I type
ps -aux|grep weewx
I get
root 535 5.6 6.1 117524 58128 ?Sl 10:16 2:42 python2
/usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid
/etc/weewx/weewx.conf
pi2130 0.0 0.0 4368 564 pts/0S+
Hi David,
As for stopping weewx, kill 535 will work, but systemd will likely
restart it very soon. I ran into an similar issue
the other day with systemd. In this case it was for NUT (ups monitoring
stuff). The systemctl stop
didn't stop the daemon (same message you got). I ended up disa
Thanks for your reply Vince. Completely understand re network. I am using
Ethernet rather than WiFi for both my Rpi which hosts weewx and my davis
weather station.
Does anyone have any input on my question about stopping weewx please?
Repeated here:
In the meantime, I am having trouble stopping
Sorry - we can't fix your network. Lots of legacy embedded type 2.4GHz
wifi things have issues staying on the network and stable. I'd suggest
you try to see if your wifi is being interfered with from a neighbor
perhaps. Maybe you can switch which channel your wifi is on.
FWIW, we have too m
Still no further forward with this problem, but by setting loop_on_it=1 as
Tom K suggested, I do at least have a working weather station website,
albeit with repeated periods where it is not "live" and where graphs etc
are always an hour or so out of date.
I have put the most recent log below,
Perfect. Thanks.
On Fri, 8 Dec 2023 at 12:12, Jacques Terrettaz wrote:
> Yes, you should !
>
> The Meteo-Pi HAT card is providing an internal serial port t which weewx
> will connect to capture the data.
>
> Le 8 déc. 2023 à 12:45, David Hindley a écrit :
>
> Many thanks. Can I have weewx runn
Tom - that is correct. I don’t seem to be able to browse to the device. I
type its IP address into a browser on my Windows PC on the same network and
nothing happens. I can access the console via the weatherlink software,
but don’t see anywhere where I can disable weatherlink uploads.
David.
On
Just to clarify, you have a Davis 6555 WeatherlinkIP, right?
Before buying new equipment, I'd focus on Jacque's suggestion to disable
any transmissions to weatherlink.com from the device. You should be able to
browse to the device and get an option to turn the transmissions off.
On Fri, Dec 8, 2
Yes, you should !
The Meteo-Pi HAT card is providing an internal serial port t which weewx will
connect to capture the data.
> Le 8 déc. 2023 à 12:45, David Hindley a écrit :
>
> Many thanks. Can I have weewx running on the same RPi that the Meteo-Pi is
> connected to?
>
> David.
>
> On Fr
Many thanks. Can I have weewx running on the same RPi that the Meteo-Pi is
connected to?
David.
On Fri, 8 Dec 2023 at 11:12, Jacques Terrettaz wrote:
> Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"
> instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html
>
Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"
instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html
The datalogger card is plugged to the console and the HAT card is plugged to
the 40-pin header of the RPI and both are linked with a RJ11 cable : no more
n
Thanks. I did that and I just get “This site can’t be reached”. My
datalogger is connected via Ethernet, and I think is no longer made by
davis.
On Thu, 7 Dec 2023 at 14:29, jterr...@gmail.com
wrote:
> According to your weewx logs, the ip address of the datalogger is
> 192.168.0.25.
>
> So shut
According to your weewx logs, the ip address of the datalogger is
192.168.0.25.
So shut down weewx and open this URL http://192.168.0.25 using your web
browser
Le jeudi 7 décembre 2023 à 13:25:20 UTC+1, hind...@gmail.com a écrit :
> Many thanks for these suggestions. Regarding 1. how do I co
Many thanks for these suggestions. Regarding 1. how do I connect to the
datalogger in order to uncheck the "Upload to weatherlink" option? If the
weatherlink upload is causing the conflict, I am not clear why this would
suddenly start being an issue, but certainly worth trying.
On 2, no, I don'
David,
I have 2 suggestions about your network problems with your IP datalogger :
1. By default, the IP datalogger will periodically send sensor real-time
data and datalogger archive data to weatherlink.com servers. Weewx needs
exclusive access to the IP datalogger. You may try to disa
Thanks. I might end up having to try one of these options.
On Tuesday 5 December 2023 at 15:19:35 UTC gary@gmail.com wrote:
> I went with a WiFiLogger2 which has performed without a hitch for a couple
> of years now.
> The maker also has an Ethernet unit if you don't want the added heat fro
I went with a WiFiLogger2 which has performed without a hitch for a couple
of years now.
The maker also has an Ethernet unit if you don't want the added heat from a
radio in your console.
https://wifilogger.net/
https://wifilogger.net/ethernet.html
On Tuesday, December 5, 2023 at 6:54:14 AM UT
I have recently moved a BT Wholehome Wifi disc a little closer to the
Console (10cm now; was 100cm) , so I guess that *might* be "interfering"
in some way - I will try moving it further away again to see if that
solves the problem. I have already re-seated the WLIP logger a few times.
Incid
Hello, I think I had the same wakeup problem with the weatherlink, found a
way out using this driver:
https://github.com/chaunceygardiner/weewx-vantagenext
In my case weewx restarted repeatedly after getting loop packets failed,
unfortunately I did not document the error.
Hope it helps,
Tomás
That's certainly possible. I'd say ask Davis, but this logger has been so
long out of production that I doubt David would get any satisfaction out of
them.
I'm also suspicious when electronic devices "just break." That's very rare.
But, it does happen.
One thing you could try: reseating the logge
the vantage IP device seems to accept a connection, work for a while, then stop
responding, then connection is reset → sounds like on device side it seizes up
and the ip protocol times out; establishing new connection just repeats the
cycle. the device apparently has been working for years and i
I am getting some strange errors with my weewx set up. My log is below. I
have tried rebooting the RPi that weewx runs on, and also disconnecting the
power from the Davis Weather station console. Anyone got any idea what is
going on please?
DEBUG weewx.engine: Finished loading service weewx
25 matches
Mail list logo
