Topic: new firmware for GW1000/WH2650 v1.7.3

[olicat]

Hi!

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

New Firmware GW1000V1.7.3:

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

The changelog is identical to v1.7.2 - only point 4 has been added.
I hope that the (rarely occurring) reboots will be fixed with this.

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

Regards, Oliver

[olicat]

Hi!

I have now installed the new version on my test GW1000.
There are no obvious problems and I don't see any changes so far (not even in the output format via custom server).
Now we have to wait and see whether the sporadic reboots continue.

Oliver

[broadstairs]

I have just installed it and will see what happens. With the reboots I'm not sure I'm seeing them or at least WD is not stopping at all gathering data so dont know if I get reboots or not WD has not apparently had any interrupts to data where it has disconnected for a few weeks now. Is there some way to detect these?

Stuart

[olicat]

Hi!

Is there some way to detect these?

Of course.
In each data row, the key runtime is supplied, which contains the number of seconds since the last start.
When I receive each line, I check whether the value for runtime is larger than the last reported value.
If this value is not larger (less or equal), there was a reboot.
My internal FOSHKplugin version reports this reboot via push message and logs the reboot in the log. The number of daily reboots is also logged in the daily CSV.

Oliver

[broadstairs]

Hi!

Is there some way to detect these?

Of course.
In each data row, the key runtime is supplied, which contains the number of seconds since the last start.
When I receive each line, I check whether the value for runtime is larger than the last reported value.
If this value is not larger (less or equal), there was a reboot.
My internal FOSHKplugin version reports this reboot via push message and logs the reboot in the log. The number of daily reboots is also logged in the daily CSV.

Oliver

OK so I guess this is only in the custom server data? I'll need to set something up to gather that and check it.

Stuart

[olicat]

Hi!

this is only in the custom server data?

Presumably, you can also retrieve the value via the API. But this is not documented in the (last) document v1.6.4 that I have.
Probably runtime also goes via Ecowitt protocol to Ecowitt.net - but yes - I use the custom server for these things.

I'll need to set something up to gather that and check it.

Shall I provide you with my internal FOSHKplugin version?

Oliver

[broadstairs]

Hi!

this is only in the custom server data?

Presumably, you can also retrieve the value via the API. But this is not documented in the (last) document v1.6.4 that I have.
Probably runtime also goes via Ecowitt protocol to Ecowitt.net - but yes - I use the custom server for these things.

I'll need to set something up to gather that and check it.

Shall I provide you with my internal FOSHKplugin version?

Oliver

Well I just realised I could use your EAR to get an initial view, turn it off for a few hours and enable it again and see what the value is. That way I can see initially if I have a problem.

Yes if you wouldn't mind please your internal FOSHKplugin would be useful.

Stuart

[Rover1822]

Item #4 Event display bug. Well it cleared mine which had been additive, now reads 0. Be aware if you have valid event data, like it rained very recently (I had rain this morning) the value will be reset to 0 after the update.  Not a bug, probably part of the fix.

[Daali]

I have 3 units, all were at 1.7.2. 

All 3 updated "successfully" to 1.7.3

2/3 were perfect upgrades
1/3 had the Default AP SSID broadcasting(could not connect) while working after update.  logging into ws_view and "configure router" - > save, stopped the broadcasting of the SSID.