Cumulus Support

I've just started having GW1100 problems over the last few days. Before I contact Ecowitt, please am I doing anything wrong? I wasn't running auto discovery but it's been fine for months. I changed that to see if it made any difference, also rebooted the GW1100. File extract attached, grateful for any help thank you.


2022-04-26 18:07:36.374 Rain counter set to = 166.2
2022-04-26 18:07:36.378 Getting rain totals, rain season start = 1
2022-04-26 18:07:36.378 Today = 26/04/22
2022-04-26 18:07:36.401 Rainthismonth from dayfile: 17.3
2022-04-26 18:07:36.401 Rainthisyear from dayfile: 166.2
2022-04-26 18:07:36.413 Running GW-1000 auto-discovery...
2022-04-26 18:07:36.484 Using local IP address 192.168.1.122 to discover the GW1000
2022-04-26 18:07:36.692 Discovered GW1000 device: IP=192.168.1.151, MAC=E8:DB:84:E3:D4:D3
2022-04-26 18:07:40.303 Discovered one GW1000 device
2022-04-26 18:07:40.304 Using IP address = 192.168.1.151 Port = 45000
2022-04-26 18:07:40.306 GW1000 Connect attempt 1
2022-04-26 18:07:40.332 GW1000 Connect attempt 2
2022-04-26 18:07:40.333 GW1000 Connect attempt 3
2022-04-26 18:07:40.334 GW1000 Connect attempt 4
2022-04-26 18:07:40.335 GW1000 Connect attempt 5
2022-04-26 18:07:40.335 GW1000 connect failed
2022-04-26 18:07:40.335 Not Connected
2022-04-26 18:07:40.337 Loading last N hour data from data logs: 26/04/2022 18:07:00
2022-04-26 18:07:40.346 LoadRecent: Attempting to load 7 days of entries to recent data list
2022-04-26 18:07:49.200 LoadRecent: Loaded 1 new entries to recent database
2022-04-26 18:07:49.210 LoadRecentAqFromDataLogs: Attempting to load 7 days of entries to Air Quality recent data
2022-04-26 18:08:07.144 LoadRecentAqFromDataLogs: Loaded 9658 new entries to recent database
2022-04-26 18:08:07.149 LoadLast3Hour: Attempting to load 3 hour data list
2022-04-26 18:08:07.213 LoadLast3Hour: Loaded 181 entries to last 3 hour data list
2022-04-26 18:08:07.260 Creating extra sensors
2022-04-26 18:08:07.262 Lock: Station waiting for the lock
2022-04-26 18:08:07.481 844 web tags initialised
2022-04-26 18:08:07.499 Generating the daily graph data files
2022-04-26 18:08:09.506 Lock: Cumulus releasing the lock
2022-04-26 18:08:09.507 Lock: Station has the lock
2022-04-26 18:08:09.507 API.GetHistoricData: Missing Ecowitt API data in the configuration, aborting!
2022-04-26 18:08:09.507 Lock: Station releasing the lock
2022-04-26 18:08:09.642 Starting GW1000
2022-04-26 18:08:09.648 Start Extra Sensors
2022-04-26 18:08:09.648 Start Timers
2022-04-26 18:08:09.648 Starting 1-minute timer
2022-04-26 18:08:09.651 Data logging interval = 0 (1 mins)
2022-04-26 18:08:09.651 Starting Realtime timer, interval = 30 seconds
2022-04-26 18:08:09.652 Wundlist count is zero
2022-04-26 18:08:09.652 Windylist count is zero
2022-04-26 18:08:09.652 MySqlList is Empty
2022-04-26 18:08:09.654 Normal running
2022-04-26 18:08:09.656 Attempting to reconnect to GW1000...
2022-04-26 18:08:09.657 GW1000 Connect attempt 1
2022-04-26 18:08:10.665 GW1000 reconnected
2022-04-26 18:08:10.665 Reconnected to GW1000
2022-04-26 18:08:13.422 Reading live data

Does the data continuously update in the phone app - WS View(+), or is that pausing as well?

A recent firmware update to the GW1000 devices caused them to reboot very frequently, but I've not heard of any issues with the GW1100

Mark,

Thanks for responding, it’s pausing the uploads too. I had a major 2 hour fallout 23/24 April over the rollover period which was a pain. Since then it’s dropped out quite frequently, but for shorter periods. I stopped Cumulus and restarted it yesterday evening which took 4 tries to find the GW again. Nothing has changed in my setup or kit. I guess I’d better reset the gateway completely and see what happens, I may even go back to my backup GW1000 if I can’t stop it.

Linda

for the time being firmware 1.7.2 for GW1000/WH2650, 2.1.4 for GW1100 and 2.1.4 for GW2000 are rather stable. The frequents reboot of the GW1000/WH2650 devices introduced with 1.6.9 - 1.7.1 has also diminished with 1.7.2.

