I know of no v4 vs v5 issues. I run v5 here. Tests ok for me on both venv and dpkg installations.
I guess I would suggest trying to nmap the gateway from the pi and check the port seems open. If you want to post your current weewx.info I can take a look. But it sounds like a typo or something networky to me, assuming you have no firewalls in between the pi and the gateway… On Friday, June 13, 2025 at 1:07:30 PM UTC-7 Nick wrote: > On 13/06/2025 20:58, vince wrote: > > The old PYTHONPATH needs to look in two places now - one where user stuff > > goes, one where weewx core goes. > > > > Try the following (tests ok here): > > PYTHONPATH=/etc/weewx/bin:/usr/share/weewx python3 -m user.gw1000 > > --test-driver --ip-address=192.168.1.104 > > > > > > Vince, > > Some good & some bad news, no funny errors but still no joy. > > Here is the output & a ping to show that the station is on the network > > <code> > pi@RpiPP:~ $ PYTHONPATH=/etc/weewx/bin:/usr/share/weewx python3 -m > user.gw1000 --test-driver --ip-address=192.168.1.104 > Using configuration file /etc/weewx/weewx.conf > debug level is '1' > > IP address obtained from command line options > Port number set to default port number > Battery state filtering is 'False' (using the default) > > Unable to connect to device: Failed to obtain response to command > 'CMD_READ_FIRMWARE_VERSION' after 3 attempts > > Things to check include that the correct device IP address is being > used, > the device is powered on and the device is not otherwise > disconnected from > the local network. > pi@RpiPP:~ $ ping 192.168.1.104 > PING 192.168.1.104 (192.168.1.104) 56(84) bytes of data. > 64 bytes from 192.168.1.104: icmp_seq=1 ttl=128 time=7.44 ms > 64 bytes from 192.168.1.104: icmp_seq=2 ttl=128 time=2.64 ms > 64 bytes from 192.168.1.104: icmp_seq=3 ttl=128 time=5.67 ms > ^C > --- 192.168.1.104 ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 2004ms > rtt min/avg/max/mdev = 2.641/5.247/7.435/1.979 ms > </code> > > I am sure this _did_ work with a V4.xxx install so I may just, for > giggles, nuke the V5 install & go for a V4 install that ran as root > rather than the unprivileged user. Though it looks like the firmware > version returned is either miss-coded by the station or the checksum is > wrong or ... so that may not work out any better. > > Ho Hum > > Regards > > Nick > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/2b475c27-d9ec-46d1-bf80-afadaec4d639n%40googlegroups.com.
