The other Pi has no problems communicating with the GW1000, and I can't find any relevant settings in the router. The only reference to ports are passing 80 & 443 from the outside to the Pi where WeeWx is working.
No problem using rcp to copy files between the two RPis. They all have ssh turned on, and I access the command line via putty - none of them have a GUI. There is another Pi on the network running Pi-Hole and setting that up last week didn't stop the other WeeWx Pi from accessing the GW1000. Again, I've looked through the setup and can't see anything that might be relevant. (there are 4 RPis - Pi-Hole, WeeWx live & test, & a WWW server for the WeeWx data. The generated files are FTP's to it by WeeWx). What is the best way to check what ports the problem Pi has open and/or if that's the problem? If the default RPi OS setup has them all open by default then that's what I have. On Friday, 26 November 2021 at 16:48:19 UTC [email protected] wrote: > does your router allow the server (RPi) to connect to other devices, > especially to the GW1000, resp. the GW1000 to connect to the RPi ? > Routers often restrict the access by default. > > Ports 45000, 46000 TCP/UDP need to be open for weewx to communicate with > the GW1000 and vice versa. > On 26.11.2021 17:11, Auchtermuchty Weather wrote: > > I'm moving my WeeWx back to the right Pi, but with up-to-date Pi OS, WeeWx > and GW1000 driver. Versions are: > > WeeWX 4.5.1 > GW1000 0.4.1 > Raspbian 5.10.63-v7+ > > I have another Pi working quite happily picking up data via the GW1000 > driver, so I don't think there's a problem there. > > I've following the instructions at GIT to install it using wee_extension but > when I try to test it I get: > > $ PYTHONPATH=/home/weewx/bin python -m user.gw1000 --test-driver > Using configuration file /home/weewx/weewx.conf > > Unable to connect to device: Failed to detect device IP address and/or > port after 3 attempts > > So I've run this: > $ PYTHONPATH=/home/weewx/bin python -m user.gw1000 --sensors --debug=3 > > And this is in /var/log/debug: > Nov 26 15:57:22 LiveWeeWx weewx[6200] DEBUG __main__: Sending broadcast > packet 'FF FF 12 03 15' to '255.255.255.255:46000' > Nov 26 15:57:22 LiveWeeWx weewx[6200] DEBUG __main__: Received broadcast > response 'FF FF 12 00 21 48 3F DA 54 59 59 C0 A8 01 A2 AF C8 10 57 48 32 36 > 35 30 41 2D 57 49 46 49 35 39 35 39 F0' > Nov 26 15:57:22 LiveWeeWx weewx[6200] DEBUG __main__: Invalid response to > command 'CMD_BROADCAST': Invalid checksum in API response. Expected '17' > (0x11), received '240' (0xF0). > Nov 26 15:57:27 LiveWeeWx weewx[6200] DEBUG __main__: Failed attempt 1 to > detect device IP address and/or port > Nov 26 15:57:37 LiveWeeWx weewx[6200] DEBUG __main__: Sending broadcast > packet 'FF FF 12 03 15' to '255.255.255.255:46000' > Nov 26 15:57:37 LiveWeeWx weewx[6200] DEBUG __main__: Received broadcast > response 'FF FF 12 00 21 48 3F DA 54 59 59 C0 A8 01 A2 AF C8 10 57 48 32 36 > 35 30 41 2D 57 49 46 49 35 39 35 39 F0' > Nov 26 15:57:37 LiveWeeWx weewx[6200] DEBUG __main__: Invalid response to > command 'CMD_BROADCAST': Invalid checksum in API response. Expected '17' > (0x11), received '240' (0xF0). > Nov 26 15:57:42 LiveWeeWx weewx[6200] DEBUG __main__: Failed attempt 2 to > detect device IP address and/or port > Nov 26 15:57:52 LiveWeeWx weewx[6200] DEBUG __main__: Sending broadcast > packet 'FF FF 12 03 15' to '255.255.255.255:46000' > Nov 26 15:57:52 LiveWeeWx weewx[6200] DEBUG __main__: Received broadcast > response 'FF FF 12 00 21 48 3F DA 54 59 59 C0 A8 01 A2 AF C8 10 57 48 32 36 > 35 30 41 2D 57 49 46 49 35 39 35 39 F0' > Nov 26 15:57:52 LiveWeeWx weewx[6200] DEBUG __main__: Invalid response to > command 'CMD_BROADCAST': Invalid checksum in API response. Expected '17' > (0x11), received '240' (0xF0). > Nov 26 15:57:57 LiveWeeWx weewx[6200] DEBUG __main__: Failed attempt 3 to > detect device IP address and/or port > > No idea what the problem is. I have a feeling I might have had this > problem previously and documented it, but I've managed to lose that > document - if it ever existed. :( > > -- > 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 on the web visit > https://groups.google.com/d/msgid/weewx-user/f3a02509-adf7-4fb8-a23a-5eeec262ef45n%40googlegroups.com > > <https://groups.google.com/d/msgid/weewx-user/f3a02509-adf7-4fb8-a23a-5eeec262ef45n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- 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 on the web visit https://groups.google.com/d/msgid/weewx-user/2d044300-0fe7-4417-825a-da8a80713ecdn%40googlegroups.com.