I contacted Ecowitt and had a quick response asking me if when it happens I can ping Ecowitt.net and if the wifi light is slow flashing.

Both are almost impossible unless I can catch it in the act! This is difficult as if it’s at night I can’t observe it anyway, and the dropouts are being picked up by Cumulus but I’m obviously not watching that 24/7. It seemed to settle down, but had another session of dropouts yesterday. I think all I can do at the moment is to log them and see if there’s a pattern. It’s odd that it’s been fine for 6 months, nothing has changed in my setup at all.

I had another series of dropouts this morning, things have been fine since. Grateful please if anyone can see anything stupid that I'm doing to cause this? Otherwise, I'm not sure what to do next. I can't think that anything is faulty or it would happen more frequently. Thanks very much

2022-06-03 18:16:07.407 Starting on Linux
2022-06-03 18:16:07.430 Creating SIGTERM monitor
2022-06-03 18:16:07.623 Running interactively
2022-06-03 18:16:08.135 Creating main MX log file - MXdiags/20220603-181608.txt
2022-06-03 18:16:08.604 Cumulus MX v.3.17.0 build 3184
2022-06-03 18:16:08.604 Working Dir: /home/pi/CumulusMX/
2022-06-03 18:16:10.679 http://192.168.1.122:8998/
2022-06-03 18:16:10.681 Open the admin interface by entering one of the above URLs into a web browser.
2022-06-03 18:16:10.724 Today.ini = data/today.ini
2022-06-03 18:16:10.725 Last update=2022-06-03T18:15:00
2022-06-03 18:16:21.285 Connected to station
2022-06-03 18:16:53.284 Normal running
2022-06-04 04:04:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:04:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:05:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:05:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:06:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:06:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:07:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:07:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:08:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:08:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:09:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:09:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:10:25.375 Failed to discover any Ecowitt devices
2022-06-04 04:10:55.375 Failed to discover any Ecowitt devices
2022-06-04 04:11:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:11:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:12:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:12:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:13:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:13:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:14:25.315 Failed to discover any Ecowitt devices
2022-06-04 04:14:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:15:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:15:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:16:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:16:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:17:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:17:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:18:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:18:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:19:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:19:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:20:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:20:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:21:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:21:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:22:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:22:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:23:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:23:55.306 Failed to discover any Ecowitt devices
2022-06-04 04:24:25.306 Failed to discover any Ecowitt devices
2022-06-04 04:24:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:25:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:25:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:26:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:26:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:27:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:27:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:28:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:28:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:29:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:29:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:30:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:30:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:31:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:31:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:32:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:32:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:33:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:33:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:34:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:34:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:35:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:35:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:36:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:36:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:37:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:37:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:38:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:38:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:39:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:39:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:40:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:40:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:41:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:41:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:42:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:42:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:43:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:43:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:44:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:44:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:45:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:45:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:46:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:46:55.297 Failed to discover any Ecowitt devices
2022-06-04 04:47:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:47:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:48:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:48:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:49:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:49:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:50:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:50:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:51:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:51:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:52:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:52:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:53:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:53:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:54:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:54:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:55:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:55:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:56:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:56:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:57:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:57:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:58:25.296 Failed to discover any Ecowitt devices
2022-06-04 04:58:55.296 Failed to discover any Ecowitt devices
2022-06-04 04:59:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:59:55.296 Failed to discover any Ecowitt devices
2022-06-04 05:00:25.295 Failed to discover any Ecowitt devices
2022-06-04 05:00:55.295 Failed to discover any Ecowitt devices
2022-06-04 05:01:25.295 Failed to discover any Ecowitt devices
2022-06-04 05:01:55.295 Failed to discover any Ecowitt devices
2022-06-04 05:02:25.296 Failed to discover any Ecowitt devices
2022-06-04 05:02:55.296 Failed to discover any Ecowitt devices
2022-06-04 05:03:25.296 Failed to discover any Ecowitt devices
2022-06-04 05:03:55.296 Failed to discover any Ecowitt devices
2022-06-04 05:04:25.296 Failed to discover any Ecowitt devices
2022-06-04 05:04:55.296 Failed to discover any Ecowitt devices
2022-06-04 05:05:25.296 Failed to discover any Ecowitt devices

