weewx 4.0 fails connecting to Vantage Vue

126 views
Skip to first unread message

Andre C

unread,
May 1, 2020, 3:31:21 PM5/1/20
to weewx-user
After upgrading weewx from 3.9.2 to 4.0, weewx no longer recognizes the Vantage Vue console.

The console has a serial to IP link, so weewx communicates over Ethernet.
Below the output from syslog:

May  1 21:20:33 Domo systemd[1]: Starting LSB: weewx weather system...
May  1 21:20:35 Domo weewx[420] INFO __main__: Initializing weewx version 4.0.0
May  1 21:20:35 Domo weewx[420] INFO __main__: Using Python 3.7.3 (default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]
May  1 21:20:35 Domo weewx[420] INFO __main__: Platform Linux-4.19.97-v7+-armv7l-with-debian-10.3
May  1 21:20:35 Domo weewx[420] INFO __main__: Locale is 'nl_NL@euro'
May  1 21:20:35 Domo weewx[420] INFO __main__: PID file is /var/run/weewx.pid
May  1 21:20:35 Domo weewx[443] INFO __main__: Using configuration file /etc/weewx/weewx.conf
May  1 21:20:35 Domo weewx[443] DEBUG __main__: Initializing engine
May  1 21:20:35 Domo weewx[443] INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage)
May  1 21:20:35 Domo weewx[332]: Starting weewx weather system: weewx.
May  1 21:20:35 Domo systemd[1]: Started LSB: weewx weather system.
May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Driver version is 3.2.0
May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Opened up ethernet host 192.168.178.10 on port 22222. timeout=4.0, tcp_send_delay=0.5
May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage: Gentle wake up of console successful
May  1 21:20:36 Domo weewx[443] ERROR weewx.drivers.vantage: No <ACK> received from console
May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage: _determine_hardware; retry #0
May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No <ACK> received from console
May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage: _determine_hardware; retry #1
May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No <ACK> received from console
May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage: _determine_hardware; retry #2
May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: No <ACK> received from console
May  1 21:20:38 Domo weewx[443] DEBUG weewx.drivers.vantage: _determine_hardware; retry #3
May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: Unable to read hardware type; raise WeeWxIOError
May  1 21:20:38 Domo weewx[443] ERROR weewx.engine: Import of driver failed: Unable to read hardware type (<class 'weewx.WeeWxIOError'>)
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****  Traceback (most recent call last):
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****      self.console = loader_function(config_dict, self)
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****      return VantageService(engine, config_dict)
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 1897, in __init__
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****      Vantage.__init__(self, **config_dict[DRIVER_NAME])
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 514, in __init__
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****      self._setup()
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in _setup
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****      self.hardware_type = self._determine_hardware()
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in _determine_hardware
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****      raise weewx.WeeWxIOError("Unable to read hardware type")
May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:     ****  weewx.WeeWxIOError: Unable to read hardware type
May  1 21:20:38 Domo weewx[443] CRITICAL __main__: Unable to load driver: Unable to read hardware type
May  1 21:20:38 Domo weewx[443] CRITICAL __main__:     ****  Exiting...

Any help is appreciated.

Tom Keffer

unread,
May 1, 2020, 6:01:05 PM5/1/20
to weewx-user
If you open up a telnet session to the Vue, can you communicate with it?

Use the connectivity test, except use telnet. 

--
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 on the web visit https://groups.google.com/d/msgid/weewx-user/30b975af-18ad-4c5e-b97e-a1d1cddb4821%40googlegroups.com.

Andre C

unread,
May 2, 2020, 12:54:58 AM5/2/20
to weewx-user
Attached the tcpdump output from the communication between weewx running on a raspberry PI and the vantage Vue console.
There is communication, but no data transfer.

Running telnet:

Trying 192.168.178.10...
Connected to 192.168.178.10.
Escape character is '^]'.VER

OK
RXTEST

OK
RXCHECK

OK

I hope this helps.

Andre

Op zaterdag 2 mei 2020 00:01:05 UTC+2 schreef Tom Keffer:
To unsubscribe from this group and stop receiving emails from it, send an email to weewx...@googlegroups.com.
weewxdump.text

Tom Keffer

unread,
May 2, 2020, 8:08:21 AM5/2/20
to weewx-user
Thanks.

Can you give us some details about your hardware setup? From your description that "the console has a serial to IP link" I had assumed that your Vantage Vue had a normal WeatherLink serial logger, which you were accessing via some sort of serial-to-IP converter. Is that the case?

Or, are you using the (now discontinued) Vantage WeatherlinkIP logger?

Or, something else?

-tk

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ae7b2620-a65a-4af9-8960-d233cfc78387%40googlegroups.com.

Andre Abepol

unread,
May 2, 2020, 11:55:20 AM5/2/20
to weewx...@googlegroups.com
I have a WeatherLink IP connected to theVantage Vue console.
Since about 6 weeks a Vantage Pro2 ISS is installed. At the same time I moved from the old wview softwareto weewx, which worked like a charm.
Until last week. First I was getting error messages like 'received unexpected 0xDD".
I found some tips, this might be due to clock drift and/or old software in the console.
Therefore I upgraded the console to the latest software ()1.15). The upgrade however did not solve the "0xDD" error messages. And now even these message are gone  and the whole communications is stuck.
Something between the WeatherLink IP and the console ??

Andre


Op za 2 mei 2020 om 14:08 schreef Tom Keffer <tke...@gmail.com>:

Andre C

unread,
May 2, 2020, 1:03:26 PM5/2/20
to weewx-user
After shutting down power, re-install the WeatherLink-IP and re-powering, the Vantage Vue console is now detected again!
However, another error message arises:

May  2 18:50:14 Domo weewx[12892] DEBUG weewx.drivers.vantage: Getting archive packets since 2020-05-01 11:35:00 CEST (1588325700)
May  2 18:50:15 Domo weewx[12892] DEBUG weewx.drivers.vantage: Gentle wake up of console successful
May  2 18:50:16 Domo weewx[12892] DEBUG weewx.drivers.vantage: Retrieving 3 page(s); starting index= 0
May  2 18:50:17 Domo weewx[12892] ERROR weewx.engine: Internal error detected. Catchup abandoned
May  2 18:50:17 Domo weewx[12892] ERROR weewx.engine: **** Unknown archive type = 0xdd

The starting point of weewx reflects the last record in the archive table (I assume the 2-hour time difference is due to the delta between localtime and UTC):
sqlite3 /var/lib/weewx/weewx.sdb
sqlite>SELECT datetime(dateTime,'unixepoch') FROM archive ORDER BY dateTime DESC LIMIT 1;
2020-05-01 09:35:00

Is this "Unknown archivetpe = 0xDD" a known issue ?

Andre


Op zaterdag 2 mei 2020 06:54:58 UTC+2 schreef Andre C:

Tom Keffer

unread,
May 2, 2020, 1:45:26 PM5/2/20
to weewx-user
I've seen this a few times. Try clearing the logger memory:

wee_device --clear-memory

-tk

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1079aeef-7a4d-49e9-b619-3ffff22c2063%40googlegroups.com.

Andre C

unread,
May 2, 2020, 1:57:44 PM5/2/20
to weewx-user
I first tried wee_device --dump in order to salvage the logger data. This failed due to a CRC16 error.
So as a last resort I cleared the memory.
As a net result i'm missing archive record fot about a day and a half.
The goood news is that the console output is monitored again!!!

thanks a lot for your help,

Andre

Op zaterdag 2 mei 2020 19:45:26 UTC+2 schreef Tom Keffer:
Reply all
Reply to author
Forward
0 new messages