Topic: GW1000 locking up and requires power cycle!

[broadstairs]

I have had an issue with my GW1000 seemingly locking up which required a power cycle to recover. I could not access it via the APP and the custom server had stopped although I could ping it on the lan so wifi was connected. Has anyone else here seen this kind of behavior and managed to find out the cause? Nothing has changed on my lan or router etc.

Stuart

[gszlag]

I have had an issue with my GW1000 seemingly locking up which required a power cycle to recover. I could not access it via the APP and the custom server had stopped although I could ping it on the lan so wifi was connected. Has anyone else here seen this kind of behavior and managed to find out the cause? Nothing has changed on my lan or router etc.

Stuart

Yup..exactly happens with my GW100 about every week or so..it just stops. Pull the thing out of the electrical outlet for several seconds, plug it back in..works perfectly for another week. I am considering buying a replacement or putting it it on a timer that will automatically "reboot" every so often.

[broadstairs]

May I ask if you use software to process the data and if so which one?

Stuart

[gszlag]

May I ask if you use software to process the data and if so which one?

Stuart

WeeWX and CumulusMX

Should also mention that the IP of the GW1000 is reserved in the router.

When the GW1000 fails, WeeWX shows N/A in the sidebar items (default Seasons skin) and CumulsMX just stops updating. Additionally the custom server upload to pwsdashboard website stops so this seems to suggest it is not a software issue but perhaps a hardware issue with the device.

The GW1000 is only about 3 meters from the router - I have tried a few different locations for the GW1000 with the same results. Installing a USB extention to keep the power supply away from the GW1000 was an absolute must in my case.

[Rover1822]

There is an issue if you are running dual band under the same SSID where this may happen. (2.4 and 5 GHz)
I have a router used as an AP that just doesn't get along with my GW1000s

[gszlag]

There is an issue if you are running dual band under the same SSID where this may happen. (2.4 and 5 GHz)
I have a router used as an AP that just doesn't get along with my GW1000s

Thanks for the tip. My router was replaced by the ISP just a couple months ago with the exact same model. DHCP had gone brain dead. Rather than updating firmware they just replaced it. Long story short - the old router had the same SSID for both bands but the replacement router has different SSIDs so in my case, the replacement router did not fix the issue. Could be this router just doesn't like my GW1000.

[broadstairs]

I still fail to see why the GW1000 has issues if 5ghz is enabled since it cannot 'see' the 5ghz network. Different if steering is enabled where your access point attempts to move connection to 5ghz but at least on my mesh network I have that turned off for the GW1000. I suspect there is some sloppy coding gone on in the GW1000 and probably the GW1100 if it also behaves badly. If you use either a router or mesh system which does steering (or whatever they call it on your h/w) it must be turned off for the GW1*00 hardware.


At least for my hang up I suspect my software being used may have an issue with error recovery if some network issue happens and it loses connection. I know you can cause such problems  as I managed it when testing some code I was writing to gather data 

Stuart

[plunet]

Just thinking out loud here.... there's obviously a lot of us that have no issues with a GW1000, but it's interesting that there are at least two members that are seeing this issue.

It might be hardware, but I would probably wager it's more likely to be software.

• What is the status of the LEDs on the GW1000 when it locks up? Do you see the RF LED blink from time to time?
• Can you ping the GW1000's IP address when it's locked up?
• Do you have anything "interesting" on your local LAN that creates a lot of broadcast traffic?
• Are you using anything that requires Multicast on your local LAN?
• What version of firmware is the GW1000 running.
• How long has the locking up issue been going on for?
• Any recent changes (add sensors, or changes to GW1000 config) since you think it started to lock up?
• One of you mentioned that it locks up "every week or so" - do you have more precise timings for the length of time it will run before it locks up (you might be able to get this from Ecowitt graphs)

[/li]
[/list]

[giusCB]

Same problem for me!!

[Rover1822]

Same problem for me!!

Please post as much of the conditions, your network setup, the power supply in use etc. As many factors as you can think of.

Would be informative and may help others

I have 4 at the house GW1000s and a GW1100... absolutely not a single issue yet and I have had them a while (the GW1000s) .
Have another at my office, also no issues.
Have set up a few neighbors , and they haven't had issues

At the house I run 3 APs (not mesh, APs are hardwired to a primary Asus router)  , separated SSIDs . All of my routers are ASUS (different models) , although I have one AC1300 model that had issues with the GW1000, but it also had issues with a couple of security cameras so I blame the router (or my configuration of that AP) in that case.

All of the above is not meant to discount those that have issues, as it is evident they exist.

Also all of mine are plugged into decent UPS systems

[giusCB]

nothing special, my gw1100 are with 5v power supply connected with a 2.4ghz router, after some weeks they don't upload their data on ecowitt cloud with red led light blinking.

[gszlag]

Just thinking out loud here.... there's obviously a lot of us that have no issues with a GW1000, but it's interesting that there are at least two members that are seeing this issue.

