Re: [weewx-user] Pipe errors etc

[David Hindley]

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 current version.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/2beac3b1-a0b4-4735-8943-5eb3f4a0e5d7n%40googlegroups.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAHtYHVKG2q9qq%2BZYptkA2SKUp3skZaY9ij7HNUvihQ_UbcofSg%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[vince]

"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 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2beac3b1-a0b4-4735-8943-5eb3f4a0e5d7n%40googlegroups.com.

Re: [weewx-user] Pipe errors etc

[hind...@gmail.com]

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 4.10 (which is the version I am 
using).  However, weewx failed even quicker than before, with errors that 
appear unrelated to the ip-errors. Here is an extract from the syslog. Any 
ideas as to what is causing this?  I possibly did something dumb when 
upgrading the OS.

*

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
self.loadServices(config_dict)

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 161, in loadServices

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
obj = weeutil.weeutil.get_object(svc)(self, config_dict)

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1335, in get_object

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
mod = __import__(module)

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: File 
"/usr/share/weewx/user/mqtt.py", line 196

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
except KeyError, e:

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: 
 ^

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
SyntaxError: invalid syntax

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
Exiting.

Dec 21 15:16:12 raspberrypi kernel: [ 1174.418150] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:fb:72:be:d8:62:83:0f:08:00:46:00:00:20:e4:51:00:00 
SRC=192.168.0.218 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=58449 
PROTO=2

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
self.loadServices(config_dict)

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 161, in loadServices

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
obj = weeutil.weeutil.get_object(svc)(self, config_dict)

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1335, in get_object

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
mod = __import__(module)

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: File 
"/usr/share/weewx/user/mqtt.py", line 196

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
except KeyError, e:

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__: 
 ^

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
SyntaxError: invalid syntax

Dec 21 15:16:02 raspberrypi weewx[1307] CRITICAL __main__:   
Exiting.
**

So having failed at that, I went back to my old set up (yes, I took a 
back-up of the SD cared before upgrading the OS) and the IP-errors were, as 
expected, the same as before. So, I decided to give up on the weaterlink IP 
device, and ordered a Meteo-Pi HAT to provide a direct link between my 
Vantage Pro2 console and my Raspberry Pi running weewx.

2. The good news:

We had a power cut in our area in the UK for 6 hours last night. Power was 
restored overnight.  Very annoying, but I awoke this morning to a weewx 
system with no errors (ie still using the weatherlink IP logger).  So 
presumably, the reboot of my network router sorted out the IP errors. 
Strange, as I think I tried rebooting the router earlier in the evolution 
of these errors.

Sods law, but the Meteo-Pi arrived on the same morning (today) that the 
weewx system started working without errors. A future back-up option 
perhaps - or I may return it to the supplier.

David.


On Tuesday 19 December 2023 at 04:59:57 UTC Dominic Reich wrote:

