Yup, it's listening on that IP and that port. When first running the weewx service on a new VM, it will communicate and pull down the last 2 or so months worth of data just fine. Sits there dumping this data for quite a few minutes. Then it goes thru whatever polling timeline to gather more data. See below:
Mar 11 09:35:23 weather systemd[1395]: Reached target Paths. Mar 11 09:35:23 weather systemd[1395]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 11 09:35:23 weather systemd[1395]: Listening on GnuPG network certificate management daemon. Mar 11 09:35:23 weather systemd[1395]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 11 09:35:23 weather systemd[1395]: Reached target Sockets. Mar 11 09:35:23 weather systemd[1395]: Reached target Basic System. Mar 11 09:35:23 weather systemd[1]: Started User Manager for UID 1000. Mar 11 09:35:23 weather systemd[1395]: Reached target Default. Mar 11 09:35:23 weather systemd[1395]: Startup finished in 251ms. Mar 11 09:35:28 weather systemd[1]: Started Session 3 of user sparsons. Mar 11 09:40:01 weather weewx[1148]: vantage: Requesting 200 LOOP packets. Mar 11 09:40:01 weather weewx[1148]: vantage: Gentle wake up of console successful Mar 11 09:46:39 weather weewx[1148]: vantage: Requesting 200 LOOP packets. Mar 11 09:46:39 weather weewx[1148]: vantage: Gentle wake up of console successful Mar 11 09:48:18 weather systemd[1]: Starting Cleanup of Temporary Directories... Mar 11 09:48:19 weather systemd[1]: Started Cleanup of Temporary Directories. Mar 11 09:53:17 weather weewx[1148]: vantage: Requesting 200 LOOP packets. Mar 11 09:53:17 weather weewx[1148]: vantage: Gentle wake up of console successful This can go on for some time. This is after a fresh reboot of the Ubuntu installation after the driver stopped working. So when the driver states it's requesting 200 LOOP packets, I am unsure if that means it's pulling actual data. Website still shows the same static data as it did after it's last full pull. You can see this @ https://weather.parsoli.net/weewx Any suggestion on how to tell if this is pulling data correctly? It's as if after a few pulls, meteobridge will become unresponsive on that port. however, it's still pushing weather data to WU via meteobridge internals... On Wednesday, March 11, 2020 at 9:49:23 AM UTC-5, mwall wrote: > > > > On Wednesday, March 11, 2020 at 10:32:33 AM UTC-4, Parsoli 69 wrote: >> >> ....and now the driver starts to suffer trying to query the Davis thru >> the meteobridge. I suspect even if we figured out how to get the realtime >> data to show, this problem with the driver to meteobridge combo will still >> peeter out. I noticed some very smart folks trying to get meteobridge to >> write to a db so that Weewx could read from it, however didn't see it going >> 100 yds for a touchdown. >> >> Mar 11 09:14:43 weather weewx[1067]: engine: Caught WeeWxIOError: Max >> tries exceeded while getting LOOP data. >> > > weewx tries repeatedly to connect to 192.168.1.20:22222, but those > attempts fail. > > is the meteobridge at ip address 192.168.1.20? > > is the meteobridge listening at port 22222? > > i do not have first-hand experience with the meteobridge port > relay/forward/relay (not sure which approach the meteobridge uses). i said > that it *should* work, because boris seems to be a very competent > developer, and i would be surprised if such a feature was not working, > given all of the meteobridge users and boris' responsiveness to fixing bugs. > > it is possible that the way that the weewx vantage driver probes the davis > hardware somehow exposes a bug in meteobridge or a bug in the weewx vantage > driver code. if so, we should fix that. > > however, doing that requires that you are certain that the problem is not > your configuration. > > can your weewx installation communicate directly with your vantage station? > > m > -- 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/def7ac5e-b3e5-4d21-b973-4a5c92cc6e83%40googlegroups.com.
