Topic: new firmware version for GW2000: V2.2.4

[Rover1822]

honestly, the NTP described with the person having an issue is a non normal infrasture  .  I also run my own NTP , and have not had issues. But there are so many variables involved .

There are other devices that would have the same issue, but it is good to bring it to light.

[thunder.ky]

Unfortunately, I've also experienced issues with my GW2000 connecting to my sensors with v2.2.4. Never had any these issues with past firmware, and now I'm seeing various sensors disconnected. Some reconnect on their own, and others only after a reboot.

[broadstairs]

Unfortunately, I've also experienced issues with my GW2000 connecting to my sensors with v2.2.4. Never had any these issues with past firmware, and now I'm seeing various sensors disconnected. Some reconnect on their own, and others only after a reboot.

Are you using an ethernet connection or wifi?

Stuart

[atakama]

honestly, the NTP described with the person having an issue is a non normal infrasture  .  I also run my own NTP , and have not had issues. But there are so many variables involved .

There are other devices that would have the same issue, but it is good to bring it to light.

I agree, the NTP server is also at fault here, because replies with stratum = 0 should be used for KoD packets. The server should determine it own stratum based on the stratum of its peers.
Other clients on the same network ignore the stratum field and the GW2000 itself also ignored it, when running firmware 2.1.3.

[thunder.ky]

Are you using an ethernet connection or wifi?

Stuart

Hi Stuart,

I'm using WiFi.

[broadstairs]

It's just that my GW2000 is on ethernet and I have no issues with sensor reception. I wonder if it might cause problems if using WiFi.

Stuart

[Rover1822]

I have a ton of sensors, no issue with the GW2000 on WiFi

I have so many that if I just run rtl_433, without being specific on sensor, the screen just scrolls LOL

[broadstairs]

This is not the first report of iffy sensor reception on this new f/w using WiFi. Until someone proves the actual cause we're still guessing.

Stuart

[thunder.ky]

This is not the first report of iffy sensor reception on this new f/w using WiFi. Until someone proves the actual cause we're still guessing.

Stuart

I think I may switch to ethernet and see how it works; I've got an available switch port nearby.

[Gyvate]

not sure if I wrote this already earlier - I recommend to connect only via one of the interfaces either WLAN or LAN and keep the other one deactivated (which now possible with the last two firmware versions). Also, use/define a static address in the GW2000 rather than a MAC bound DHCP address by the router.

I have observed that when both interfaces are active and traffic is routed via both, the GW2000 network interfaces can get stuck and a reboot, power-cycle is required to make it work again.

[giusCB]

please report these problems to ecowitt. It is clear that there is something wrong with this new firmware.
 I personally had the biggest problems with the RF signal (in my case from a WH32) using the ethernet connection (also with wifi i experience some signal lost)

[Gyvate]

this thread with the discovered issues has been reported to Ecowitt
their reply:
"....We are looking into the problem, but we believe if people use only wifi or ethernet, it should be all ok.
Please give us some time."

[thunder.ky]

please report these problems to ecowitt. It is clear that there is something wrong with this new firmware.
 I personally had the biggest problems with the RF signal (in my case from a WH32) using the ethernet connection (also with wifi i experience some signal lost)

I've reported my experience to Ecowitt. Hopefully they are able to resolve something quickly.

[billybob]

Updated a couple of days ago. Had to reset because had a flashing red light on the unit after the gui showed update successful. I only use ethernet interface so don't know what the problem was during update but it came up fine after the reset. I have DHCP static reservation.

So far, it seems they have done something to the barometer pressure logic. It is not drifting as much compared to my GW1000.

As far as reception, I have WS80 as my main unit but still have the old boat WS1400 (WH24) a couple of hundred feet from my indoor unit. The reception of WS1400 was bad before but now seems rock solid. Maybe a coincidence but since other people were complaining about radio sensitivity, my experience has been opposite.

[giusCB]

can some of you try the gw2000 (with 2.2.4fw.) connected only via ethernet cable to the router? (with wlan off)
i'm experienced signal lost when the gw2000 is connected via ethernet 

[Gyvate]

can some of you try the gw2000 (with 2.2.4fw.) connected only via ethernet cable to the router? (with wlan off)
i'm experienced signal lost when the gw2000 is connected via ethernet 

I have two GW2000 FW 2.2.4 connected via ethernet (LAN cable) with no issues so far.

[broadstairs]

can some of you try the gw2000 (with 2.2.4fw.) connected only via ethernet cable to the router? (with wlan off)
i'm experienced signal lost when the gw2000 is connected via ethernet 

I also have one GW2000 with this f/w using only ethernet (wlan turned off) and have no seen any issues with signal loss of sensors.

Stuart

[giusCB]

many thanks for the feedback 

[olicat]

Hi!

Since the update to v2.2.4 (and also with the Beta v3.0.0) I now sometimes see that the WS90 is not sending data (or that the GW2000 does not see it or is not sending it). I monitor the reception of wh90batt in the Ecowitt protocol via custom server. And sometimes over several intervals (30 seconds) the wh90batt value is not sent by the GW2000.
The connection of the GW2000 here is via WIFI; the LAN port is not used. WIFI problems can be ruled out, as other data are sent by the GW2000.

It is not impossible that this behaviour has nothing to do with the firmware version update. But I did not have this with the firmware versions before.
But I am still at the beginning of my investigations ...

Oliver

[thunder.ky]

Since the update to v2.2.4 (and also with the Beta v3.0.0) I now sometimes see that the WS90 is not sending data (or that the GW2000 does not see it or is not sending it). I monitor the reception of wh90batt in the Ecowitt protocol via custom server. And sometimes over several intervals (30 seconds) the wh90batt value is not sent by the GW2000.
The connection of the GW2000 here is via WIFI; the LAN port is not used. WIFI problems can be ruled out, as other data are sent by the GW2000.

It is not impossible that this behaviour has nothing to do with the firmware version update. But I did not have this with the firmware versions before.
But I am still at the beginning of my investigations ...

This is same thing that alerted me to this behaviour, I started getting alerts that the wh90batt was not being received. I then started noticing intermittently that the GW2000 would not receive data from my WS90, my lightning sensor and/or one of my soil moisture sensors. As mentioned in a previous I did not have any issues with older firmware. I've exchanged a few e-mails with Ecowitt on the subject, and hoping for a solution.

[broadstairs]

I do wonder if the issue could be with a WS90 rather than the WS80 which I have and see no issues?

Stuart