2022-06-04 04:04:53.231 Discovery Run #1
2022-06-04 04:04:54.255 Discovery Run #2
2022-06-04 04:04:54.684 Reading live data
2022-06-04 04:04:55.295 Failed to discover any Ecowitt devices
2022-06-04 04:04:57.703 DoCommand(CMD_GW1000_LIVEDATA): No response received
2022-06-04 04:04:57.704 GetLiveData: Invalid response
2022-06-04 04:05:00.008 *** Data input appears to have stopped
2022-06-04 04:05:00.009 Current CPU temp = 49.4°C
2022-06-04 04:05:01.705 Reading live data
2022-06-04 04:05:04.713 DoCommand(CMD_GW1000_LIVEDATA): No response received
2022-06-04 04:05:04.713 GetLiveData: Invalid response
2022-06-04 04:05:08.714 Reading live data
2022-06-04 04:05:11.732 DoCommand(CMD_GW1000_LIVEDATA): No response received
2022-06-04 04:05:11.733 GetLiveData: Invalid response
2022-06-04 04:05:15.733 Reading live data
2022-06-04 04:05:18.745 DoCommand(CMD_GW1000_LIVEDATA): No response received
2022-06-04 04:05:18.747 GetLiveData: Invalid response
2022-06-04 04:05:22.747 Reading live data
2022-06-04 04:05:23.226 ERROR: No data received from the GW1000 for 30 seconds
2022-06-04 04:05:23.227 Running Ecowitt Local API auto-discovery...


2022-06-04 04:28:23.253 Discovery Run #1
2022-06-04 04:28:24.255 Discovery Run #2
2022-06-04 04:28:25.295 Failed to discover any Ecowitt devices
2022-06-04 04:28:26.856 Ecowitt Gateway Connect attempt 2
2022-06-04 04:28:28.095 Error opening TCP port: No route to host
2022-06-04 04:28:33.096 Ecowitt Gateway Connect attempt 3
2022-06-04 04:28:36.255 Error opening TCP port: No route to host
2022-06-04 04:28:41.255 Ecowitt Gateway Connect attempt 4
2022-06-04 04:28:44.415 Error opening TCP port: No route to host
2022-06-04 04:28:49.415 Ecowitt Gateway Connect attempt 5
2022-06-04 04:28:52.575 Error opening TCP port: No route to host
2022-06-04 04:28:53.229 ERROR: No data received from the GW1000 for 30 seconds
2022-06-04 04:28:53.229 Running Ecowitt Local API auto-discovery...

Did either your computer or your Ecowitt device become disconnected from the network?

Thank you very much for helping with the obvious! I need to check the RPi logs, I hadn’t thought of that. I’ve just checked the upload to Ecowitt which looks to be ok. I’ll look at the Pi later to see what that is saying. I could be blaming the GW1100 when it isn’t that at all. I’ll let you know what I find. Thanks once again

Could I use this Topic to ask all concerned with posting errors NOT to cut and post to your post from the MXDiags file, please zip up the MXDiags .txt file and attach that to your post, it gives everyone a better chance of fixing your problem.

Yes, thank you. Sorry!

my apologies to everyone, hopefully I’ve now learned my lesson, to check before assuming something. Something obviously happened to my router, the GW1100 was blameless. Thanks to Freddie for pointing me in the right direction which is where I should have started in the first place….

Help or suggestions please.

I am using ecowitt GW1100A- V2.1.8 the firmware was updated 5th Sep 22
For the last 4 weeks I receive the dreaded "No data received from the GW1000 for 30 seconds"

I have two installations of Cumulusmx running. One on windows tablet, one on raspberry pi.

Both are on build 3205

This morning I checked the window. / terminal screen and they show differing data.

The windows installation records normal running.
The pi terminal shows 15 connection issues over last 16 hours or so.

Attachments show displays of both installations.

I have been running both installations for last 20 months without these issues.

Any suggestions please ?

Cordially...Paul

Paul,

I have about given up on this, it’s beyond my ability to solve! You’re having exactly the same thing happening as I get. I’m still wondering if it’s somehow to do with how MX is interacting with the Pi? I had a nightmare few weeks with dropouts as you’re describing, then over the last week or so, since I upgraded to 3204 I’ve had no problems at all. I’ve still to rebuild the Pi, it’s not something I’m very keen to do, especially since I’ve no idea what’s causing the issue. There are so many possible variables, the GW1100 itself, the router, the Pi, operating software, CumulusMX software. Interestingly, if your windows machine is fine, then this rather rules out hardware issues from the GW or router.

Linda

I did have similar issues and I've read somewhere that aging of some 2.4 GHz chip isn't unusual but I cannot find where.
My old zyxel armor X1 has been replaced and the number of reconnects is much lower.

LindaFNM wrote: ↑Tue 06 Sep 2022 9:29 am if your windows machine is fine, then this rather rules out hardware issues from the GW or router.
Linda

GW yes, router not necessarily - there are a few more factors in the network infrastructure to be considered, before the router can be excluded.
Only if the whole route from the console to the application and back is (for practical purposes) identical regarding configuration, connectivity type, hardware involved (including cables, switches, access points, server location etc.), the router could be excluded.
The RPi network interface(s) could behave naughtily too - the RPi might temporarily not get enough power turning the network interface(s) unstable - an often observed issue with RPis (too weak a power supply).