Topic: new firmware version for GW1100/GW2000: V2.1.9

[olicat]

Hi!

There's a new firmware version V2.1.9 available for the GW1100 and GW2000.

Use the current WSView Plus app or the web interface of the GW1100/GW2000 ("Device Setting") to update.

Changelog for V2.1.9:
1.Optimize exception handling of RF reception
2.Fix some display problems
3.Supports the upload of leaf moisture sensor data

Oliver

[Gyvate]

I think the following is worth to be noted:

3.Supports the upload of leaf moisture sensor data is meant for the WH2682 mode of the GW2000 - the GW2000 in its normal "edition" could already upload WN35 data earlier.
the WH2682 as a physical console/gateway is the Ambient ObserverIP 2.0 - it will show this name (WH2682) in its WebUI

However, a GW1100 and GW2000 can also be put into the WH2682 mode if the wires for the internal T/H sensors are removed 
the WebUI of a GW1100/GW2000 and a WH2682/ObserverIP2.0 is the same - with the difference that a real ObserverIP2.0 can only display all available Ambient sensors and not all Ecowitt sensors.
A GW1100/GW2000 in WH2682 mode however can display of course all Ecowitt and Ambient sensors.

[broadstairs]

Just installed this and will see how it goes. All OK so far. Interesting about the RF reception as I reported my problem to Ecowitt where I was occasionally missing a rain tip on the GW1100, although it also happened on the GW1000 so wonder if that will get an update as well.

Stuart

[Gyvate]

I have often a 0.1 mm rain tip difference between my HP2550 console and my WN1910 console (GW1000 API) - and it shifts between the two ...

[mcrossley]

I still think the rain discrepancies are rounding errors in the Ecowitt code rather than anything else. One receiver could miss transmissions for a whole day and the counts should still match once it does receive a message.

[broadstairs]

Yes but the issue is that it misses a single tip but continues to receive all the other tips and never corrects.

Stuart

[giusCB]

" exception handling " What does this mean ?

[mcrossley]

Yes but the issue is that it misses a single tip but continues to receive all the other tips and never corrects.

My point is because of the way they work they cannot miss a tip. They may miss transmissions but the tips are not lost.

[Gyvate]

" exception handling " What does this mean ?

I guess it means situations where there are issues (e.g. connection drops) with the connection between console and sensors - how this is handled.
Usually, in a programming context, exception handling means dealing with situations which are outside the "normal", usual and expected during proper functioning.
Such an exception may be the loss of the RF connection (in the sense that no packets or no processable packets are received in a certain period of time).

[kheller2]

I think the following is worth to be noted:

3.Supports the upload of leaf moisture sensor data is meant for the WH2682 mode of the GW2000 - the GW2000 in its normal "edition" could already upload WN35 data earlier.
the WH2682 as a physical console/gateway is the Ambient ObserverIP 2.0 - it will show this name (WH2682) in its WebUI

However, a GW1100 and GW2000 can also be put into the WH2682 mode if the wires for the internal T/H sensors are removed 
the WebUI of a GW1100/GW2000 and a WH2682/ObserverIP2.0 is the same - with the difference that a real ObserverIP2.0 can only display all available Ambient sensors and not all Ecowitt sensors.
A GW1100/GW2000 in WH2682 mode however can display of course all Ecowitt and Ambient sensors.

So this sort of implies Ambient will be getting leaf moisture sensors?
And ... are you saying that the unit behaves differently if you remove the T/H sensors and "becomes" a WH2682 that then needs a WH32B for T/H?

[Gyvate]

I think the following is worth to be noted:

3.Supports the upload of leaf moisture sensor data is meant for the WH2682 mode of the GW2000 - the GW2000 in its normal "edition" could already upload WN35 data earlier.
the WH2682 as a physical console/gateway is the Ambient ObserverIP 2.0 - it will show this name (WH2682) in its WebUI

However, a GW1100 and GW2000 can also be put into the WH2682 mode if the wires for the internal T/H sensors are removed 
the WebUI of a GW1100/GW2000 and a WH2682/ObserverIP2.0 is the same - with the difference that a real ObserverIP2.0 can only display all available Ambient sensors and not all Ecowitt sensors.
A GW1100/GW2000 in WH2682 mode however can display of course all Ecowitt and Ambient sensors.

So this sort of implies Ambient will be getting leaf moisture sensors?
And ... are you saying that the unit behaves differently if you remove the T/H sensors and "becomes" a WH2682 that then needs a WH32B for T/H?

If you remove the T/H sensor from a GW1100 or GW2000, it becomes a functional WH2682, the firmware switches into WH2682 mode, and it will need/be able to connect a WH32B - correct
The WH32B will override the internal pressure sensor.

The fact that the WH2682/ObserverIP 2.0 now supports the upload of Leaf Wetness sensors most likely means that Ambient will soon come up with a WH31something for their WN35. I don't think Ecowitt implemented that just for people who remove the T/H sensor from a GW1100/GW2000 ... - which average user would have that knowledge and apply it ...

[hiljo]

Is it possible to disable the immediate upload after a lightning strike somewhere? Does anyone know? Thanks!

[Gyvate]

Is it possible to disable the immediate upload after a lightning strike somewhere? Does anyone know? Thanks!

As far as I know it is hardcoded in the WiFi firmware. No selectable option.
Why would you want to disable the immediate upload ?

[hiljo]

My custom upload cannot handle a lot of uploads at a short interval. I've set it now at every 5 minutes. So if there are more uploads then once a every 5 minutes, my calculations go wrong 

[Autofill]

Interesting. My GW2000 is still on 2.1.8 and says that is the latest version. Hmmm..

Auto update is enabled.

[Gyvate]

Interesting. My GW2000 is still on 2.1.8 and says that is the latest version. Hmmm..
Auto update is enabled.

maybe you need to refresh the interface - "logout" (call IP address only in the browser)/login
and then check manually for firmware upgrade