CumulusMX 3.28.6 / Ecowitt GW1000

[BadBlake]

My setup:
Win7 64bit
Cumulus 3.28.6
Ecowitt GW1000
Ecowitt sensors

I've been using CumulusMX a couple of years now without a glitch. Been running perfectly up until 2 days ago when I got this message - "Failed to discover any Ecowitt devices".
I checked the GW1000 and it seem ok -I even tried another GW1000 which I bought just in case the old one broke down, but got the same result.
I checked the latest errors in the Utilities/latest errors and got this:

By the way, I have a satellite tuner at 192.168.1.130. I don't know why Cumulus is referring to this ip address. CumulusMX is running at 192.168.1.146
Haven't the slightest idea what to do here. I hope somebody can give me a hand here -I need help!


2024-08-19 11:08:00 - Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing
2024-08-19 11:08:00 - Failed to discover any Ecowitt devices
2024-08-19 11:07:56 - ERROR: No data received from the GW1000 for 30 seconds
2024-08-19 11:07:49 - Error opening TCP port: No connection could be made because the target machine actively refused it 192.168.1.130:45000
2024-08-19 11:07:33 - Error opening TCP port: No connection could be made because the target machine actively refused it 192.168.1.130:45000
2024-08-19 11:07:30 - Failed to discover any Ecowitt devices
2024-08-19 11:07:26 - ERROR: No data received from the GW1000 for 30 seconds
2024-08-19 11:07:26 - Realtime[25]: Not all data is ready, aborting process
2024-08-19 11:07:22 - Error opening TCP port: No connection could be made because the target machine actively refused it 192.168.1.130:45000
2024-08-19 11:07:16 - Error opening TCP port: No connection could be made because the target machine actively refused it 192.168.1.130:45000
2024-08-19 11:07:00 - Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing
2024-08-19 11:07:00 - Failed to discover any Ecowitt devices
2024-08-19 11:06:56 - ERROR: No data received from the GW1000 for 30 seconds
2024-08-19 11:06:30 - Failed to discover any Ecowitt devices
2024-08-19 11:06:26 - ERROR: No data received from the GW1000 for 30 seconds
2024-08-19 11:06:26 - Realtime[23]: Not all data is ready, aborting process
2024-08-19 11:06:20 - Error opening TCP port: No connection could be made because the target machine actively refused it 192.168.1.130:45000
2024-08-19 11:06:00 - Failed to discover any Ecowitt devices
2024-08-19 11:06:00 - Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing
2024-08-19 11:05:59 - Error opening TCP port: No connection could be made because the target machine actively refused it 192.168.1.130:45000
2024-08-19 11:05:56 - ERROR: No data received from the GW1000 for 30 seconds
2024-08-19 11:05:43 - Error opening TCP port: No connection could be made because the target machine actively refused it 192.168.1.130:45000
2024-08-19 11:05:32 - Error opening TCP port: No connection could be made because the target machine actively refused it 192.168.1.130:45000
2024-08-19 11:05:30 - Failed to discover any Ecowitt devices
2024-08-19 11:05:26 - Error opening TCP port: No connection could be made because the target machine actively refused it 192.168.1.130:45000
2024-08-19 11:05:26 - ERROR: No data received from the GW1000 for 30 seconds
2024-08-19 11:05:26 - Realtime[21]: Not all data is ready, aborting process
2024-08-19 11:05:00 - Minimum data set of pressure, temperature, and wind is not available and NoSensorCheck is not enabled. Skip processing
2024-08-19 11:05:00 - Failed to discover any Ecowitt devices
2024-08-19 11:04:56 - ERROR: No data received from the GW1000 for 30 seconds
2024-08-19 11:04:30 - Error opening TCP port: No connection could be made because the target machine actively refused it 192.168.1.130:45000
2024-08-19 11:04:30 - Failed to discover any Ecowitt devices
2024-08-19 11:04:26 - ERROR: No data received from the GW1000 for 30 seconds

[broadstairs]

Well first thing is to check the CMX settings as it obviously has the wrong IP, or you router has assigned different IPs after a reboot or update. Do you specify the IP or allow CMX to discover the devices? It is a good to allocate fix IPs to things like a GW1000 so the IP cannot be changed. Once this is sorted then move on to a couple of things to try.... can you access the GW1000 from the WSView Plus phone app if so does it show all the sensor data? Can you ping the GW1000 from a console window and does it show up? Have you tried a power off/on cycle (leave it off for 30 seconds or so before powering on)? If it does not respond to anything then it could be a power supply issue, have yo a spare and if so what happens when you try that?

Stuart

[rogerthn]

Maybe try with autodiscover disabled?
My settings below

Screenshot 2024-08-19 132847.png

[freddie]

My setup:
Win7 64bit
Cumulus 3.28.6
Ecowitt GW1000
Ecowitt sensors

I've been using CumulusMX a couple of years now without a glitch. Been running perfectly up until 2 days ago when I got this message - "Failed to discover any Ecowitt devices".
I checked the GW1000 and it seem ok -I even tried another GW1000 which I bought just in case the old one broke down, but got the same result.
I checked the latest errors in the Utilities/latest errors and got this:

By the way, I have a satellite tuner at 192.168.1.130. I don't know why Cumulus is referring to this ip address. CumulusMX is running at 192.168.1.146
Haven't the slightest idea what to do here. I hope somebody can give me a hand here -I need help!


...

A tip for future posts - if you zip up the whole log file and attach it to a reply then there will be two advantages: no long posts with repeating error messages, and we get to see ALL pertinent information (for example, the logging of the detection of your station is not included in the log snippet in your post).