Topic: PWS offine: FOSHK WH2600 data no longer accepted by Wunderground?

[Glamers]

Hi Forum!

This is a repost.... I previously posted this message in the "Wunderground"-discussion, but got no response whatsoever..
So, here we try again! (Hoping for the best!)

My station hardware is FOSHK WH2600, Renkforce version. As far as I can see identical to Ambient WS1400.
The console is running firmware: Weather Logger V 2.1.9.
It allows me to change the address it is sending its data to. I can change "server type" from PHP (current) to JSP or ASP.
Other configuration options are non-existent.

The station cooperated flawlessly with Wundergound since 2015, most of the time flying a "Golden Star". From that I conclude the protocol on my side is not on error.


On October 11 2022, 6:38 PM CET however, Wundergound stops reporting my WPS-data, stating my PWS is offline. My station (IUTRECHT299) nonetheless continued to operate until this very day.

Although I repeatedly tried to get feedback from Wunderground, they remain totally unresponsive.
These are my supporttickets:
   Request Number 03498067 [ ref:_00DA0L1VM._5002K16vxCO:ref ]
   Request Number 03591144 [ ref:_00DA0L1VM._5002K16yvh0:ref ]
As I wanted to be absolutely sure the error was not on my side, I ran WhireShark to analyse the traffic between my PWS and Wunderground:

==========================================================================
line   Date & Time                      Source                   Destination        Protocol    Length   Info
2   2022-11-25 12:51:51,515915   192.168.178.100   54.159.105.134   TCP   60   8605 → 80 [SYN] Seq=0 Win=5840 Len=0 MSS=1460
3   2022-11-25 12:51:51,861039   54.159.105.134   192.168.178.100   TCP   60   80 → 8605 [SYN, ACK] Seq=0 Ack=1 Win=62727 Len=0 MSS=1460
4   2022-11-25 12:51:51,864209   192.168.178.100   54.159.105.134   TCP   60   8605 → 80 [ACK] Seq=1 Ack=1 Win=5840 Len=0
5   2022-11-25 12:51:52,043831   192.168.178.100   54.159.105.134   HTTP   571   GET /weatherstation/updateweatherstation.php?
                                    ID=IUTRECHT299&
                                    PASSWORD=<hidden>&
                                    tempf=53.1&
                                    humidity=85&
                                    dewptf=48.7&
                                    windchillf=53.1&
                                    winddir=251&
                                    windspeedmph=5.82&
                                    windgustmph=7.38&
                                    rainin=0.00&
                                    dailyrainin=0.31&
                                    weeklyrainin=0.31&
                                    monthlyrainin=0.31&
                                    yearlyrainin=0.31&
                                    solarradiation=82.05&
                                    UV=1&indoortempf=61.5&
                                    indoorhumidity=72&
                                    baromin=30.12&
                                    lowbatt=2&
                                    dateutc=2022-11-25%2012:52:33&
                                    softwaretype=Weather%20logger%20V2.1.9&
                                    action=updateraw&
                                    realtime=1&
                                    rtfreq=5 HTTP/1.0
6   2022-11-25 12:51:52,143199   54.159.105.134   192.168.178.100   TCP   60   80 → 8605 [ACK] Seq=1 Ack=518 Win=62210 Len=0
7   2022-11-25 12:51:52,144097   54.159.105.134   192.168.178.100   HTTP   328   HTTP/1.1 404 Not Found  (text/html)
8   2022-11-25 12:51:52,144097   54.159.105.134   192.168.178.100   TCP   60   80 → 8605 [FIN, ACK] Seq=275 Ack=518 Win=62210 Len=0
9   2022-11-25 12:51:52,166801   192.168.178.100   54.159.105.134   TCP   60   8605 → 80 [ACK] Seq=518 Ack=275 Win=5840 Len=0
10   2022-11-25 12:51:52,168162   192.168.178.100   54.159.105.134   TCP   60   8605 → 80 [FIN, ACK] Seq=518 Ack=276 Win=5840 Len=0
11   2022-11-25 12:51:52,267657   54.159.105.134   192.168.178.100   TCP   60   80 → 8605 [ACK] Seq=276 Ack=519 Win=62209 Len=0

==========================================================================

