Page 1 of 1
Issues with FW 6.4 an Ecowitt Sensor Data
Posted: Tue Aug 25, 2026 9:25 am
by Audinator
Hello,
Since yesterday afternoon, detection of my Ecowitt sensors have failed. This may be related to the firmware update to version 6.4. I haven’t changed any settings myself, yet the list of sensors remains empty. I tried using the GW 3000 instead of the GW 1000, but without success. The configured IP address hasn’t changed; when I access it, all the sensors are displayed as usual. What else can I do? Or does this issue need to be fixed in the new firmware?
Thank you very much for your help.
Re: Issues with FW 6.4 an Ecowitt Sensor Data
Posted: Tue Aug 25, 2026 4:12 pm
by admin
GW3000 works fine with latest release on all systems I know of. Does "System - Logging" give any insight on your issue?
Re: Issues with FW 6.4 an Ecowitt Sensor Data
Posted: Tue Aug 25, 2026 5:33 pm
by Audinator
I also tried GW 3000 but no change. Before yesterday it was working without any problems for months with GW 1000 and also GW 3000. I have GW 2000 but I choosed GW 1000 as station, as intervall for wind is 12 seconds and with GW 3000 it is 30 seconds, which is too less.
Nevertheless, system logging looks like this (first try with GW1000, then GW3000):
logger (25.08.2026 16:39:24): station 0 (GW1000), error connect socket 192.168.178.84 (150): port 45000: Operation now in progress
logger (25.08.2026 16:39:42): station 0 (GW1000), error connect socket 192.168.178.84 (148): port 45000: No route to host
logger (25.08.2026 16:40:24): station 0 (GW1000), error connect socket 192.168.178.84 (150): port 45000: Operation now in progress
logger (25.08.2026 16:40:39): give up waiting for sensors after 120 secs.
logger (25.08.2026 16:40:39): services activated.
logger (25.08.2026 16:40:42): station 0 (GW1000), error connect socket 192.168.178.84 (148): port 45000: No route to host
logger (25.08.2026 16:41:24): station 0 (GW1000), error connect socket 192.168.178.84 (150): port 45000: Operation now in progress
logger (25.08.2026 16:41:42): station 0 (GW1000), error connect socket 192.168.178.84 (148): port 45000: No route to host
logger (25.08.2026 16:42:24): station 0 (GW1000), error connect socket 192.168.178.84 (150): port 45000: Operation now in progress
logger (25.08.2026 16:42:42): station 0 (GW1000), error connect socket 192.168.178.84 (148): port 45000: No route to host
logger (25.08.2026 16:43:24): station 0 (GW1000), error connect socket 192.168.178.84 (150): port 45000: Operation now in progress
system (25.08.2026 16:43:41): stop of logging process initiated.
logger (25.08.2026 16:43:41): parent process received termination signal (15).
logger (25.08.2026 16:43:41): child process received termination signal (15).
system (25.08.2026 16:43:45): start of logging process initiated.
logger (25.08.2026 16:43:45): historical data loaded (62 records).
logger (25.08.2026 16:43:45): data logger started.
logger (25.08.2026 16:43:46): connect station 0 (GW3000 via SW Driver).
logger (25.08.2026 16:43:49): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (25.08.2026 16:43:49): services paused.
system (25.08.2026 16:44:12): stop of logging process initiated.
logger (25.08.2026 16:44:12): parent process received termination signal (15).
logger (25.08.2026 16:44:12): child process received termination signal (15).
logger (25.08.2026 16:44:13): disconnect station 0 (GW3000): exit
system (25.08.2026 16:44:16): start of logging process initiated.
logger (25.08.2026 16:44:17): historical data loaded (62 records).
logger (25.08.2026 16:44:17): data logger started.
logger (25.08.2026 16:44:17): connect station 0 (GW3000 via SW Driver).
logger (25.08.2026 16:44:21): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (25.08.2026 16:44:21): services paused.
logger (25.08.2026 16:46:18): give up waiting for sensors after 120 secs.
I can reach Gateway via 192.168.178.84 and see all data, as usual. I am glad if you have any ideas. Thanks!
Re: Issues with FW 6.4 an Ecowitt Sensor Data
Posted: Tue Aug 25, 2026 6:03 pm
by admin
Please send me remote login credentials. Looks like a routing issue, not an Application SW issue.