Topic: new firmware for GW1000/WH2650 v1.7.2

[olicat]

Hi!

A new firmware for the GW1000/WH2650 is now available:

New Firmware GW1000V1.7.2:

• Fix the bug of abnormal startup of the system.
• Fix Wunderground upload bug.
• Support WS90 related data reception, calibration and upload.

Use - as usual - the app WS View or WSView Plus to update!

Regards, Oliver

[Rover1822]

I know Oliver and I and others are staring at logs looking for a reboot
Only been 8 hours here but nothing, but that means nothing

[mfc]

Same here
I'm beyond ten hours now, and carefully optimistic 

[Daali]

How's the stability so far?

[olicat]

Hi!

How's the stability so far?

Better.
But the real problem was not completely fixed.
I had a reboot today 06:03:43 after a runtime of 106061 seconds again.

Has anyone else noticed an unexpected reboot with v1.7.2?
Rover?

Oliver

[mfc]

My bootloop issue seems to be gone. Also, on my end no unexpected reboot so far.

[alfmk]

Hi

Has anyone else noticed an unexpected reboot with v1.7.2?

I had a reboot last night at 23:03:43 after a runtime of 302758 seconds

Alf

[Rover1822]

Has something changed on how the rain "event" totals are being calculated? On my GW1000, regardless of sensor (WH40, WH65,Wittboy) the GW1000s are reporting significantly higher rain event "totals" when compared to the other consoles (WS2000,GW1100,GW2000), which all agree, and make sense. This can be seen in WSView plus and on Ecowitt.net

I had a significant rainfall yesterday, ending before midnight. Around an inch ,example for the event, the wittboy reported 0.98 inch, the GW1000 reported 1.41 inch. Same kind of differences for the other rain sensors (with different values of course).

There is no calibration difference for all the rain sensors on the consoles, all are running defaults and gains of "1"

Also doesn't appear to be a way to change the units in WSview plus for the GW1000 under "more", where as you can for the GW1100 , etc.

Have I missed something somewhere?

Edit : I downloaded the data from Ecowitt.net, and it appears the "event" totals never reset for the GW1000, as they do for the other consoles (I take that back I found 1 reset on the totals). But it is still weird
Edit 2 : My uptime since upgrading to 1.7.2 on the GW1000s is 702542 , there have been no reboots

[Dador]

Hi,
I wanted to report a bug. Perhaps it is related to the new update, because before, when I was using 1.6.7 at 100%, this was not a problem. Well, currently I have WiFi GW1000 visible all the time. I guess after going through the connection process, that wifi should be gone. Additionally, it is always on the channel of one of the routers (I have 2). I can't turn it off, nor do I know where to do it. Suggestions?

[Rover1822]

I had this happen under 1.6.9

See post https://www.wxforum.net/index.php?topic=43812.msg446119#msg446119

I basically fixed by doing the following

Interesting, Put the GW1000 into configuration mode, connected to the GW1000 AP, and in WSView went through the add new device , reconfigured the SSID and password, saved.

After 5 minutes the Access point shutoff

repeated process for the other 2, now all 3 are not showing up as APs (Hotspots)

[Dador]

@Rover1822

Thanks for the direction. Problem solved.

I've done a few reboots of GW1000 before, but that didn't help. I finally found the cause. I used this method and it worked.

Hold the black button on the gateway for 10 seconds till the red wifi light and the blue RF light flash at the same time for three times. Then release it.

Before that, I only held the reset for 5 seconds (as it says in WS Viev app) and it had no effect. The AP GW1000 actually faded after about 5 minutes

[Rover1822]

@Rover1822

Thanks for the direction. Problem solved.

I've done a few reboots of GW1000 before, but that didn't help. I finally found the cause. I used this method and it worked.

Hold the black button on the gateway for 10 seconds till the red wifi light and the blue RF light flash at the same time for three times. Then release it.

Before that, I only held the reset for 5 seconds (as it says in WS Viev app) and it had no effect. The AP GW1000 actually faded after about 5 minutes

Be careful with the 10 seconds as that is supposed to be a factory reset of the GW1000


per the manual:

"Hold the black button for about 10 seconds till the red light and blue light flash simultaneously for three times will reset the gateway to factory settings. The history data, WiFi settings, calibration etc. will be all lost and need to be setup again via WS View app."

[Rover1822]

@Rover1822

Thanks for the direction. Problem solved.

I've done a few reboots of GW1000 before, but that didn't help. I finally found the cause. I used this method and it worked.

Hold the black button on the gateway for 10 seconds till the red wifi light and the blue RF light flash at the same time for three times. Then release it.