Apart from TCP handshakes, it can be seen on line 5 that my station (source 192.168.178.100) sends a HTTP "GET" and further data to destination 54.159.105.134 (rtupdate.wunderground.com). Wundergound (source 54.159.105.134) replies on line 7 with a "HTTP/1.1 404 Not Found".

What can be made of that?? Did Wunderground update its serversoftware? Did it move to another address? Or am I just cancelled? 


What to do? Did anyone have the same problem? How to have a (two-way) communication with Wunderground?


Please help me out?

Kind regards,
Gus Lamers
the Netherlands

[Rover1822]

I deleted my post that said to use a different url as yours worked for me , as long as I used the domain name and not the IP

I get a bad request as I am not including data , but not a 404
If use the IP of the URL then I get a 404

[olicat]

Hi!

This certainly sounds more like DNS problems on your side than problems with WU itself.
Take a web browser and go to the following page:

https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?

What do you get as a message in the browser window?

For me it says "bad request" - which is not an error - because the request is indeed bad.
But if you get a "404 page not found" you should look for the problem in your DNS - maybe the IP address was changed on WU's side and your name resolution still points to the old IP address.
Does your weather station receive the DNS server via DHCP or is it entered manually?

According to dig, rtupdate.wunderground.com refers alternately to the IP addresses 52.22.134.222 and 34.232.250.77 and 54.159.105.134 - so the IP address you are using should be correct.
Possibly this server had some temporary problems. Or the problem lies somewhere else entirely.
What do you get as a return message when you enter this URL in the browser?

https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?ID=IUTRECHT299&PASSWORD=%3Chidden%3E

And if you enter your real password instead of <hidden>?

If it is "unauthorized" you just have a password problem.

Oliver

[Rover1822]

Bingo !! (I think anyway)

You need to update your firmware. Something did indeed change

See https://www.foshk.com/Support/software/191.html   for the update.  Released 2022/11/29  version 2.2.8

"Solve the problem cannot connection to the server at wunderground"

Let us know if that works

[kheller2]

Just a guess, but it looks like they are sending the HOST header now with the name, vs IP addresses:

&action=updateraw&realtime=1&rtfreq=5 HTTP/1.0                            &action=updateraw&realtime=1&rtfreq=5 HTTP/1.0
Accept: */*                                                               Accept: */*
Host: %bu.%bu.%bu.%bu                                                |    Host: rtupdate.wunderground.com:80

[Glamers]

Thank you all for your replies!

I hope this will lead to a solution.

@olicat:
I ran the experiments you advised.
Going to: "https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?" results in "bad request".
Going to: "https://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?ID=IUTRECHT299&PASSWORD=%3Chidden%3E" naturally gives "unauthorized" in return.
But if I replace "hidden" with my Station Key, I get "bad request" again.
Going to: ""https://54.159.105.134/weatherstation/updateweatherstation.php?ID=IUTRECHT299&PASSWORD=StationKey" is blocked by my Virus Scanner, saying: "Your connection to this web page is not safe due to an unmatching security certificate".
My PWS receives the DNS server via DHCP.
Could this info bring me any further?

@Rover1822:
You advise me to update my firmware.
I have to admit that I am a bit reluctant here..
In the past I inadvertently destroyed a device using PCtools...
Furthermore, FOSHK gives no information at all of what the update brings. For instance: could it change the sensor communication frequency? (My sensors operate on the 868 MHz band)
Moreover, as I said before, Wunderground is completely silent. Is it too much to expect an explanation from them? Can they change their interface without notice, leaving their users uninformed? Is anyone else suffering from the same problem? If I don't have any info of what exactly should be corrected, should I go this trial-and-error game, running the risk of losing my device all together?

@kheller2:
As I replied to olicat, I tried "rtupdate.wunderground.com" vs. "54.159.105.134", only to get my experiment blocked by Bitdefender...

Again, many thanks to think along with me and hope to hear from you all soon!

Regards,

Gus

[olicat]

Hi!

It seems to be no problem with DNS because the destination acts as expected with "bad request" and "unauthorized". The "bad request" on your second try results on missing any measurement data - if you would send a

http://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?ID=IUTRECHT299&PASSWORD=password&dateutc=now