It might be hardware, but I would probably wager it's more likely to be software.

• What is the status of the LEDs on the GW1000 when it locks up? Do you see the RF LED blink from time to time?
• Can you ping the GW1000's IP address when it's locked up?
• Do you have anything "interesting" on your local LAN that creates a lot of broadcast traffic?
• Are you using anything that requires Multicast on your local LAN?
• What version of firmware is the GW1000 running.
• How long has the locking up issue been going on for?
• Any recent changes (add sensors, or changes to GW1000 config) since you think it started to lock up?
• One of you mentioned that it locks up "every week or so" - do you have more precise timings for the length of time it will run before it locks up (you might be able to get this from Ecowitt graphs)

[/li]
[/list]

Lockups are random..anything more than a week it will go down. Best stretch may have been 2 weeks. I use the Nirsoft wireless watcher occasionally to see what all the connected devices are doing. The GW1000 will "disappear". Unplugging and plugging it back in causes the router to rediscover the device. WeeWX is on a rpi. Sometimes CMX and WeeWX needs a reboot after power cycling the GW1000.

The GW1000 was problematic right out of the box and would "crash" several times a day. Putting in the USB extention helped big time and the GW1000 is currently about 30 cm away from the power supply.

This home network is just a simple network - just the garden variety of computers tablets, TV, TV box, soundbar.,Ambient WS-2000 console etc. Nothing exciting here unless you call an ooma phone exciting. Should not be any excessive broadcast traffic.

The GW1000 is an awkward spot so I can't see the lights easily but when it goes down next time, I'll pull it out and take a look. Latest firmware 1.6.8.
Multicast? Don't think so.

I've just started rebooting the GW1000 device in WSview just to see if it will make any difference.

[Rover1822]

have you tried a different power supply?

[gszlag]

have you tried a different power supply?

Yup - tried that too - tried 2 of them  - ASUS chargers..

[Rover1822]

Hmm, try another brand?... Of course this is not an answer.

Although I really like the GW1000s , they do have limitations. A lot of USB PSUs  are meant for charging a device that has a battery, in that case they work great. But the GW1000 is not a battery device. Interruptions on power delivery to a GW1000 will cause a restart, a couple in short order may interrupt the boot up and who knows what happens. I see this with PCs and other items not on good UPS, or power supply. 

I do not plug in the GW1000s into a device that has a USB port, by that I mean,I use dedicated plug in adapters to line voltage/power , a wall adapter. All these devices , routers, PCs, etc with USB , will tend to control the USB in some aspect and are subject to the operation of the primary device. That is why I use adapters straight to the wall for USB power , or off a UPS

I am not saying this is your issue, or anyone's, just little things.

[gszlag]

Hmm, try another brand?... Of course this is not an answer.

Although I really like the GW1000s , they do have limitations. A lot of USB PSUs  are meant for charging a device that has a battery, in that case they work great. But the GW1000 is not a battery device. Interruptions on power delivery to a GW1000 will cause a restart, a couple in short order may interrupt the boot up and who knows what happens. I see this with PCs and other items not on good UPS, or power supply. 

I do not plug in the GW1000s into a device that has a USB port, by that I mean, use dedicated plug in adapters to line voltage/power , a wall adapter. All these devices , routers, PCs, etc with USB , will tend to control the USB in some aspect and are subject to the operation of the primary device. That is why I use adapters straight to the wall for USB , or off a UPS

I am not saying this is your issue, or anyone's, just little things.

Yeah..options are getting a bit thin at this point. I like to refer to these kind of events as "solar flare" events

[plunet]

Just thinking out loud here.... there's obviously a lot of us that have no issues with a GW1000, but it's interesting that there are at least two members that are seeing this issue.

It might be hardware, but I would probably wager it's more likely to be software.

• What is the status of the LEDs on the GW1000 when it locks up? Do you see the RF LED blink from time to time?
• Can you ping the GW1000's IP address when it's locked up?
• Do you have anything "interesting" on your local LAN that creates a lot of broadcast traffic?
• Are you using anything that requires Multicast on your local LAN?
• What version of firmware is the GW1000 running.
• How long has the locking up issue been going on for?
• Any recent changes (add sensors, or changes to GW1000 config) since you think it started to lock up?
• One of you mentioned that it locks up "every week or so" - do you have more precise timings for the length of time it will run before it locks up (you might be able to get this from Ecowitt graphs)

[/li]
[/list]

Lockups are random..anything more than a week it will go down. Best stretch may have been 2 weeks. I use the Nirsoft wireless watcher occasionally to see what all the connected devices are doing. The GW1000 will "disappear". Unplugging and plugging it back in causes the router to rediscover the device. WeeWX is on a rpi. Sometimes CMX and WeeWX needs a reboot after power cycling the GW1000.

The GW1000 was problematic right out of the box and would "crash" several times a day. Putting in the USB extention helped big time and the GW1000 is currently about 30 cm away from the power supply.