Before that, I only held the reset for 5 seconds (as it says in WS Viev app) and it had no effect. The AP GW1000 actually faded after about 5 minutes

Be careful with the 10 seconds as that is supposed to be a factory reset of the GW1000


per the manual:

"Hold the black button for about 10 seconds till the red light and blue light flash simultaneously for three times will reset the gateway to factory settings. The history data, WiFi settings, calibration etc. will be all lost and need to be setup again via WS View app."


The 5 seconds is to get into configuration mode, without resetting the unit

[Dador]

As I mentioned, I did the first restarts for these 5s, until the first flashes of the LEDs. Even so, I was losing all settings, such as offsets, which had to be reset later.

In my case, whether 5s or 10s, I had the same results for the sensors, i.e. I was losing settings. However, 10s only solved the problem with AccesPoint.

[olicat]

Hi!

I continued to have occasional reboots even with v1.7.2 (once each in the last two days).
Hopefully this has now been fixed with the new firmware v1.7.3.
I am lying in wait ...

Oliver

[Dador]

Huh,

My joy was premature. Today I look and the AP GW1000 is still visible. I have no idea what makes it turn on by itself  .

Also, I'm starting to wait for an update.

[olicat]

Hi!

I have no idea what makes it turn on by itself

You should look at the runtime of the unit and log it if necessary.
I would expect the AP mode to be activated every time the device is started. However, with the "more modern" devices such as GW1100 and GW2000, the AP mode is switched off approx. 5 minutes after start-up. Perhaps there's a bug in the current firmware of the GW1000 or it works differently.

I'm starting to wait for an update

You don't have to wait long.
However, the changelog does not say whether the AP problem has been solved.
My GW1000 does not show any open AP here - but the last reboot was also longer than 5 minutes ago.

Oliver

[Dador]

There is clearly something wrong with the WIFI. Currently, every time the router resets, the GW1000 loses communication and turns on the AccesPoint, which it does not turn off after configuration. I think something got mixed up with the software.

Is it possible to downgrade the software? The last stable version is 1.6.9.

[olicat]

Hi!

I think something got mixed up with the software.

Are you still at v1.7.2 or at v1.7.3 already?
Both GW1000s with firmware v1.7.3 here are absolutely stable.
No reboots for more than 5 days; no AP networks, no abnormalities.

Oliver

[Dador]

Are you still at v1.7.2 or at v1.7.3 already?
Both GW1000s with firmware v1.7.3 here are absolutely stable.
No reboots for more than 5 days; no AP networks, no abnormalities.

Oliver

Yes, I have version 1.7.3. I always update to the latest version, use WS View every day. Unfortunately, the update did not help me. Do you know if it is possible to download software packages somewhere from the Ecowitt server? Really, in 1.6.X I never had some of these problems as of now.

[broadstairs]

There is clearly something wrong with the WIFI. Currently, every time the router resets, the GW1000 loses communication and turns on the AccesPoint, which it does not turn off after configuration. I think something got mixed up with the software.

Is it possible to downgrade the software? The last stable version is 1.6.9.

I too do not have any issues with the latest f/w. I am puzzled by your statement that your router resets - why? My router runs 24x7 unless we have a power cut or I reboot it.

Stuart

[olicat]

Hi!

Do you know if it is possible to download software packages somewhere from the Ecowitt server? Really, in 1.6.X I never had some of these problems as of now.

At least I know there was a possibility to downgrade a firmware version.
However, this app was never released by Ecowitt for the general public and unfortunately only functions to a limited extent today.
I assume that there is now a more advanced solution from Ecowitt - but I don't know.
You should ask Ecowitt regarding your problems and possible solutions.

Regards, Oliver

[Dador]

Sometimes I have to reset the router because it just freezes connections with some devices.
Currently, after each reset of the router, the GW1000 enables the AP and does not disable it. Found a way to remove this manually. I need to manually restart the GW1000 gateway in the WS View application. Then the AP turns off.
However, it is troublesome and cumbersome.
There are posts on the forum where others also complain about Wifi working after updates. There must be something wrong with the software.

[Rover1822]

Have you tried using a static IP for the device (reserving it on the router)?

Sometimes I have to reset the router because it just freezes connections with some devices.

So you have other devices that also have issues?

[Dador]

Have you tried using a static IP for the device (reserving it on the router)?

All my devices are assigned a static fixed IP.

So you have other devices that also have issues?

I have 2 routers and about 12 internet devices, of which 6 devices use wifi. Sometimes one router loses the wifi connection, hence the need for a restart. But it was happening all the time, and I have had problems with the AP GW1000 for a short time, basically from version 1.7.x.