weewx.drivers.vantage no longer talking to my weatherlinkIP

[Greg Guldenschuh]

Folks,

  I updated weewx to version 5.2.0-1 on Debian 12.9 earlier in the week and it appears that weewx is no longer talking to the weatherlink IP (WLIP) interface.  I can ping the  WLIP IP address and get a response to the ping.

I am getting an IP read error: timed out.

[John Smith]

weeWX log output would be more informative, also set debug=1 in weewx.conf if you haven't already...

--
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 visit https://groups.google.com/d/msgid/weewx-user/c9546419-1bd0-4a12-863b-d90217b52995n%40googlegroups.com.

[Greg Guldenschuh]

I saw these after I filed the issue, but decided to save them and would upload them as I got the chance.

These were shown in the weewx.log file the service them exited with errors.

Nov 08 14:29:07 VE1 weewxd[2360]: ERROR weewx.drivers.vantage: ip-read error: timed out
Nov 08 14:29:14 VE1 weewxd[2360]: ERROR weewx.drivers.vantage: ip-read error: timed out
Nov 08 14:29:20 VE1 weewxd[2360]: ERROR weewx.drivers.vantage: ip-read error: timed out
Nov 08 14:29:27 VE1 weewxd[2360]: ERROR weewx.drivers.vantage: ip-read error: timed out
Nov 08 14:29:28 VE1 weewxd[2360]: ERROR weewx.drivers.vantage: Unable to wake up Vantage console
Nov 08 14:29:28 VE1 weewxd[2360]: ERROR weewx.engine: Import of driver failed: Unable to wake up Vantage console (<class 'weewx.WakeupError'>)
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****  Traceback (most recent call last):
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****      self.console = loader_function(config_dict, self)
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****                     ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****      return VantageService(engine, config_dict)
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in __init__
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****      Vantage.__init__(self, **config_dict[DRIVER_NAME])
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****      ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 539, in __init__
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****      self._setup()
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****      ~~~~~~~~~~~^^
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 1440, in _setup
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****      self.port.wakeup_console(max_tries=self.max_tries)
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****      ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 113, in wakeup_console
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****      raise weewx.WakeupError("Unable to wake up Vantage console")
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL weewx.engine:     ****  weewx.WakeupError: Unable to wake up Vantage console
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL __main__: Unable to load driver: Unable to wake up Vantage console
Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL __main__:     ****  Exiting...
Nov 08 14:29:28 VE1 systemd[1]: weewx.service: Main process exited, code=exited, status=4/NOPERMISSION

I will turn on the debug tomorrow and restart weewx and see what comes out.

BTW, everything was working just fine on weewx 5.1 before the update.

Thanks,

Greg Guldenschuh

[John Smith]

That would seem to indicate that weeWX connected to the IP since there is no mention of it, but the console wouldn't respond, or not as it's expecting anyway...

Tried taking out batteries from the console and disconnecting from power until it goes flat and then putting them back in etc?

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/d9cd6ace-7edb-4710-8d97-c6e8fc00dffd%40gmail.com.

[Greg Guldenschuh]

Console has no batteries in it, it is on UPS power all the time.

Have powered down waited for over a minute, the powered back up more than 5 times already save exact response, or lack thereof each time.

I did already mention that the 5.1 version of weewx was working up to and until the 5.2 version was installed.

Greg G.

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/Raw1AqYysM4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAGTinV45DspAfRfpFAUNMP1VW6mA%2BYfMid76W2QgdRy0rJ9Q8g%40mail.gmail.com.

[John Smith]

Might need to factory reset it somehow then.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/88c68141-0016-4fa7-aa25-47b8090e5768%40gmail.com.

[Greg Guldenschuh]

I will have to look up how to do that.

I have to replace 2 thermostats in my water heater tomorrow, that will take most of the day.

I may have to do this on Monday.

Thanks, I will respond after I get the water heater fixed tomorrow.

Greg G.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAGTinV44eHTZRajP99ro0kMqZ-wY9M1d7ZUN3MvPPf%2BvpTWxUQ%40mail.gmail.com.

[jterr...@gmail.com]

in your log, I see "NOPERMISSION3:

Nov 08 14:29:28 VE1 weewxd[2360]: CRITICAL __main__:     ****  Exiting...
Nov 08 14:29:28 VE1 systemd[1]: weewx.service: Main process exited, code=exited, status=4/NOPERMISSION

 

You may have to read this weewx wiki article about network permissions :  https://github.com/weewx/weewx/wiki/Understanding-permissions#how-to-fix-network-permissions

[John Smith]

I don't think that's it or it would have complained about not being able to connect and would have spat out the IP and port....

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/ac9e685a-0650-4cc3-933b-f7e0497a80d7n%40googlegroups.com.

[Greg Guldenschuh]

John,

   Set debug=1 and restarted weewx.  

I have attached a file where I extracted all the weewx lines from syslog.

Hopefully this helps you.

BTW, I checked Davis's weatherlink and it is getting data from my site.

Thanks,

Greg G

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAGTinV7SRQqYYzjTPwk5KdaaENtE7rxn4pq3TZnToqhHickKKA%40mail.gmail.com.

