Topic: Console stopped uploading data to Wunderground

[WXDA]

Hi, I have a 1 week old Watson branded version of the Ecowitt HP2551 Weather Station Display Console (the newest one with the full colour display) and at 1am last night it stopped uploading data to Wunderground. The station shows as offline but the WU icon is still showed on the console.

Initially I thought it was a Wunderground issue (as 99% of the time it is) and tried fiddling with the station settings, re-adding my details into the console etc. but nothing worked. Then I power-cycled the console and it started sending data, but only for 1-2 minutes before it stopped again. Now the only way to get the console to send data is to power-cycle it every couple of minutes.

The console is still sending data to Ecowitt, Weathercloud, WOW and PWSWeather (through the custom option) and when I set up a new WU station and add those details to the console the same thing happens. This has led me to think it’s a console issue with WU.

I’ve tried updating the console to the latest firmware that was just released, moving it to another room just incase it’s interference, even restarting my router, but no joy.

The only thing I’ve not done is reset the console to factory settings. Before I do this nuclear option I wanted to check to see if anyone has come across anything like this before? I tried searching the forum but nothing came up.

Thanks
DA

[Jim Ace]

I have a 2902A  and I just noticed today that I'm having the same problem, all other weather services are updating but not WU.  Guess I'll wait and see, I'm betting that WU is the problem.

BTW WU list my station as Online.

[WXDA]

@Jim

Interesting… that does seem to point to a WU issue. Mine is listed online in my list of stations, but the actual station page says it’s as it’s offline. That could be because it’s not reported for 1h+ though.

[edit] Just looked at your page and it’s the same as mine.

[Jim Ace]

Mine is reporting intermittently,  it will report for and hour and then offline, I'm going to wait day and see if it get resolved before I start messing with the station.

[Rover1822]

I have had this issue, and I have a rather involved network with 11 cameras and other devices , I think like 35 on my network.

In some cases a soft reboot of your router (via its interface) is not enough, do a full router power down (unplug, wait a bit, plug back in). Also , don't discount a re-power or online reset of your modem (if separate)

[Jim Ace]

I tried a power down and reboot the router, still had the problem funny Ambient weather dashboard is working just fine.

[Jim Ace]

Update, I unplugged the router for five mins and rebooted, all is working at this time.   

[WXDA]

I just switched off and unplugged my router for 5 minutes, reconnected it and data is flowing to Wunderground again. What would cause that issue that this kind of reboot would fix? Interested to see how long this will last (not holding my breath ).

Thanks Jim and Rover for the help

[Rover1822]

I don't have a flat answer why. Could be a whole bunch of things, DHCP lease times and reconnect, some buffer, DNS cache  etc.

[Waimarie]

I have 2 stations on WU.  Both show as being on-line, but only one is showing any data.

I am NOT playing with any settings.  I will just leave it up to the almighty IBM to sort out their sh*t.   

Until then, CumulusMX rules 

[WXDA]

I emailed WU tech support about the issue.They had no idea what was causing it but did say: "Are you using a dual band wireless router for the station?  I know of people getting flakey results with them."

My router is dual band so maybe there’s something in that? Anyway, for now everything is working again

[Waimarie]

I emailed WU tech support about the issue.They had no idea what was causing it but did say: "Are you using a dual band wireless router for the station?  I know of people getting flakey results with them."

My router is dual band so maybe there’s something in that? Anyway, for now everything is working again

I would think 90% of internet users use dual band routers, so that is a very poor excuse!  After all it is only 11 year old technology. (in 3 months time)

And both my stations are reorting again, after one going down for a while.

[WXDA]

I would think 90% of internet users use dual band routers, so that is a very poor excuse!  After all it is only 11 year old technology.

You would think so. Got this email reply from Wunderground tech support this morning:
“Some people do experience this dropping out when using a dual band router.  If there's any way to turn off one band, it might improve the performance.”

This maybe worth a try for some people though I’m not changing my router settings. Wunderground should just be more reliable like most other PWS services.

[SWX]

Had the same exact issue with my GW1000 the other day but it resolved itself. I originally thought the issue was on my end since nearby stations were still uploading, very odd.

[lyric]

Similar problem, I have the European version of the 2902A some but by no means all nights it disconnects from Wunderground at 03.28 local time. It does not reconnect until AC power is reset.
Wunderground say they are not doing anything at that time, like a backup.
I don't know where to go next.
I am going to start leaving my PC on 24/7 to see if any errors are recorded trying to rule out router/ISP.
how do I get the latest update for the console ?
I am open to any suggestions.

[galfert]

I have a thought that there was some issue with DNS as it relates to IPv6. For those of you with issues, do you know if your ISP gives you both IPv4 and IPv6 Internet presence?

I don't think this is still an issue. But I believe something happened with IPv6 DNS. I was getting non-responses from 1.1.1.1. It still worries me that sometimes I see see this below where is shows Server: UnKnown but then other times it doesn't. So that isn't consistent. Before though what I saw was not only Server UnKnown but also no DNS results from IPv6 DNS servers while at the very same time if I queried any IPv4 DNS server it always got a response.

Now bad Server UnKnown but still provides good DNS results:

Code: [Select]

C:\Windows\System>nslookup rtupdate.wunderground.com 2606:4700:4700::1111
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  2606:4700:4700::1111

Non-authoritative answer:
Name:    prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-0001.us-south.containers.appdomain.cloud
Addresses:  52.116.188.162
          169.60.133.174
          169.47.111.60
Aliases:  rtupdate.wunderground.com
          prod-pws-ng-ingest.prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-0001.us-south.containers.appdomain.cloud

Now a typical good response:

Code: [Select]

C:\Windows\System>nslookup rtupdate.wunderground.com 2606:4700:4700::1111
Server:  one.one.one.one
Address:  2606:4700:4700::1111

Non-authoritative answer:
Name:    prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-0001.us-south.containers.appdomain.cloud
Addresses:  169.60.133.174
          52.116.188.162
          169.47.111.60
Aliases:  rtupdate.wunderground.com
          prod-pws-ng-ingest.prod-pws-ng-546567-997b58a668d15d562a6bed58ea7c5f9e-0001.us-south.containers.appdomain.cloud

Before when I and everyone else was not uploading to WU:

Code: [Select]

C:\Windows\System>nslookup rtupdate.wunderground.com 2606:4700:4700::1111
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  2606:4700:4700::1111

DNS request timed out.
    timeout was 2 seconds.
*** UnKnown can't find rtupdate.wunderground.com: Non-existent domain


[WXDA]

@lyric Updating firmware made no difference for me. Only way I “fixed” it was to unplug the router for >5mins and then plug it back in. Had to reboot the console too to bring everything back online. Been ok for 5 days so far, will be interesting to see if it will disconnect the same time this week as last.

@galfert my ISP only gives me IPv6.

[galfert]

@galfert my ISP only gives me IPv6.

Exactly! I think WU messed up their IPv6 DNS AAAA record....which they have now fixed.

[Calochortus]

Saw the same thing, hard stop a hair before midnight ET and then back on at 7AM ET on 2020-07-10.

Funny though, I thought it was my internal DNS proxy gone wonky.