Cumulus Support

I have an installation as depicted in my hand made drawing (see scan attached, note that the upper website nr 2 must be website nr 1). The issue is that at 9h31 today the wind and T/H sensor of the WS80 (which I use as main T/H sensor as well) went haywire on one of my GW1100. This is shown in the two images of Ecowitt.net attached as well. Important to realise that both GW1100's are attached to the same WS80 device.

My conclusion is that it is the GW1100 firmware reading the WS80 which has a bug somewhere, probably in the difference between the WS80 and WS90 (what kind of sensor is this??? it is not on the Ecowitt.comm shop site). Both GW1100's have the same firmware : GW1100A_V2.0.9 which is automatically installed (I don't know when, the installation itself might be the issue).

Anyway, when I concluded the GW1100 was the problem, I rebooted and the problem went away.
I sent a link of this message to Ecowitt Support and posted it on WXforum.net.

I guess you mean the battery status.
This will probably need to be corrected in the firmware of the GW1100.
It's the only one console so far (except the GW2000) which is able to identify a WS90 at all.
However, regarding your post in wxforum.net, be aware that people from the wxforum.net CANNOT see your pictures unless the are CMX forum members.
What's your firmware release ?
I am still on 2.0.8 and it doesn't show on mine even though I also have a WH65/WS69 and WS80 outdoor array.

Gyvate wrote: ↑Fri 31 Dec 2021 3:41 pm I guess you mean the battery status.
This will probably need to be corrected in the firmware of the GW1100.
It's the only one console so far (except the GW2000) which is able to identify a WS90 at all.
However, regarding your post in wxforum.net, be aware that people from the wxforum.net CANNOT see your pictures unless the are CMX forum members.
What's your firmware release ?
I am still on 2.0.8 and it doesn't show on mine even though I also have a WH65/WS69 and WS80 outdoor array.

Look good: its temp, hum and wind all wrong in one GW1100 and correct in the other.
And note: there is no WS90 present at all, I don't even know the device.

I was referring to the visible WS90 value.
If the wrong data of your 2nd GW1100 are related to that, is a second question.
Your normal GW1100 doesn't report a WS90 battery status.
Looks like you rebooted the wrongly reporting GW1100 and issue solved ...
A factory reset wasn't done.
Issues can come from the location of the GW1100 and interference with other EM devices.
The connection of the power supply (direct, extension cable) and the quality of the extension cord may play a role.
Or it went just nuts as computer device sometimes do ....

Gyvate wrote: ↑Fri 31 Dec 2021 4:26 pm I was referring to the visible WS90 value.
If the wrong data of your 2nd GW1100 are related to that, is a second question.
Your normal GW1100 doesn't report a WS90 battery status.
Looks like you rebooted the wrongly reporting GW1100 and issue solved ...
A factory reset wasn't done.
Issues can come from the location of the GW1100 and interference with other EM devices.
The connection of the power supply (direct, extension cable) and the quality of the extension cord may play a role.
Or it went just nuts as computer device sometimes do ....

Well, up to ecowitt to solve it and anyway, i understand perfectly well bugs may exist or hardware may fail or have errors for multiple reasons but afaics it is an error in the firmware which must detect and catch erroneous data transmissions (if those are the cause)

Remember that the previous error i reported was similar to this one. If it continues to go on like this it means that I have to correct errors in CMX every month. That is a tedious task. i may have to to maybe once per year but every month will inevitably lead to this being my last ecowitt as regular meteo station. It must be more reliable than this.

Gyvate wrote: ↑Fri 31 Dec 2021 4:26 pm Issues can come from the location of the GW1100 and interference with other EM devices.
The connection of the power supply (direct, extension cable) and the quality of the extension cord may play a role.

The WS80 is 40 meter away from the GW1100 and running on batteries, no cables at all.

HansR wrote: ↑Fri 31 Dec 2021 5:05 pm

Gyvate wrote: ↑Fri 31 Dec 2021 4:26 pm Issues can come from the location of the GW1100 and interference with other EM devices.
The connection of the power supply (direct, extension cable) and the quality of the extension cord may play a role.

The WS80 is 40 meter away from the GW1100 and running on batteries, no cables at all.

I was referring to the GW1100, to the console, not to the sensors.
And the GW1100 has a USB power plug and comes with an extension cord.
There had been multiple issues over the past years with the GW1000 and also with the GW1100
where the location - and the connection [cable] - played a significant role.
Changing the location and exchanging the cable solved the issues many times.

After several mail exchanges with Ecowitt with some misunderstandings, they advised me:

1. To use WsView Plus (so I installed it beside plain WsView)
2. And in WsView Plus in the Sensors ID list the top one is WS90
3. Disable WS90 ( )

So I presume it is a current firmware problem when both WS80 and WS90 are enabled and 'learning'.
We'll see what this brings.
Other explanation with this instruction is minimal.

And in addition:

1. Yes, Ecowitt claims this solves the issue
2. I agreed a max of two month before concluding a fix.
3. And who knows, maybe it is better to disable all unused sensorID entries (it avoids at least the permanent learning which no doubt takes valuable value reading time). I will do that anyway.

HansR wrote: ↑Sat 08 Jan 2022 9:40 am And in addition:

1. Yes, Ecowitt claims this solves the issue
2. I agreed a max of two month before concluding a fix.
3. And who knows, maybe it is better to disable all unused sensorID entries (it avoids at least the permanent learning which no doubt takes valuable value reading time). I will do that anyway.

see https://www.wxforum.net/index.php?topic ... #msg420959 red highlighted paragraph towards the end of the HP2551 console post

@Gyvate: Ah you just edited... good addition.

NOTE: the issue does not seem to be resolved by disabling all sensors not used.
Check out this observation.