This home network is just a simple network - just the garden variety of computers tablets, TV, TV box, soundbar.,Ambient WS-2000 console etc. Nothing exciting here unless you call an ooma phone exciting. Should not be any excessive broadcast traffic.

The GW1000 is an awkward spot so I can't see the lights easily but when it goes down next time, I'll pull it out and take a look. Latest firmware 1.6.8.
Multicast? Don't think so.

I've just started rebooting the GW1000 device in WSview just to see if it will make any difference.

If you can see that the GW1000 has disappeared off the network from something independant like the Nirsoft tool you have been using then that is a fairly good indication that it's given up at Layer1 (ie. it's dropped the Wifi association with your router). Especially as the GW1000 will be trying to upload data regularly to the APIs so it would be unusual for it to go to "sleep" and disappear out of the MAC (layer 2) or ARP (layer 3) tables on devices.

My comments around broadcast traffic and multicast is that the network stacks of embedded devices can be intolerant of batting off excessive amounts of broadcast or multicast traffic. That's not to say that the GW1000 would suffer from this - but if you know your way around network packets and can cope with Wireshark, maybe just a quick look at what is floating around your LAN using wireshark and that there's not loads of broadcast or multicast floating around would be useful. If there is any multicast and your router has an IGMP option, turn it on! In fact, turning on IGMP in most domestic situations would rarely cause any problem, but could prevent unintended consequences with maurading multicast. Bonjour used by apple products and mDNS are the usual suspects you migth see domestically and generally don't cause any problems as they are low bandwidth.

If its been a problem child GW1000 since day one maybe the writing is on the wall, but observing the status of all the LEDs on the GW1000 before you next power cycle it wouldn't be a complete waste of time.

[broadstairs]

In my case the GW1000 has been reasonably stable. Recently it had an issue and stopped responding to WDs crongw1000.exe which showed an 8 digit number (I think) in it's left side panel and had not responded after that apparently this happened around 0730 in the morning. Now I suspect crongw1000 may have tried to recover from an error but badly and cause the GW1000 to lock its socket and fail to connect at all to repeated requests. I know from experience this can happen as I said when I was testing my own code and managed to lock it out. I must point out that my code only runs 4 times per day at 0101,0801,1301 and 1901 hours to extract battery data, so had nothing to do with the GW1000 locking at around 0730. I do not have many devices on my lan especially at that hour of the day and nothing which causes any significant amount of network traffic. I have now gone back to V5.3 of crongw1000.exe from V5.5which was running at the time and so far no further occurrence.

Stuart

[Platokidd]

I have 3 gw1000's and 1 gw1100. All of them have had issues at one time or another locking up and / or not working. Adding a 3 foot usb extension cord and moving the gw's location fixed my issues.

[broadstairs]

I have my GW1000 on an extension cord and has been for a few weeks now and it is about 4-5 feet from the access point. To be honest in my case I am fairly convinced that the lock up is caused by software error recovery not doing the right thing to recover following an error on the lan and causing the lock up problem is trying to trace it since it happens very infrequently.

Stuart

[Gyvate]

My GW1000s (3), WH2650s (2) have been working for months now without any issue.
Only my new GW1100 had an issue the other day (of course just when I was away for a couple of days  ):
it stopped sending data to ecowitt.net, strangely enough it continued posting data via the customized server function.
And I couldn't connect anymore via the WebUI.
When I was back home, the WSView app also failed to connect.
The red LED was on constantly, no occasional blinking as my other GW1000s do.
My router would still show its IP as connected - when I disconnected the GW1100 power supply, it disappeared from the router (to be expected).
So I did a reset - no change in symptoms. I tried a factory reset, but nothing would happen - neither with pressing the middle button nor by using a staple end on the backside.
Pressing the reset button > 5 seconds would results in 3 blinks of the red LED, then all went out and it restarted - still the red LED not blinking.
I simply didn't get a factory reset working which would result in a fast blinking LED, no matter how long I held the reset button, entered a staple pin into the reset hole, powered it off for a longer time. 
However, after a few restarts, the router recognized the "old" IP again, the WSView app connected and the WebUI could be reached again - and it (the GW1100) sent data again.
All still the same (old) IP address (MAC bound).
Still the red LED remains only on constant light and a factory reset is impossible.
I'm wondering if I should complain with Ecowitt as it now continues doing its job ...

[Rover1822]

Still the red LED remains only on constant light and a factory reset is impossible.

Unlike my GW1000s, my GW1100 red LED is always solid on. I just checked Ecowitt.net and looked at the history graphs and I haven't had a drop out, this is the only place that unit uploads.
I haven't tried a factory reset as I haven't had a reason to.

[broadstairs]

I can confirm my GW1100 (not used live) red led is on solid.

Stuart

[olicat]

Hi!

my GW1100 (not used live) red led is on solid.

... same here ...

Oliver

[Rover1822]

I'm going to make the assumption this is by design. Why have it different than the GW1000?, no idea