Frequent weewx exiting with Vantage 6555 (WeatherIP)

81 views
Skip to first unread message

Ryan Stasel

unread,
Jun 4, 2025, 2:31:17 PM6/4/25
to weewx-user
Hi All,

For the last few months I've had issues with my Weewx instance crapping out not able to talk to the 6555 I have (in a weather envoy). 

Before I go down the hardware issue avenue, wondering if anyone else has seen issues with these. 

It crashed on me this morning around 7:15am, and looks like it just stopped responding? It's up now though. (I restarted weewx and it recovered and downloaded the archived records).

Thanks! 

Here's the log output

Jun 04 07:16:26 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: ip-read error: timed out

Jun 04 07:16:26 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: LOOP batch try #1; error: timed out

Jun 04 07:20:22 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: ip-read error: timed out

Jun 04 07:20:22 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: DMPAFT try #1; error: timed out

Jun 04 07:20:28 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: ip-read error: timed out

Jun 04 07:20:31 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: send_data: no <ACK> received from Vantage console

Jun 04 07:20:31 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: DMPAFT try #2; error: No <ACK> received from Vantage console

Jun 04 07:20:37 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: ip-read error: timed out

Jun 04 07:20:40 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: send_data: no <ACK> received from Vantage console

Jun 04 07:20:40 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: DMPAFT try #3; error: No <ACK> received from Vantage console

Jun 04 07:20:45 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: ip-read error: timed out

Jun 04 07:20:49 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: send_data: no <ACK> received from Vantage console

Jun 04 07:20:49 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: DMPAFT try #4; error: No <ACK> received from Vantage console

Jun 04 07:20:49 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: DMPAFT max tries (4) exceeded.

Jun 04 07:20:49 raspi-server-misc weewxd[187111]: INFO weewx.engine: Main loop exiting. Shutting engine down.

Jun 04 07:20:49 raspi-server-misc weewxd[187111]: INFO weewx.engine: Shutting down StdReport thread

Jun 04 07:20:49 raspi-server-misc weewxd[187111]: CRITICAL __main__: Caught WeeWxIOError: Max tries exceeded while getting archive data.

Jun 04 07:20:49 raspi-server-misc weewxd[187111]: CRITICAL __main__:     ****  Waiting 60.0 seconds then retrying...

Jun 04 07:21:49 raspi-server-misc weewxd[187111]: INFO __main__: retrying...

Jun 04 07:21:49 raspi-server-misc weewxd[187111]: INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage)

Jun 04 07:21:51 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: send_data: no <ACK> received from Vantage console

Jun 04 07:21:51 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: _determine_hardware; retry #0: 'No <ACK> received from Vantage console'

Jun 04 07:21:52 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: send_data: no <ACK> received from Vantage console

Jun 04 07:21:52 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: _determine_hardware; retry #1: 'No <ACK> received from Vantage console'

Jun 04 07:21:52 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: send_data: no <ACK> received from Vantage console

Jun 04 07:21:52 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: _determine_hardware; retry #2: 'No <ACK> received from Vantage console'

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: send_data: no <ACK> received from Vantage console

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: _determine_hardware; retry #3: 'No <ACK> received from Vantage console'

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: ERROR weewx.drivers.vantage: Unable to read hardware type; raise WeeWxIOError

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: ERROR weewx.engine: Import of driver failed: Unable to read hardware type (<class 'weewx.WeeWxIOError'>)

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****  Traceback (most recent call last):

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****      self.console = loader_function(config_dict, self)

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****      return VantageService(engine, config_dict)

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in __init__

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****      Vantage.__init__(self, **config_dict[DRIVER_NAME])

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 539, in __init__

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****      self._setup()

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 1444, in _setup

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****      self.hardware_type = self._determine_hardware()

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****                           ^^^^^^^^^^^^^^^^^^^^^^^^^^

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 1435, in _determine_hardware

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****      raise weewx.WeeWxIOError("Unable to read hardware type")

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL weewx.engine:     ****  weewx.WeeWxIOError: Unable to read hardware type

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL __main__: Unable to load driver: Unable to read hardware type

Jun 04 07:21:53 raspi-server-misc weewxd[187111]: CRITICAL __main__:     ****  Exiting...

Jun 04 07:21:53 raspi-server-misc systemd[1]: weewx.service: Main process exited, code=exited, status=4/NOPERMISSION

Tom Keffer

unread,
Jun 4, 2025, 3:47:56 PM6/4/25
to weewx...@googlegroups.com
Judging from the last entry in the log, it could be a permissions issue.

--
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/5699cb36-3fba-4965-8e84-0fa2246a234cn%40googlegroups.com.

Ryan Stasel

unread,
Jun 4, 2025, 3:54:01 PM6/4/25
to weewx...@googlegroups.com, weewx...@googlegroups.com
Agreed, but it starts back up fine. 

So I’m not clear what permission it might be complaining about. :/ 

All the errors prior seem to indicate the console isn’t responding. 



On Jun 4, 2025, at 12:47, Tom Keffer <tke...@gmail.com> wrote:


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/4rqjXVeS-3Y/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/CAPq0zEAsVnFEqxibOQK6ZpgYaS7tWLS%3DFo_ijHQx_aZQKXJ0mA%40mail.gmail.com.

Ryan Stasel

unread,
Jun 5, 2025, 3:38:02 PM6/5/25
to weewx...@googlegroups.com
Hey Tom (et al),

Looks like this is potentially a red herring, it just means it exited with status code 4, but doesn’t necessarily mean “NOPERMISSION”.


It's unclear WHY this is happening with this setup. 

Anything I can do to try to help figure out? Or maybe some way to adjust the “waiting 60.0 seconds” and have it say wait for a couple minutes after it doesn’t recover in 60 seconds? 

Thanks! 

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/4rqjXVeS-3Y/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/CAPq0zEAsVnFEqxibOQK6ZpgYaS7tWLS%3DFo_ijHQx_aZQKXJ0mA%40mail.gmail.com.

vince

unread,
Jun 5, 2025, 5:52:06 PM6/5/25
to weewx-user
Couple wild guesses - do you have both wifi and wired ethernet configured up ? Perhaps the os can't figure out which interface to use ?   Alternately you might try setting loop-on-init to brute force trying to restart forever.  Again - these are wild guesses :-)
Reply all
Reply to author
Forward
0 new messages