Weather Display stops updating Wunderground

Software Weather Display for Windows
1

Hey folks,

Been using Weather Display for a few months so far, and everything’s been great. However just recently, every 2-3 days I’ll get the email from Wunderground that my station has stopped reporting. Logging into my server and restarting the Weather Display software fixes the issue.

I’m relatively new to Weather Display, so not sure how to debug (the menus are intimidating!). However the “brain dead” method of restarting it definitely fixes the issue every time.

Anyone seen this before?

2

What weather station type
?

What version/ build of WD?
When the problem occurs, is WD
Still getting data from the station?
What shows under view, program debug?

3

Howdy!

It’s a Davis Vantage Pro 2. I’m using the IP data logger.

Weather Display is 10.37S b94

Yep, when Wunderground complains Weather Display itself is trucking along just fine and receiving updates.

Next time it does it, I’ll check the debug log!

4

Ok, watched it closer. It is indeed not updating from the IP Data Logger. The logger is still on net, i.e. it is pingable. The weather display app isn’t blinking the “Data Received” whatsoever, nor is the number incrementing (it got stuck at 4520). Just sitting idle.

Here is what the Debug log shows (172.16.66.61 is the logger)

Doing checking of time zone calculation
Daylight saving in use
Loaded all time records
TCP/IP connected to 172.16.66.61
Doing checking of time zone calculation
Daylight saving in use
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
15:20:10 Error with TCP/IP Socket connection
15:20:10 Error with TCP/IP Socket connection
15:20:10 Error with TCP/IP Socket connection
15:20:10 Error with TCP/IP Socket connection
15:20:10 Error with TCP/IP Socket connection
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
15:27:10 Error with TCP/IP Socket connection
15:27:10 Error with TCP/IP Socket connection
15:27:10 Error with TCP/IP Socket connection
15:27:10 Error with TCP/IP Socket connection
15:27:10 Error with TCP/IP Socket connection
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
17:03:10 Error with TCP/IP Socket connection
17:03:10 Error with TCP/IP Socket connection
17:03:10 Error with TCP/IP Socket connection
17:03:10 Error with TCP/IP Socket connection
17:03:10 Error with TCP/IP Socket connection
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
17:32:10 Error with TCP/IP Socket connection
17:32:10 Error with TCP/IP Socket connection
17:32:10 Error with TCP/IP Socket connection
17:32:10 Error with TCP/IP Socket connection
17:32:10 Error with TCP/IP Socket connection
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
17:46:09 Error with TCP/IP Socket connection
17:46:09 Error with TCP/IP Socket connection
17:46:09 Error with TCP/IP Socket connection
17:46:09 Error with TCP/IP Socket connection
17:46:09 Error with TCP/IP Socket connection
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
clock sync
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61
TCP/IP connected to 172.16.66.61

5

Suggest you try a power off of the ip logger /console i.e. put console in setup mode then remove power lead and batteries for 1 min shut down WD before powering up logger again and press the done button and when it is receiving data then restart WD

6

do you happen to have the IP data logger set to send data to weatherlink.com ?
if so then try unsetting that (via the setup page (i.e in a browser, pointing it to , e.g 192.168.something)