Topic: GW3000 V1.0.9 firmware release

[Gyvate]

New Version:V1.0.9
- Support IoT device WFC02.
- Support custom NTP servers.
- Fix the issue of repeated restarts when there is no Internet connection.

[mcrossley]

I'm on v1.0.8.1 and it is not finding a new version?

Web UI and WSView+

[Gyvate]

mine came in on the WebUI - not on WSV+ - and only after active questioning. No red dot yet. It may take some time to get through

[broadstairs]

Mine has just updated OK, just slightly strange that on initially reloading the Web UI on live data only internal values showed up but after a short while everything appeared and is now running fine.

Stuart

[Paulcheffus]

Hi

My GW3000 has updated itself this morning 10:30 BST (09:30 UTC) but I don't have automatic updates enabled and I didn't perform the update.
Was previously at 1.0.8.1

Cheers

Paul

[mcrossley]

Mine has now updated via the web UI, but I notice the outdoor T/H no longer shows the transmitter id and "signal" just an antenna icon.

[Gyvate]

I think you mean WSV+ Live data - or the sensors ID page in the WebUI
my WH32 shows there with bars ...
Maybe you have to re-register it again with its sensorID - I assume you have a backup (screencopy, paper/digital notes) for that  .

[weatherbee]

Mine updated this morning on its own.  I don't have automatic updates enabled. First time it has done that.
Everything is working ok.
Tom

[olicat]

Hi!

To all users for whom the update was automatically installed even though automatic updates are deactivated:
From which firmware version did the update to v1.0.9 take place?

I still have v1.0.6 here, auto update disabled and an automatic update has not taken place (so far?).

Oliver

[Paulcheffus]

Hi!

To all users for whom the update was automatically installed even though automatic updates are deactivated:
From which firmware version did the update to v1.0.9 take place?

I still have v1.0.6 here and an automatic update has not taken place (so far?).

Oliver

Hi

Mentioned above mine was 1.0.8.1

Cheers

Paul

[OldAlaskaGuy]

Installed via auto update. All T&H sensors have signal strength indicators and ID. Although I am getting a notice of a data spike showing 0 hPa for low limit that is ongoing. Using a GW3000 to feed Cumulus and all pressure data looks good on Ecowitt. What error log should I post?

[Gyvate]

Mine has just updated OK, just slightly strange that on initially reloading the Web UI on live data only internal values showed up but after a short while everything appeared and is now running fine.

Stuart

that's normal as these are the first sensors it reads, no delay - whereas the others have to be newly "found" i.e. their next signal registered

[OldAlaskaGuy]

I have rebooted my GW3000 and the error notice of a data spike on CumulusMX that is ongoing showing 0 hPa for low limit. Ecowitt is reporting normal pressures 1013-1017 hPa. What log files do you need to see the issue?SOLVED  I had inadvertently ticked to let Cumulus calculate sea level pressure. Un-ticked and saved.

[broadstairs]

Mine has just updated OK, just slightly strange that on initially reloading the Web UI on live data only internal values showed up but after a short while everything appeared and is now running fine.

Stuart

that's normal as these are the first sensors it reads, no delay - whereas the others have to be newly "found" i.e. their next signal registered

Yes but I have a WS80 which send data fast and I've never before seen that it was definitely slow to display!

Stuart

[KC5JIM]

Mine auto-updated(auto updates enabled), and there have been no issues.

[weatherbee]

Mine auto updated from version 1.0.8.1.
Tom

[mcrossley]

I think you mean WSV+ Live data - or the sensors ID page in the WebUI
my WH32 shows there with bars ...
Maybe you have to re-register it again with its sensorID - I assume you have a backup (screencopy, paper/digital notes) for that  .

It's fixed itself, I just reopened the WSV+ app and the outdoor T/H now shows the sensor id and signal

[Rocketman]

My Gw3000 was on 1.0.6 updated manually to 1.0.9 ( all OK )

[Gyvate]

Ecowitt pushed a forced 1.0.9 upgrade to all 1.0.8.1 GW3000 gateways as the change with the reboots in 1.0.9 should have been already included.
Or, the other way around, 1.0.8.1 was in a way premature (a hot fix) but was released earlier to avoid custom server issues with WH45/46/46D owners
That was exceptional and only 1.0.8.1 gateways were affected.

[Dirk27]

Until now I've watched this "overriding" of the disabled automatical firmware update setting only two times:
This GW3000 update and the HP10 update to V1.1.0.

[zoomx]

Me too found 1.0.9 and I didn't have the automatic update so it was forced. I had  1.0.8.1

[CloudyDave]

Personally I'm very disturbed by this ability that allows for the pushing of an update when the device is configured for "NO AUTO UPDATE".  I consider this to be a critical security issue.  Has it not occured to anyone that if a rogue update was allowed to update your device with code that  monitors all of your network traffic, and send it to tim-buck-too, is not a good thing to allow under any circumstances.  I've been contemplating replacing my GW2000 with the newer GW3000 but with this discovery and the fact that this newer GW3000 version hangs when "NO INTERNET" connection (which appears to have been resolved) is available, is uncalled for.  Please educate me if you have a valid reason why this should be allowed so I can be enlightened.  This issue with the device hanging is probably the same design flaw or bug that requires me to perform a power off/on for the GW2000 on a daily basis in order to prevent the hangs that occurs with it!  Hopefully they will determine if it is the same issue and make an update available for the GW2000.  Note that I do not allow my GW2000 to have INTERNET access - only LAN.  The only time I allow internet access is when I wish to perform an update - at my discretion.  I can then monitor for problems / issues after I have allowed an update to  be performed.  Your thoughts.

[Vasco]

This issue with the device hanging is probably the same design flaw or bug that requires me to perform a power off/on for the GW2000 on a daily basis in order to prevent the hangs that occurs with it!  Hopefully they will determine if it is the same issue and make an update available for the GW2000.

I doubt it's a design flaw or bug - my GW2000 has been running for over a year without a hitch.

EDIT: It seems I was wrong. My apologies.

[CloudyDave]

If this an appropriate reply since I don't want to hijack this thread - I opened a new topic on my issue with the GW2000 since it's not directly related to the GW3000.
https://www.wxforum.net/index.php?topic=48715.0

[Gyvate]

see reply in your thread - the issue is being worked on by Ecowitt - and it obviously affects not only a GW3000 or GW2000 ...