it should be accepted with "success" (if you use your password).
Then you know that everything (WU itself, connection, DNS, credentials) is ok.
The only open point ist your weather station itself.

Therefore, I would seriously advise a firmware update. Especially because it explicitly says something about fixing it with WU:

WH2600 firmware V2.2.8
Solve the problem cannot connection to the server at wunderground

I don't think that this update can change anything about the frequency of the station.

Of course, it can happen that you brick the station during the update and it can no longer be used. But what is the difference to the current state?
With the update there is at least hope.

Oliver

[Rover1822]

In the zip file firmware download there are explicit instructions on how to perform the upgrade. Personally I think the risks are minimal.

As far as WunderGround, this appears to be a change that did not effect many stations, otherwise there would be a huge uproar. As far as can they change things at will, yeah, they can, one would think they would consider the impact of changes, but in reality they are probably not familiar with all the different station types out there.

[Glamers]

Hi everyone,

thanks for thinking with me.

I tried to upgrade using IPTools but, yes, my station is "bricked".........

I download the new firmware from FOSHK (WH2600_V2.2.8_0xC782DE20.BIN) and I used the latest version of IPTools that I found on the site of Ambient (https://ambientweather.com/mwdownloads/download/link/id/623)

I connected my PC to my base station through a Hub (NOT a switch!) and the hub in its turn to the internet.

I ran IPTools. It found my station immediately. I selected the new firmware from FOSHK and pressed "upgrade".....

This line turned up:
"TFTP server @ 192.168.178.41 is running on UDP port 69 succesfully."

After that..... nothing.... The green bar showed no progress at all.

I waited for more than an hour. At that time I cancelled IPTools.
The result: My base station is dead...

If anyone out there is having an idle FOSHK base station, an "ObserverIP" or anything like that, that scans for sensors at the 868 MHz band, please let me know!

Thanks again.....
Gus

[olicat]

Hi!

Sorry ...
Is the station no longer found at all? Not even after switching it off and on again?
Anything binking on the WH2600?

Oliver

[Glamers]

I'am afraid, no...
Power and ACT lights are blinking.
Reboot (switching it off and on) doesn't help.
PCTools does not find the device any more..

Over and out, I think...

Now I am left with a perfectly good pair of sensors and no way to read them out.

A new base station would be wunderful!

(I am prepared to pay for it!)

Gus

[olicat]

Hi!

Which outdoor sensor do you use? The original one from the WH2600 set (the boat)?
Which other sensors do you own?
It think all these should also run with e.g. a GW1100 or GW2000.
The GW2000 could even make use of the LAN cable you used for the WH2600. But it could also use WIFI - as could the GW1100.
If your sensors work with 868MHz, you would only have to buy a corresponding console with 868MHz.

Apart from that:
Write an email to Ecowitt support and explain what you have done and what the situation is. Maybe they have another idea.

Oliver

[kheller2]

I do feel bad about the bricking.   I'm not sure if they have a battering in them that can be removed (I know some consoles like the WS2000 DO and can get locked up and repaired by removing that battery).  I'm wondering if the flash didn't go because of firewall issues with windows or something else.   In any case, a GW11000 or GW2000 can be had on Amazon at 15% off at times or order directly from Ecowitt.

But before any of that, let us know what sensors you have so we can help you out (better than we have).

[uzeka]

Dear Gus,

you made my day, thanks a million!
Guess what - exactly the same problem here. Tried everything to isolate the cause but ended up with 'must be something at wunderground'.
My station is Eurochron EGWS1000, FW 1.6 (using config SW "Weather Logger GSM '1.8'). Wunderground reported it to be offline since
Oct 11th 22 at 06:34 pm (GMT+2).

https://www.wunderground.com/dashboard/pws/IGERBS4

Now, we need to elaborate what changed there an if we can mitigate it with the station config parameters. But I doubt...
Unfortunately, my station seems to be unsupported and there is no FW update avail. I'd switch to a different weather portal if I knew which would work an how to connect, or host the data on my own server, if I knew which solution would be needed to manage the data.

Have a nice Advent Sunday
Ulrich

[olicat]

Hi!

If you can send data via custom server, you are of course able to send the data to a local destination or other compatible services (such as Awekas).
See if you can configure your own destination and, if necessary, test with EAR which data is actually transmitted.
Then you could check the comparison PDF to see if you can find a solution that suits you.

Ulrich sounds like a German-language name - perhaps the German version of the PDF will fit better.

Oliver

[uzeka]

Will give it a try, thanks, most appreciated!

[olicat]

Hi!

Although I'm afraid this new version doesn't fix your WU problem.
There is a newer version than v1.6 of Weather Logger GSM: v1.8.
This version is from November 2020 - maybe that would be worth a try?
Otherwise you should definitely ask Ecowitt about it by email.

add:
Too bad, I just saw that the files in the ZIP are newer than those of v1.6 but are still from 2017. This makes it even less likely that your WU problem will be solved. But as a (pre)last try, I would probably take a chance.

Oliver

[Glamers]

Hi all!

first of all I want to state that no one is to blame for "bricking" my station. It was me, and only me, who executed the upgrade that turned out disastrous.

I contacted Ecowitt and this is their answer:"You can buy our GW1100 or GW2000 hub. It can be purchased here: https://shop.ecowitt.com/collections/lan-wifi-gateway".

So that is what I did. It will arrive next Friday. Let's see what happens.

I'll keep you posted!

Gus

[olicat]

Hi!

It still makes me uncomfortable to have given you this advice.
Sorry!

Please note that the GW1100 requires a WIFI connection - so a LAN cable cannot be plugged in there. A GW2000 offers a LAN socket in addition to the WIFI.
And:
When configuring via the WSView Plus app, you must - if you have the old outdoor sensor of the WH2600 ("the boat") - tick the corresponding box under More/Device Settings/Sensor Type. Otherwise, the rain and/or wind data may not be correct.

Regards, Oliver

[Glamers]

@olicat:

Do not worry. It was a risk that I met before, also on a renkforce base station. (At that time I could return it to Conrad under guarantee. Not anymore this time.)

Here is a link to the set I have: "https://www.conrad.de/de/p/renkforce-renkforce-wh2600-funk-wetterstation-vorhersage-fuer-12-bis-24-stunden-1267654.html".
Is this what you call "the boat"? (I'll have to admit: It looks indeed a bit like a boat. My wife thinks more of a loo.  )

I ordered the GW2000.
I'll try to find the mentioned box next weekend.

Hope this will solve it all.

Gus

[Rover1822]

Yep that is known as the boat or WH24. It is now consider to be an older outdoor array, but if it works, cool.

[olicat]

Hi!

In another forum there was a success story today that after this update WU with the WH2600 is working properly again.
So basically the update works. I don't know why it didn't work in your case. However, a grateful culprit would be your virus scanner.

Oliver

[Rychu]

To @Glamers:

Please, be sure to read this_click

[Glamers]

Hi all!

First of all I have to thank you for your help.
The Ecowitt GW2000 does the trick. I am back on line again, and got even my Gold Star back!

Now, just because I am curious, I ran Wireshark again.
Below you will find the result. I placed the old "Weatherlogger" data (first column) next to the new "GW2000" stuff (second column).

12   2022-12-19 10:53:04,695352   192.168.178.100   54.159.105.134   TCP   60   63799 → 80 [SYN] Seq=0 Win=5744 Len=0 MSS=1440
13   2022-12-19 10:53:04,797082   54.159.105.134   192.168.178.100   TCP   60   80 → 63799 [SYN, ACK] Seq=0 Ack=1 Win=62727 Len=0 MSS=1460
14   2022-12-19 10:53:04,798369   192.168.178.100   54.159.105.134   TCP   60   63799 → 80 [ACK] Seq=1 Ack=1 Win=5744 Len=0
15   2022-12-19 10:53:04,805541   192.168.178.100   54.159.105.134   HTTP   564   GET /weatherstation/updateweatherstation.php?
   ID=IUTRECHT299&                  ID=IUTRECHT299&
   PASSWORD=<hidden>&               PASSWORD=<hidden>&
   tempf=53.1&                     tempf=46.40&
   humidity=85&                     humidity=99&
   dewptf=48.7&                     dewptf=46.22&
   windchillf=53.1&                  windchillf=42.80&
   winddir=251&                     winddir=151&
   windspeedmph=5.82&               windspeedmph=6.93&
   windgustmph=7.38&                  windgustmph=14.99&
   rainin=0.00&                     rainin=0.000&
   dailyrainin=0.31&                  dailyrainin=0.213&
   weeklyrainin=0.31&                  weeklyrainin=0.272&
   monthlyrainin=0.31&                  monthlyrainin=0.272&
   yearlyrainin=0.31&                  yearlyrainin=0.272&
   solarradiation=82.05&               solarradiation=27.68&
   UV=1&indoortempf=61.5&               UV=1&indoortempf=57.56&
   indoorhumidity=72&                  indoorhumidity=63&
   baromin=30.12&                  baromin=29.970&
   lowbatt=2&                     lowbatt=0&
      dateutc=2022-11-25%2012:52:33&         dateutc=now&
   softwaretype=Weather%20logger%20V2.1.9&   softwaretype=GW2000A_V2.2.0&
   action=updateraw&                  action=updateraw&
   realtime=1&                     realtime=1&
   rtfreq=5 HTTP/1.0                   rtfreq=5 HTTP/1.0
16   2022-12-19 10:53:04,905769   54.159.105.134   192.168.178.100   TCP   60   80 → 63799 [ACK] Seq=1 Ack=511 Win=62217 Len=0
17   2022-12-19 10:53:04,908349   54.159.105.134   192.168.178.100   HTTP   334   
      HTTP/1.1 404 Not Found  (text/html)         HTTP/1.1 200 OK  (text/plain)
18   2022-12-19 10:53:04,908698   54.159.105.134   192.168.178.100   TCP   60   80 → 63799 [FIN, ACK] Seq=281 Ack=511 Win=62217 Len=0

From this,it can be seen that the ONLY difference between the two is the "dateutc" format:
Weatherlogger: dateutc=2022-11-25%2012:52:33& vs. GW2000: dateutc=now&.
Could this have been a time sync thing?

Well, although being happy with my new device, one (little) disappointment remains:The GW2000 refuses to pick up my old WH25 indoor sensor. I would like to install it in a different room...
Ecowitt support replies as followes: "Wh25 is indoor TH&P sensor, and this sensor has integrated on GW2000 already. So it will not pick up your wh25 sensor data"... Pity.
Does anyone know the trick to have the GW2000 pick up all the sensors in its reach? (Or should this be a different topic?)

Thanks!
And a merry Christmas to you all!

Gus

[olicat]

Hi!

Even if it looks like it at first glance, it is probably not the case!
Put the string together and send it via web browser:

Code: [Select]

http://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?ID=IUTRECHT299&PASSWORD=pwd&dateutc=2022-12-23 12:45:00
http://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?ID=IUTRECHT299&PASSWORD=pwd&dateutc=2022-12-23+12:45:00
http://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?ID=IUTRECHT299&PASSWORD=pwd&dateutc=now
With all these requests you should receive a success.
The format for sending the time of the data (dateutc) is largely correct - more modern (?) systems use a "+" instead of the " " to separate the date and time. But all forms are still accepted by WU.
By the way, it does not change anything if the stationtype is also transferred - Weather%20logger%20V2.1.9 is therefore not on a blacklist.

I'm afraid it's not so much the content of the message, but the nature of the connection that has precluded the WH2600 from WU and requires its firmware update. Unfortunately, I don't see enough of the Wireshark recording.

Another difference, by the way, is lowbatt, whose status 2 is not quite clear to me. Presumably, 2 in this context simply means "runs on wall power".
But that has nothing to do with the impossibility of sending data to WU.

Prioritising the WH32B over the built-in sensors is a long-cherished wish of ours. So far, Ecowitt has just not implemented this.
In my experience, the sensors in the GW2000 are also much better than those of the WH32B - but if you want local separation, that doesn't help much.
You have two options:
Cut off/desolder the sensors on the GW2000 - then the GW2000 uses the data from the WH32B.
Buy a WH31 for the other room - it will then be displayed as additional temperature/humidity, but will reliably provide data without interfering with the GW2000.

But I don't want to be the one again who makes you do something that then goes wrong and leaves you with another destroyed device.
So, please use the WH31 option instead.

Regards, Oliver