[John Smith]

I'm only seeing console lines standing out, both succeeding and failing... So it's not a networking problem as far as I can see... Corrupt memory issue maybe?

ERROR weewx.drivers.vantage: send_data: no <ACK> received from Vantage console
ERROR weewx.drivers.vantage: LOOP batch try #1; error: No <ACK> received from Vantage console
DEBUG weewx.drivers.vantage: Successfully woke up Vantage console

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/e49cedd3-2d4e-45eb-ae03-cdedec81fd2e%40gmail.com.

[Tom Keffer]

I don't know why you're getting the LOOP errors, but the memory in your console is definitely corrupted. See the wiki article Corrupt station memory.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAGTinV7WxQQp669DdAxcb7E9BiJHofeCfE5kjcP3Hz8CFgjDPw%40mail.gmail.com.

[Greg Guldenschuh]

John,

  I am able to log into my weatherlink.com account and see all the data for my station, up to date to the very minute, including the hi/lo loop data that gives errors with weewx.

It would seem that if there is a memory corruption in my console, then that same corruption should affect all data collections, and since weatherlink.com has all the data and it is currently collecting, with no errors, I have to wonder if the assessment of memory corruption is not correct.  I am seeing on the forum  lot of these memory corruption diagnostics.

These errors all seem to have started when I upgraded from 5.1 to 5.2, is there a good way to downgrade back to 5.1 and see if the errors go away?

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAGTinV7WxQQp669DdAxcb7E9BiJHofeCfE5kjcP3Hz8CFgjDPw%40mail.gmail.com.

[Greg Guldenschuh]

John,

   Yesterday I noticed some dust on the top of the console and I got some canned air and blew it through all the vent holes on the console.

This morning I restarted weewx 5.2 and now it is reading fine and posting my updates.

Let's keep this issue open till the end of this week to see if the problem comes back.

On 11/9/2025 6:53 PM, John Smith wrote:

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAGTinV7WxQQp669DdAxcb7E9BiJHofeCfE5kjcP3Hz8CFgjDPw%40mail.gmail.com.

[John Smith]

I'm guessing it's 2 different types of memory in play, RAM and some sort of storage memory for more than the current archive period, and it's the latter causing problems....

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/70afdc1c-d78b-4ae4-9482-6f9035693b8e%40gmail.com.

[John Smith]

Yep heat can definitely have that effect on electronics.... or in this case lack of air flow to take the heat away...

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/0e18cf9b-76b6-4d56-bb16-4bd4cf06993a%40gmail.com.

[Greg Guldenschuh]

Tom,

  Since I took a can of canned air and blew the dust out of the console, it now appears to be working again.

I thought of that after seeing the dust on top of the console when I took it down from the wall.

I have seen cases in my career in IT where dust accumulation caused heat problems and where the dust was conductive enough to cause spurious currents among the leads of ICs and that was enough to cause problems.

I try to look for the simpler explanations first.

Since taking the canned air and blowing the console clean through all ventilation holes and inside the battery compartment, the console is functioning perfectly.

I would recommend this as a first step--and a lot less expensive than replacing a console--in troubleshooting the issues that I was getting.

In my experience when memory goes bad, it stays bad, and does not come back to life after a good dust removal.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEBBoE8Wa7gMeoq4z2Rxiz_mWp5Ufi5k3bKOoMPWKmA5vw%40mail.gmail.com.

[Tom Keffer]

On the Davis stations, the memory can get internally corrupted, particularly after a power failure. It is an algorithmic failure, not an electronic failure. In all cases that I know of (probably a couple hundred over the history of WeeWX) it can be corrected by clearing the memory.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/448bb01d-d59c-4903-a581-011866186621%40gmail.com.

[Greg Guldenschuh]

My observations are over my 47 year career in IT.  Don't dispute that you have a point  with corruption.  I have tried clearing the console memory multiple times, and still had the problem.   

I finally noticed the dust and tried that. As soon as I powered the console up and get it connected to weewx, it began working again.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEChshhui8SmxaEKGaWgTGuv4k2oxsO2VCUGv%3DRmuxRdaA%40mail.gmail.com.

[Ryan Stasel]

Hey all,

I've been chasing an issue like this occasionally for years. Never found any good reason for it. fwiw, Davis does have a link in their documentation about how the console won't respond if it's uploading to weatherlink at the time, and the other device should just retry: https://support.davisinstruments.com/article/ohno6ugc5x-how-do-i-communicate-directly-with-my-weather-link-ip-data-logger

At this point I'm going to try creating a dedicated vlan for the Davis so nothing else can possibly talk to it other than weewx. 

[Greg Guldenschuh]

Ryan,

  I had the same issue.  My console had been working hanging in the wall in my basement for 8 years. While I was working to define the problem, I noticed some dust trails on the top of the console while hanging.  I eventually got a can of canned air and blew out the entire inside of the console through every hole I could get the straw in.  After that it started talking again.  This is a really inexpensive possible way to fix it.  I suggest trying this first. 

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/e56edec6-a3d2-4365-bd17-9d30fc75d51bn%40googlegroups.com.