> * 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
> >pi 2130 0.0 0.0 4368 564 pts/0 S+ 11:04 0:00 grep
> >--color=auto weewx
> >
> >And, then typing
> >
> >sudo /etc/init.d/weewx stop
> >
> >produces
> >
> > Stopping weewx (via systemctl): weewx.service.
> >
> >but then repeating the grep command, still shows the 535 process still
> >running?
> >
> >How do I stop weewx - do I have to use kill 535 perhaps?
>
> That is an option, but I'd first confirm that weewx is not getting
> stopped (that can take some seconds to happen though).
>
> If you confirm weewx unstopped after 10 seconds you could kill the
> process number with `sudo kill 535` (sending 

Re: [weewx-user] Pipe errors etc

[Dominic Reich]

* 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+   11:04   0:00 grep
--color=auto weewx

And, then typing

sudo /etc/init.d/weewx stop

produces

Stopping weewx (via systemctl): weewx.service.

but then repeating the grep command, still shows the 535 process still
running?

How do I stop weewx - do I have to use kill 535 perhaps?


That is an option, but I'd first confirm that weewx is not getting
stopped (that can take some seconds to happen though).

If you confirm weewx unstopped after 10 seconds you could kill the
process number with `sudo kill 535` (sending TERM signal to the process)
and if that does not work either you can KILL the process with
`sudo kill -9 535` which will force the process to kill.

You would normally kill a process with TERM, which tells the process to
save and finish, KILL will quit the process regardless of unfinished
operations of that process.

This is usually described in the `signal(3)` manpage, but could differ on
your operating system.

You could also use the pid file of weewx, which could look something
like that to force kill the process:
`sudo kill -9 $(cat /var/run/weewx.pid)`

HTH

- dominic



Thanks

David.

On Sat, 16 Dec 2023 at 19:39, vince  wrote:


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 many neighbors here with misconfigured wifi to even
count, depending on who moves in/out and who visits them occasionally.
What I eventually needed to do was (a) move everything in the house that
could do it over to 5GHz wifi, and (b) buy a Unifi AcLite AP and basically
try to out-radiate the neighbors.  Problem went away at that point.


--
You received this message because you are subscribed to a topic in the
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%40googlegroups.com

.



--
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAHtYHVLtTSA9rq-fKN%2BPaDMJazz41B1OdBVfxHxKJa%3DZ%2BRim4A%40mail.gmail.com.


--
The weak are always anxious for justice and equality.
The strong pay no heed to either.
- Aristotle

--
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ZDJjZTgzNjcwNTI4MDFlNmZlYTU4YWMyMzhmODQ4Zm%40odin.oe7drt.com.

Re: [weewx-user] Pipe errors etc

[cric...@pobox.com]

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 disabling the 
service unit and killed the processes by hand.
For weewx, I have a perl script that runs from cron that starts weewx if 
it's down.  Works great, except that I have to
remember to stop weewx by hand in care of a reboot or shutdown.  Some 
people like systemd.  I'm not one of them.

Chris


On Monday, December 18, 2023 at 1:10:12 AM UTC-7 David Hindley wrote:

> 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 weewx - not sure if this is 
> related to my ongoing pipe errors or not.  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+   11:04   0:00 grep 
> --color=auto weewx
>
> And, then typing 
>
> sudo /etc/init.d/weewx stop
>
> produces
>
>  Stopping weewx (via systemctl): weewx.service.
>
> but then repeating the grep command, still shows the 535 process still 
> running?
>
> How do I stop weewx - do I have to use kill 535 perhaps?
>
> Thanks
>
> David. 
> On Sat, 16 Dec 2023 at 19:39, vince  wrote:
>
>> 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 many neighbors here with misconfigured wifi to even 
>> count, depending on who moves in/out and who visits them occasionally.  
>> What I eventually needed to do was (a) move everything in the house that 
>> could do it over to 5GHz wifi, and (b) buy a Unifi AcLite AP and basically 
>> try to out-radiate the neighbors.  Problem went away at that point.
>>
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e9f3e79b-d362-4c4d-8d37-f3e2832d1f55n%40googlegroups.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

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 weewx - not sure if this is
related to my ongoing pipe errors or not.  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+   11:04   0:00 grep
--color=auto weewx

And, then typing

sudo /etc/init.d/weewx stop

produces

 Stopping weewx (via systemctl): weewx.service.

but then repeating the grep command, still shows the 535 process still
running?

How do I stop weewx - do I have to use kill 535 perhaps?

Thanks

David.

On Sat, 16 Dec 2023 at 19:39, vince  wrote:

> 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 many neighbors here with misconfigured wifi to even
> count, depending on who moves in/out and who visits them occasionally.
> What I eventually needed to do was (a) move everything in the house that
> could do it over to 5GHz wifi, and (b) buy a Unifi AcLite AP and basically
> try to out-radiate the neighbors.  Problem went away at that point.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%40googlegroups.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAHtYHVLtTSA9rq-fKN%2BPaDMJazz41B1OdBVfxHxKJa%3DZ%2BRim4A%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[vince]

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 many neighbors here with misconfigured wifi to even 
count, depending on who moves in/out and who visits them occasionally. 
 What I eventually needed to do was (a) move everything in the house that 
could do it over to 5GHz wifi, and (b) buy a Unifi AcLite AP and basically 
try to out-radiate the neighbors.  Problem went away at that point.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%40googlegroups.com.

Re: [weewx-user] Pipe errors etc

[hind...@gmail.com]

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, in case anyone has any more 
brainwaves that might solve this.

In the meantime, I am having trouble stopping weewx - not sure if this is 
related to my ongoing pipe errors or not.  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+   11:04   0:00 grep 
--color=auto weewx

And, then typing 

sudo /etc/init.d/weewx stop

produces

 Stopping weewx (via systemctl): weewx.service.

but then repeating the grep command, still shows the 535 process still 
running?

How do I stop weewx - do I have to use kill 535 perhaps?

Thanks

David.


Log of weewx from syslog

Dec 16 10:57:10 raspberrypi weewx[535] INFO __main__: Starting up weewx 
version 4.10.2
Dec 16 10:57:10 raspberrypi weewx[535] DEBUG weewx.manager: Daily summary 
version is 4.0
Dec 16 10:57:10 raspberrypi weewx[535] DEBUG weewx.manager: Daily summary 
version is 4.0
Dec 16 10:57:10 raspberrypi weewx[535] DEBUG weewx.manager: Daily summary 
version is 4.0
Dec 16 10:57:10 raspberrypi weewx[535] DEBUG weewx.manager: Daily summary 
version is 4.0
Dec 16 10:57:12 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Dec 16 10:57:13 raspberrypi weewx[535] INFO weewx.engine: Clock error is 
1.42 seconds (positive is fast)
Dec 16 10:57:13 raspberrypi weewx[535] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Dec 16 10:57:13 raspberrypi weewx[535] INFO weewx.manager: Starting 
backfill of daily summaries
Dec 16 10:57:13 raspberrypi weewx[535] INFO weewx.manager: Daily summaries 
up to date
Dec 16 10:57:13 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Getting 
archive packets since 2023-12-16 10:55:00 GMT (1702724100)
Dec 16 10:57:16 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Dec 16 10:57:18 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Retrieving 0 page(s); starting index= 0
Dec 16 10:57:18 raspberrypi weewx[535] INFO weewx.engine: Starting main 
packet loop.
Dec 16 10:57:20 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Dec 16 10:57:21 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Requesting 200 LOOP packets.
Dec 16 10:57:24 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Dec 16 10:57:25 raspberrypi weewx[535] ERROR weewx.drivers.vantage: 
send_data: no  received from Vantage console
Dec 16 10:57:25 raspberrypi weewx[535] ERROR weewx.drivers.vantage: LOOP 
batch try #1; error: No  received from Vantage console
Dec 16 10:57:32 raspberrypi weewx[535] ERROR weewx.drivers.vantage: ip-read 
error: timed out
Dec 16 10:57:32 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Wake up 
try 1 failed. Exception: timed out
Dec 16 10:57:32 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Retry 
#1 unable to wake up console... sleeping
Dec 16 10:57:41 raspberrypi weewx[535] ERROR weewx.drivers.vantage: ip-read 
error: timed out
Dec 16 10:57:41 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Wake up 
try 2 failed. Exception: timed out
Dec 16 10:57:41 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Retry 
#2 unable to wake up console... sleeping
Dec 16 10:57:50 raspberrypi weewx[535] ERROR weewx.drivers.vantage: ip-read 
error: timed out
Dec 16 10:57:50 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Wake up 
try 3 failed. Exception: timed out
Dec 16 10:57:50 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Retry 
#3 unable to wake up console... sleeping
Dec 16 10:57:58 raspberrypi weewx[535] ERROR weewx.drivers.vantage: ip-read 
error: timed out
Dec 16 10:57:58 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Wake up 
try 4 failed. Exception: timed out
Dec 16 10:57:58 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Retry 
#4 unable to wake up console... sleeping
Dec 16 10:57:59 raspberrypi weewx[535] ERROR weewx.drivers.vantage: Unable 
to wake up Vantage console
Dec 16 10:57:59 raspberrypi weewx[535] ERROR weewx.drivers.vantage: LOOP 
batch try #2; error: Unable to wake up Vantage console
Dec 16 10:58:01 raspberrypi weewx[535] ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe
Dec 16 10:58:01 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Wake up 
try 1 failed. Exception: [Errno 32] Broken pipe
Dec 16 10:58:01 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Retry 
#1 unable to wake up console... sleeping
Dec 16 10:58:02 raspberrypi weewx[535] ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe
Dec 16 10:58:02 

Re: [weewx-user] Pipe errors etc

[David Hindley]

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 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
>>
>> 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 network problems !
>>
>> I am using a Meteo-Pi since several years and I never had a single
>> problem of communication between the console and weewx
>>
>>
>>
>> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit :
>>
>>  the only thing I can think of doing next is to replace the davis
>> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
>> I'd rather not do that unless I really have to.  I have also seen some
>> users having pipe errors with this wiflogger, so am a bit nervous about
>> buying it.
>>
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com
>> 
>> .
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com
> 
> .
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/53C447C0-D2EF-44B1-9E9A-09A998A7D070%40gmail.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAHtYHVLKDPd6AKEiJpu_65pb4PJ%2BajQr2M24ZxkMt0Kj-Hv%2Bmg%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

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 Fri, 8 Dec 2023 at 13:10, Tom Keffer  wrote:

> 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, 2023 at 3:45 AM David Hindley  wrote:
>
>> 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
>>>
>>> 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 network problems !
>>>
>>> I am using a Meteo-Pi since several years and I never had a single
>>> problem of communication between the console and weewx
>>>
>>>
>>>
>>> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit
>>> :
>>>
>>>  the only thing I can think of doing next is to replace the davis
>>> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
>>> I'd rather not do that unless I really have to.  I have also seen some
>>> users having pipe errors with this wiflogger, so am a bit nervous about
>>> buying it.
>>>
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com
>>> 
>>> .
>>
>>
>>> --
>> 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 weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBUrpzUNiYs%3D7i_8uNCeV5NYZACvys95MJdjFxH_Hmniw%40mail.gmail.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAHtYHV%2BXD5Ekp-nqUL95v9u3rJs_qoOrY15L4f78GZ6PbY6Viw%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[Tom Keffer]

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, 2023 at 3:45 AM David Hindley  wrote:

> 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
>>
>> 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 network problems !
>>
>> I am using a Meteo-Pi since several years and I never had a single
>> problem of communication between the console and weewx
>>
>>
>>
>> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit :
>>
>>  the only thing I can think of doing next is to replace the davis
>> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
>> I'd rather not do that unless I really have to.  I have also seen some
>> users having pipe errors with this wiflogger, so am a bit nervous about
>> buying it.
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com
>> 
>> .
>>
> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBUrpzUNiYs%3D7i_8uNCeV5NYZACvys95MJdjFxH_Hmniw%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[Jacques Terrettaz]

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 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
>> 
>> 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 
>> network problems !
>> 
>> I am using a Meteo-Pi since several years and I never had a single problem 
>> of communication between the console and weewx
>> 
>> 
>> 
>>> Le 8 déc. 2023 à 11:04, hind...@gmail.com  
>>> mailto:hindle...@gmail.com>> a écrit :
>>> 
>>>  the only thing I can think of doing next is to replace the davis Ethernet 
>>> datalogger with the WifiLogger2, but that is quite expensive so I'd rather 
>>> not do that unless I really have to.  I have also seen some users having 
>>> pipe errors with this wiflogger, so am a bit nervous about buying it.
>> 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com
>>  
>> .
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com
>  
> .

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/53C447C0-D2EF-44B1-9E9A-09A998A7D070%40gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

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
>
> 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 network problems !
>
> I am using a Meteo-Pi since several years and I never had a single problem
> of communication between the console and weewx
>
>
>
> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit :
>
>  the only thing I can think of doing next is to replace the davis
> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
> I'd rather not do that unless I really have to.  I have also seen some
> users having pipe errors with this wiflogger, so am a bit nervous about
> buying it.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[Jacques Terrettaz]

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 
network problems !

I am using a Meteo-Pi since several years and I never had a single problem of 
communication between the console and weewx



> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit :
> 
>  the only thing I can think of doing next is to replace the davis Ethernet 
> datalogger with the WifiLogger2, but that is quite expensive so I'd rather 
> not do that unless I really have to.  I have also seen some users having pipe 
> errors with this wiflogger, so am a bit nervous about buying it.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

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 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 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't have a static IP address for the datalogger, or any
>> other device configured with the same IP address.
>>
>> On Wednesday 6 December 2023 at 07:46:08 UTC jterr...@gmail.com wrote:
>>
>>> 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
>>>disable the upload to weatherlink servers by connecting to the datalogger
>>>using a web browser and uncheck the "Upload to weatherlink.com"
>>>option.  Concerning the exclusive access needed by weewx, are you using 
>>> any
>>>other software (Weatherlink software or any other) that connects to the 
>>> IP
>>>datalogger and that may break the weewx-datalogger pipe ?
>>>2. Is the IP logger configured with  a static IP address ? If it is
>>>the case, check that you don't have any other network device configured
>>>statically with the same IP address. Check also that the address range of
>>>the DHCP server of your router does not overlap with the static IP 
>>> address
>>>of the datalogger.
>>>
>>>
>>> Le mardi 5 décembre 2023 à 18:58:12 UTC+1, hind...@gmail.com a écrit :
>>>
 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
> from a radio in your console.
>
> https://wifilogger.net/
>
> https://wifilogger.net/ethernet.html
>
> On Tuesday, December 5, 2023 at 6:54:14 AM UTC-5 hind...@gmail.com
> wrote:
>
>> 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. Incidentally, if Davis no longer make the WLIP logger, does anyone
>> know what the the preferred method now is of getting the data from the
>> weather station to weewx etc?
>>
>> I may also try the different drive that was suggested in
>> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/7difZtkUAgAJ.
>>
>> Regarding the question in
>> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/J9W5KA7rAQAJ,
>> I haven't changed anything on my network, other than moving a few 
>> ethernet
>> cables for other devices around, due to an unstable Sky TV connection.
>>
>> Thanks to everyone that has commented on this to help me find a
>> solution.  Much appreciated.
>>
>> David.
>>
>> On Tuesday 5 December 2023 at 00:25:06 UTC Tom Keffer wrote:
>>
>>> 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 logger.
>>>
>>> Oh, and is there any new source of RF nearby? A new router?
>>> Satellite dish? 5 kW pirate radio?
>>>
>>> On Mon, Dec 4, 2023 at 4:17 PM Graham Eddy  wrote:
>>>
 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 is now failing → sounds like device has broken
 *⊣GE⊢*

 On 5 Dec 2023, at 9:23 am, vince  wrote:

 Just a thought, but when I see "weewx.drivers.vantage: ip-read
 error: timed out" that makes me think your 

Re: [weewx-user] Pipe errors etc

[jterr...@gmail.com]

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 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't have a static IP address for the datalogger, or any 
> other device configured with the same IP address.
>
> On Wednesday 6 December 2023 at 07:46:08 UTC jterr...@gmail.com wrote:
>
>> 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 
>>disable the upload to weatherlink servers by connecting to the datalogger 
>>using a web browser and uncheck the "Upload to weatherlink.com" 
>>option.  Concerning the exclusive access needed by weewx, are you using 
>> any 
>>other software (Weatherlink software or any other) that connects to the 
>> IP 
>>datalogger and that may break the weewx-datalogger pipe ?
>>2. Is the IP logger configured with  a static IP address ? If it is 
>>the case, check that you don't have any other network device configured 
>>statically with the same IP address. Check also that the address range of 
>>the DHCP server of your router does not overlap with the static IP 
>> address 
>>of the datalogger.
>>
>>
>> Le mardi 5 décembre 2023 à 18:58:12 UTC+1, hind...@gmail.com a écrit :
>>
>>> 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 
 from a radio in your console.

 https://wifilogger.net/

 https://wifilogger.net/ethernet.html

 On Tuesday, December 5, 2023 at 6:54:14 AM UTC-5 hind...@gmail.com 
 wrote:

> 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. Incidentally, if Davis no longer make the WLIP logger, does anyone 
> know what the the preferred method now is of getting the data from the 
> weather station to weewx etc?
>
> I may also try the different drive that was suggested in 
> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/7difZtkUAgAJ.
>
> Regarding the question in 
> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/J9W5KA7rAQAJ, 
> I haven't changed anything on my network, other than moving a few 
> ethernet 
> cables for other devices around, due to an unstable Sky TV connection.
>
> Thanks to everyone that has commented on this to help me find a 
> solution.  Much appreciated.
>
> David.
>
> On Tuesday 5 December 2023 at 00:25:06 UTC Tom Keffer wrote:
>
>> 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 logger. 
>>
>> Oh, and is there any new source of RF nearby? A new router? Satellite 
>> dish? 5 kW pirate radio?
>>
>> On Mon, Dec 4, 2023 at 4:17 PM Graham Eddy  wrote:
>>
>>> 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 is now failing → sounds like device has broken
>>> *⊣GE⊢*
>>>
>>> On 5 Dec 2023, at 9:23 am, vince  wrote:
>>>
>>> Just a thought, but when I see "weewx.drivers.vantage: ip-read 
>>> error: timed out" that makes me think your network is unstable.   
>>> From your posts in the thread it 'sounds' like it has been working for 
>>> years without issues.  Did you change anything on your network ? Did 
>>> you 
>>> change any firewall settings on your pi or install something like 
>>> fail2ban 

Re: [weewx-user] Pipe errors etc

[hind...@gmail.com]

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't have a static IP address for the datalogger, or any other 
device configured with the same IP address.

On Wednesday 6 December 2023 at 07:46:08 UTC jterr...@gmail.com wrote:

> 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 disable 
>the upload to weatherlink servers by connecting to the datalogger using a 
>web browser and uncheck the "Upload to weatherlink.com" option. 
> Concerning the exclusive access needed by weewx, are you using any other 
>software (Weatherlink software or any other) that connects to the IP 
>datalogger and that may break the weewx-datalogger pipe ?
>2. Is the IP logger configured with  a static IP address ? If it is 
>the case, check that you don't have any other network device configured 
>statically with the same IP address. Check also that the address range of 
>the DHCP server of your router does not overlap with the static IP address 
>of the datalogger.
>
>
> Le mardi 5 décembre 2023 à 18:58:12 UTC+1, hind...@gmail.com a écrit :
>
>> 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 
>>> from a radio in your console.
>>>
>>> https://wifilogger.net/
>>>
>>> https://wifilogger.net/ethernet.html
>>>
>>> On Tuesday, December 5, 2023 at 6:54:14 AM UTC-5 hind...@gmail.com 
>>> wrote:
>>>
 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. Incidentally, if Davis no longer make the WLIP logger, does anyone 
 know what the the preferred method now is of getting the data from the 
 weather station to weewx etc?

 I may also try the different drive that was suggested in 
 https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/7difZtkUAgAJ.

 Regarding the question in 
 https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/J9W5KA7rAQAJ, I 
 haven't changed anything on my network, other than moving a few ethernet 
 cables for other devices around, due to an unstable Sky TV connection.

 Thanks to everyone that has commented on this to help me find a 
 solution.  Much appreciated.

 David.

 On Tuesday 5 December 2023 at 00:25:06 UTC Tom Keffer wrote:

> 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 logger. 
>
> Oh, and is there any new source of RF nearby? A new router? Satellite 
> dish? 5 kW pirate radio?
>
> On Mon, Dec 4, 2023 at 4:17 PM Graham Eddy  wrote:
>
>> 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 is now failing → sounds like device has broken
>> *⊣GE⊢*
>>
>> On 5 Dec 2023, at 9:23 am, vince  wrote:
>>
>> Just a thought, but when I see "weewx.drivers.vantage: ip-read 
>> error: timed out" that makes me think your network is unstable.   
>> From your posts in the thread it 'sounds' like it has been working for 
>> years without issues.  Did you change anything on your network ? Did you 
>> change any firewall settings on your pi or install something like 
>> fail2ban 
>> or pihole recently ?
>>
>>
>> -- 
>> 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 weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> 

Re: [weewx-user] Pipe errors etc

[jterr...@gmail.com]

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 disable the upload to 
   weatherlink servers by connecting to the datalogger using a web browser and 
   uncheck the "Upload to weatherlink.com" option.  Concerning the exclusive 
   access needed by weewx, are you using any other software (Weatherlink 
   software or any other) that connects to the IP datalogger and that may 
   break the weewx-datalogger pipe ?
   2. Is the IP logger configured with  a static IP address ? If it is the 
   case, check that you don't have any other network device configured 
   statically with the same IP address. Check also that the address range of 
   the DHCP server of your router does not overlap with the static IP address 
   of the datalogger.


Le mardi 5 décembre 2023 à 18:58:12 UTC+1, hind...@gmail.com a écrit :

> 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 from 
>> a radio in your console.
>>
>> https://wifilogger.net/
>>
>> https://wifilogger.net/ethernet.html
>>
>> On Tuesday, December 5, 2023 at 6:54:14 AM UTC-5 hind...@gmail.com wrote:
>>
>>> 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. Incidentally, if Davis no longer make the WLIP logger, does anyone 
>>> know what the the preferred method now is of getting the data from the 
>>> weather station to weewx etc?
>>>
>>> I may also try the different drive that was suggested in 
>>> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/7difZtkUAgAJ.
>>>
>>> Regarding the question in 
>>> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/J9W5KA7rAQAJ, I 
>>> haven't changed anything on my network, other than moving a few ethernet 
>>> cables for other devices around, due to an unstable Sky TV connection.
>>>
>>> Thanks to everyone that has commented on this to help me find a 
>>> solution.  Much appreciated.
>>>
>>> David.
>>>
>>> On Tuesday 5 December 2023 at 00:25:06 UTC Tom Keffer wrote:
>>>
 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 logger. 

 Oh, and is there any new source of RF nearby? A new router? Satellite 
 dish? 5 kW pirate radio?

 On Mon, Dec 4, 2023 at 4:17 PM Graham Eddy  wrote:

> 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 is now failing → sounds like device has broken
> *⊣GE⊢*
>
> On 5 Dec 2023, at 9:23 am, vince  wrote:
>
> Just a thought, but when I see "weewx.drivers.vantage: ip-read error: 
> timed out" that makes me think your network is unstable.   From your 
> posts in the thread it 'sounds' like it has been working for years 
> without 
> issues.  Did you change anything on your network ? Did you change any 
> firewall settings on your pi or install something like fail2ban or pihole 
> recently ?
>
>
> -- 
> 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 weewx-user+...@googlegroups.com.
>
 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/6B5C1B94-55F5-484D-8E8E-3142F471AE4C%40geddy.au
>  
> 
> .
>


-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d7ac813d-fc19-4ab7-8f73-f7f7a47ee46an%40googlegroups.com.

Re: [weewx-user] Pipe errors etc

[hind...@gmail.com]

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 from 
> a radio in your console.
>
> https://wifilogger.net/
>
> https://wifilogger.net/ethernet.html
>
> On Tuesday, December 5, 2023 at 6:54:14 AM UTC-5 hind...@gmail.com wrote:
>
>> 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. Incidentally, if Davis no longer make the WLIP logger, does anyone 
>> know what the the preferred method now is of getting the data from the 
>> weather station to weewx etc?
>>
>> I may also try the different drive that was suggested in 
>> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/7difZtkUAgAJ.
>>
>> Regarding the question in 
>> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/J9W5KA7rAQAJ, I 
>> haven't changed anything on my network, other than moving a few ethernet 
>> cables for other devices around, due to an unstable Sky TV connection.
>>
>> Thanks to everyone that has commented on this to help me find a 
>> solution.  Much appreciated.
>>
>> David.
>>
>> On Tuesday 5 December 2023 at 00:25:06 UTC Tom Keffer wrote:
>>
>>> 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 logger. 
>>>
>>> Oh, and is there any new source of RF nearby? A new router? Satellite 
>>> dish? 5 kW pirate radio?
>>>
>>> On Mon, Dec 4, 2023 at 4:17 PM Graham Eddy  wrote:
>>>
 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 is now failing → sounds like device has broken
 *⊣GE⊢*

 On 5 Dec 2023, at 9:23 am, vince  wrote:

 Just a thought, but when I see "weewx.drivers.vantage: ip-read error: 
 timed out" that makes me think your network is unstable.   From your 
 posts in the thread it 'sounds' like it has been working for years without 
 issues.  Did you change anything on your network ? Did you change any 
 firewall settings on your pi or install something like fail2ban or pihole 
 recently ?


 -- 
 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 weewx-user+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/6B5C1B94-55F5-484D-8E8E-3142F471AE4C%40geddy.au
  
 
 .

>>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e65e8a9c-47ec-45a2-8711-13ac39cd814fn%40googlegroups.com.

Re: [weewx-user] Pipe errors etc

[gary....@gmail.com]

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 UTC-5 hind...@gmail.com wrote:

> 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. Incidentally, if Davis no longer make the WLIP logger, does anyone 
> know what the the preferred method now is of getting the data from the 
> weather station to weewx etc?
>
> I may also try the different drive that was suggested in 
> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/7difZtkUAgAJ.
>
> Regarding the question in 
> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/J9W5KA7rAQAJ, I 
> haven't changed anything on my network, other than moving a few ethernet 
> cables for other devices around, due to an unstable Sky TV connection.
>
> Thanks to everyone that has commented on this to help me find a solution.  
> Much appreciated.
>
> David.
>
> On Tuesday 5 December 2023 at 00:25:06 UTC Tom Keffer wrote:
>
>> 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 logger. 
>>
>> Oh, and is there any new source of RF nearby? A new router? Satellite 
>> dish? 5 kW pirate radio?
>>
>> On Mon, Dec 4, 2023 at 4:17 PM Graham Eddy  wrote:
>>
>>> 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 is now failing → sounds like device has broken
>>> *⊣GE⊢*
>>>
>>> On 5 Dec 2023, at 9:23 am, vince  wrote:
>>>
>>> Just a thought, but when I see "weewx.drivers.vantage: ip-read error: 
>>> timed out" that makes me think your network is unstable.   From your 
>>> posts in the thread it 'sounds' like it has been working for years without 
>>> issues.  Did you change anything on your network ? Did you change any 
>>> firewall settings on your pi or install something like fail2ban or pihole 
>>> recently ?
>>>
>>>
>>> -- 
>>> 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 weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/6B5C1B94-55F5-484D-8E8E-3142F471AE4C%40geddy.au
>>>  
>>> 
>>> .
>>>
>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/021e0ca9-fd6a-4178-b932-fc30c9cfadfen%40googlegroups.com.

Re: [weewx-user] Pipe errors etc

[hind...@gmail.com]

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. 
Incidentally, if Davis no longer make the WLIP logger, does anyone know 
what the the preferred method now is of getting the data from the weather 
station to weewx etc?

I may also try the different drive that was suggested 
in https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/7difZtkUAgAJ.

Regarding the question 
in https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/J9W5KA7rAQAJ, I 
haven't changed anything on my network, other than moving a few ethernet 
cables for other devices around, due to an unstable Sky TV connection.

Thanks to everyone that has commented on this to help me find a solution.  
Much appreciated.

David.

On Tuesday 5 December 2023 at 00:25:06 UTC Tom Keffer wrote:

> 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 logger. 
>
> Oh, and is there any new source of RF nearby? A new router? Satellite 
> dish? 5 kW pirate radio?
>
> On Mon, Dec 4, 2023 at 4:17 PM Graham Eddy  wrote:
>
>> 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 is now failing → sounds like device has broken
>> *⊣GE⊢*
>>
>> On 5 Dec 2023, at 9:23 am, vince  wrote:
>>
>> Just a thought, but when I see "weewx.drivers.vantage: ip-read error: 
>> timed out" that makes me think your network is unstable.   From your 
>> posts in the thread it 'sounds' like it has been working for years without 
>> issues.  Did you change anything on your network ? Did you change any 
>> firewall settings on your pi or install something like fail2ban or pihole 
>> recently ?
>>
>>
>> -- 
>> 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 weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/6B5C1B94-55F5-484D-8E8E-3142F471AE4C%40geddy.au
>>  
>> 
>> .
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f554b857-491d-46e2-8a6e-98d61a4415d7n%40googlegroups.com.

Re: [weewx-user] Pipe errors etc

[Tomás]

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.-


On Monday, 4 December 2023 at 21:25:06 UTC-3 Tom Keffer wrote:

> 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 logger. 
>
> Oh, and is there any new source of RF nearby? A new router? Satellite 
> dish? 5 kW pirate radio?
>
> On Mon, Dec 4, 2023 at 4:17 PM Graham Eddy  wrote:
>
>> 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 is now failing → sounds like device has broken
>> *⊣GE⊢*
>>
>> On 5 Dec 2023, at 9:23 am, vince  wrote:
>>
>> Just a thought, but when I see "weewx.drivers.vantage: ip-read error: 
>> timed out" that makes me think your network is unstable.   From your 
>> posts in the thread it 'sounds' like it has been working for years without 
>> issues.  Did you change anything on your network ? Did you change any 
>> firewall settings on your pi or install something like fail2ban or pihole 
>> recently ?
>>
>>
>> -- 
>> 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 weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/6B5C1B94-55F5-484D-8E8E-3142F471AE4C%40geddy.au
>>  
>> 
>> .
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b58a2be7-a1e0-4bf9-abc9-812c11024362n%40googlegroups.com.

Re: [weewx-user] Pipe errors etc

[Tom Keffer]

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 logger.

Oh, and is there any new source of RF nearby? A new router? Satellite dish?
5 kW pirate radio?

On Mon, Dec 4, 2023 at 4:17 PM Graham Eddy  wrote:

> 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 is
> now failing → sounds like device has broken
> *⊣GE⊢*
>
> On 5 Dec 2023, at 9:23 am, vince  wrote:
>
> Just a thought, but when I see "weewx.drivers.vantage: ip-read error:
> timed out" that makes me think your network is unstable.   From your
> posts in the thread it 'sounds' like it has been working for years without
> issues.  Did you change anything on your network ? Did you change any
> firewall settings on your pi or install something like fail2ban or pihole
> recently ?
>
>
> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/6B5C1B94-55F5-484D-8E8E-3142F471AE4C%40geddy.au
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zECEuYvk_fWq6hy7XhxL3%3DTiyWKFeFQGsSvP%3DJH576O%3DUw%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[Graham Eddy]

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 is now failing → 
sounds like device has broken
⊣GE⊢

> On 5 Dec 2023, at 9:23 am, vince  wrote:
> 
> Just a thought, but when I see "weewx.drivers.vantage: ip-read error: timed 
> out" that makes me think your network is unstable.   From your posts in the 
> thread it 'sounds' like it has been working for years without issues.  Did 
> you change anything on your network ? Did you change any firewall settings on 
> your pi or install something like fail2ban or pihole recently ?

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6B5C1B94-55F5-484D-8E8E-3142F471AE4C%40geddy.au.

[weewx-user] Pipe errors etc

[hind...@gmail.com]

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.engine.StdPrint

Nov 27 17:47:08 raspberrypi weewx[1529] DEBUG weewx.engine: Loading service 
weewx.engine.StdReport

Nov 27 17:47:08 raspberrypi weewx[1529] INFO weewx.engine: 'pyephem' not 
detected, extended almanac data is not available

Nov 27 17:47:08 raspberrypi weewx[1529] DEBUG weewx.engine: Finished 
loading service weewx.engine.StdReport

Nov 27 17:47:08 raspberrypi weewx[1529] INFO __main__: Starting up weewx 
version 4.10.2

Nov 27 17:47:08 raspberrypi weewx[1529] DEBUG weewx.manager: Daily summary 
version is 4.0

Nov 27 17:47:08 raspberrypi weewx[1529] DEBUG weewx.manager: Daily summary 
version is 4.0

Nov 27 17:47:09 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console

Nov 27 17:47:10 raspberrypi weewx[1529] INFO weewx.engine: Clock error is 
-2269.18 seconds (positive is fast)

Nov 27 17:47:11 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console

Nov 27 17:47:13 raspberrypi weewx[1529] INFO weewx.drivers.vantage: Clock 
set to 2023-11-27 17:47:13 GMT (1701107233)

Nov 27 17:47:13 raspberrypi weewx[1529] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'

Nov 27 17:47:13 raspberrypi weewx[1529] INFO weewx.manager: Starting 
backfill of daily summaries

Nov 27 17:47:13 raspberrypi weewx[1529] INFO weewx.manager: Daily summaries 
up to date

Nov 27 17:47:13 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
Getting archive packets since 2023-11-27 17:30:00 GMT (1701106200)

Nov 27 17:47:14 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console

Nov 27 17:47:16 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
Retrieving 1 page(s); starting index= 3

Nov 27 17:47:16 raspberrypi weewx[1529] INFO weewx.manager: Added record 
2023-11-27 17:35:00 GMT (1701106500) to database 'weewx.sdb'

Nov 27 17:47:16 raspberrypi weewx[1529] INFO weewx.manager: Added record 
2023-11-27 17:35:00 GMT (1701106500) to daily summary in 'weewx.sdb'

Nov 27 17:47:17 raspberrypi weewx[1529] INFO weewx.manager: Added record 
2023-11-27 17:40:00 GMT (1701106800) to database 'weewx.sdb'

Nov 27 17:47:17 raspberrypi weewx[1529] INFO weewx.manager: Added record 
2023-11-27 17:40:00 GMT (1701106800) to daily summary in 'weewx.sdb'

Nov 27 17:47:17 raspberrypi weewx[1529] INFO weewx.restx: PWSWeather: 
Published record 2023-11-27 17:35:00 GMT (1701106500)

Nov 27 17:47:17 raspberrypi weewx[1529] INFO weewx.restx: WOW: Published 
record 2023-11-27 17:35:00 GMT (1701106500)

Nov 27 17:47:17 raspberrypi weewx[1529] DEBUG weewx.restx: StationRegistry: 
Failed upload attempt 1: HTTP Error 429: TOO MANY REQUESTS

Nov 27 17:47:17 raspberrypi weewx[1529] INFO weewx.engine: Starting main 
packet loop.

Nov 27 17:47:18 raspberrypi weewx[1529] INFO weewx.restx: WOW: Published 
record 2023-11-27 17:40:00 GMT (1701106800)

Nov 27 17:47:18 raspberrypi weewx[1529] INFO weewx.restx: PWSWeather: 
Published record 2023-11-27 17:40:00 GMT (1701106800)

Nov 27 17:47:19 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console

Nov 27 17:47:19 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
Requesting 200 LOOP packets.

Nov 27 17:47:21 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console

Nov 27 17:47:23 raspberrypi weewx[1529] DEBUG weewx.restx: StationRegistry: 
Failed upload attempt 2: HTTP Error 429: TOO MANY REQUESTS

Nov 27 17:47:26 raspberrypi weewx[1529] ERROR weewx.drivers.vantage: 
ip-read error: timed out

Nov 27 17:47:26 raspberrypi weewx[1529] ERROR weewx.drivers.vantage: LOOP 
batch try #1; error: timed out

Nov 27 17:47:27 raspberrypi weewx[1529] ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe

Nov 27 17:47:27 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: Retry 
#1 unable to wake up console... sleeping

Nov 27 17:47:28 raspberrypi weewx[1529] ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe

Nov 27 17:47:28 raspberrypi weewx[1529] DEBUG weewx.drivers.vantage: Retry 
#2 unable to wake up console... sleeping

Nov 27 17:47:28 raspberrypi weewx[1529] DEBUG weewx.restx: StationRegistry: 
Failed upload attempt 3: HTTP Error 429: TOO MANY REQUESTS

Nov 27 17:47:28 raspberrypi weewx[1529] ERROR weewx.restx: StationRegistry: 
Failed to publish record 2023-11-27 17:35:00 GMT (1701106500): Failed 
upload after 3 tries

Nov 27 17:47:28 raspberrypi weewx[1529] DEBUG weewx.restx: StationRegistry: 
wait interval (300 < 86400) has not passed for record 2023-11-27 17:40:00 
GMT (1701106800)

Nov 27 17:47:29 raspberrypi weewx[1529] ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken