meteohub.de

Posted: **Fri Jun 12, 2020 7:36 pm**

I triggered the 4 leak sensors and the leaks registered on the ambient website and I got 4 email alerts, one for each of the triggered sensors

Posted: **Fri Jun 12, 2020 7:54 pm**

2 & 3 Sorted. Just part 1 Lightning detector left now. But as Meatloaf said "Two Out of Three Ain't Bad"

Posted: **Sat Jun 13, 2020 12:27 am**

just curious to what this water leak sensor does?

Posted: **Sat Jun 13, 2020 12:46 am**

galfert wrote: ↑Fri Jun 12, 2020 2:56 pm Yes I had discussion with Ecowitt to explain the findings that Boris discovered. They responded quick!

MB Data Fix.jpg

Still happening after update here. less frequently, but still happening.

Posted: **Sat Jun 13, 2020 1:55 am**

I'm going on 11 hours since 1.6.0 firmware install and it hasn't had any issues even once. No data loss. I'm set to catching it also via MB alert trigger. ¯\_(ツ)_/¯

Posted: **Sat Jun 13, 2020 7:50 am**

I have two remote stations that require up to an hours drive to reach. Fortunately I have a ObserverIP at each location. I've switched them over until I can get to them to update them.
People thought I was crazy to include a backup interface. But I'm glad I did.

Posted: **Thu Jun 18, 2020 12:36 pm**

galfert wrote: ↑Sat Jun 13, 2020 1:55 am I'm going on 11 hours since 1.6.0 firmware install and it hasn't had any issues even once. No data loss. I'm set to catching it also via MB alert trigger. ¯\_(ツ)_/¯

Yeah dunno.

MB 4.3 (Jun 12 2020, build 3113), FW 1.3
GW1000 1.6.0

I still get this - although not nearly as frequent as GW1000 1.5.9 firmware:

Code: Select all

logger (17.06.2020 03:29:53): unexpected 0 bytes.
logger (17.06.2020 03:29:53): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:30:23): connect station 0 (GW1000 via th).
logger (17.06.2020 03:30:23): unexpected 0 bytes.
logger (17.06.2020 03:30:23): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:30:53): connect station 0 (GW1000 via th).
logger (17.06.2020 03:30:53): unexpected 0 bytes.
logger (17.06.2020 03:30:53): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:31:23): connect station 0 (GW1000 via th).
logger (17.06.2020 03:31:23): unexpected 0 bytes.
logger (17.06.2020 03:31:23): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:31:53): connect station 0 (GW1000 via th).
logger (17.06.2020 03:31:53): unexpected 0 bytes.
logger (17.06.2020 03:31:53): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:32:23): connect station 0 (GW1000 via th).
logger (17.06.2020 03:32:23): unexpected 0 bytes.
logger (17.06.2020 03:32:23): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:32:53): connect station 0 (GW1000 via th).
logger (17.06.2020 03:32:53): unexpected 0 bytes.
logger (17.06.2020 03:32:53): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:33:23): connect station 0 (GW1000 via th).
logger (17.06.2020 03:33:23): no valid signal for 300 seconds, data logger will be restarted.
logger (17.06.2020 03:33:23): disconnect station 0 (GW1000): exit
logger (17.06.2020 03:33:23): data logger stopped.
logger (17.06.2020 03:33:23): historical data loaded (69 records).
logger (17.06.2020 03:33:23): data logger (version 5.1d, build 3113) started.
logger (17.06.2020 03:33:24): connect station 0 (GW1000 via TCP/IP).
logger (17.06.2020 03:33:27): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (17.06.2020 03:33:27): services paused.
logger (17.06.2020 03:33:34): sensors are now providing data.
logger (17.06.2020 03:33:34): services started.
system (17.06.2020 03:33:44): stop of logging process initiated.
system (17.06.2020 03:33:52): start of logging process initiated.
logger (17.06.2020 03:33:52): historical data loaded (69 records).
logger (17.06.2020 03:33:52): data logger (version 5.1d, build 3113) started.
logger (17.06.2020 03:33:52): connect station 0 (GW1000 via TCP/IP).
logger (17.06.2020 03:33:56): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (17.06.2020 03:33:56): services paused.
logger (17.06.2020 03:34:03): sensors are now providing data.
logger (17.06.2020 03:34:03): services started.
logger (17.06.2020 03:34:03): message above repeats 1 time.
logger (17.06.2020 03:38:20): connection reestablished.
logger (17.06.2020 03:38:20): unexpected 0 bytes.
logger (17.06.2020 03:38:20): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:38:50): connect station 0 (GW1000 via th).
logger (17.06.2020 03:38:50): unexpected 0 bytes.
logger (17.06.2020 03:38:50): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:39:20): connect station 0 (GW1000 via th).
logger (17.06.2020 03:39:20): unexpected 0 bytes.
logger (17.06.2020 03:39:20): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:39:50): connect station 0 (GW1000 via th).
logger (17.06.2020 03:39:50): unexpected 0 bytes.
logger (17.06.2020 03:39:50): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:40:20): connect station 0 (GW1000 via th).
logger (17.06.2020 03:40:20): unexpected 0 bytes.
logger (17.06.2020 03:40:20): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:40:50): connect station 0 (GW1000 via th).
logger (17.06.2020 03:40:50): unexpected 0 bytes.
logger (17.06.2020 03:40:50): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:41:20): connect station 0 (GW1000 via th).
logger (17.06.2020 03:41:20): unexpected 0 bytes.
logger (17.06.2020 03:41:20): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:41:50): connect station 0 (GW1000 via th).
logger (17.06.2020 03:41:50): unexpected 0 bytes.
logger (17.06.2020 03:41:50): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:42:20): connect station 0 (GW1000 via th).
logger (17.06.2020 03:42:20): unexpected 0 bytes.
logger (17.06.2020 03:42:20): disconnect station 0 (GW1000): response without data
logger (17.06.2020 03:42:50): connect station 0 (GW1000 via th).
logger (17.06.2020 03:42:50): unexpected 0 bytes.
logger (17.06.2020 03:42:50): disconnect station 0 (GW1000): response without data
system (17.06.2020 03:43:00): stop of logging process initiated.
system (17.06.2020 03:43:08): start of logging process initiated.
logger (17.06.2020 03:43:08): historical data loaded (69 records).
logger (17.06.2020 03:43:08): data logger (version 5.1d, build 3113) started.
logger (17.06.2020 03:43:09): connect station 0 (GW1000 via TCP/IP).
logger (17.06.2020 03:43:12): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (17.06.2020 03:43:12): services paused.
logger (17.06.2020 03:43:19): sensors are now providing data.
logger (17.06.2020 03:43:19): services started.
logger (17.06.2020 03:43:19): message above repeats 1 time.
logger (17.06.2020 10:12:15): connection reestablished.
logger (17.06.2020 10:12:15): unexpected 0 bytes.
logger (17.06.2020 10:12:15): disconnect station 0 (GW1000): response without data
logger (17.06.2020 10:12:45): connect station 0 (GW1000 via th).
logger (17.06.2020 10:12:45): unexpected 0 bytes.
logger (17.06.2020 10:12:45): disconnect station 0 (GW1000): response without data
logger (17.06.2020 10:13:15): connect station 0 (GW1000 via th).
logger (17.06.2020 10:13:15): unexpected 0 bytes.
logger (17.06.2020 10:13:15): disconnect station 0 (GW1000): response without data
logger (17.06.2020 10:13:45): connect station 0 (GW1000 via th).
logger (17.06.2020 10:13:45): unexpected 0 bytes.
logger (17.06.2020 10:13:45): disconnect station 0 (GW1000): response without data
logger (17.06.2020 10:14:15): connect station 0 (GW1000 via th).
logger (17.06.2020 10:14:15): unexpected 0 bytes.
logger (17.06.2020 10:14:15): disconnect station 0 (GW1000): response without data
logger (17.06.2020 10:14:45): connect station 0 (GW1000 via th).
logger (17.06.2020 10:14:45): unexpected 0 bytes.
logger (17.06.2020 10:14:45): disconnect station 0 (GW1000): response without data
logger (17.06.2020 10:15:15): connect station 0 (GW1000 via th).
logger (17.06.2020 10:15:15): unexpected 0 bytes.
logger (17.06.2020 10:15:15): disconnect station 0 (GW1000): response without data
logger (17.06.2020 10:15:45): connect station 0 (GW1000 via th).
logger (17.06.2020 10:15:45): unexpected 0 bytes.
logger (17.06.2020 10:15:45): disconnect station 0 (GW1000): response without data
logger (17.06.2020 10:16:15): connect station 0 (GW1000 via th).
logger (17.06.2020 10:16:15): unexpected 0 bytes.
logger (17.06.2020 10:16:15): disconnect station 0 (GW1000): response without data
logger (17.06.2020 10:16:45): connect station 0 (GW1000 via th).
logger (17.06.2020 10:16:45): unexpected 0 bytes.
logger (17.06.2020 10:16:45): disconnect station 0 (GW1000): response without data
system (17.06.2020 10:16:54): stop of logging process initiated.
system (17.06.2020 10:17:01): start of logging process initiated.
logger (17.06.2020 10:17:02): historical data loaded (69 records).
logger (17.06.2020 10:17:02): data logger (version 5.1d, build 3113) started.
logger (17.06.2020 10:17:02): connect station 0 (GW1000 via TCP/IP).
logger (17.06.2020 10:17:05): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (17.06.2020 10:17:05): services paused.
logger (17.06.2020 10:17:13): sensors are now providing data.
logger (17.06.2020 10:17:13): services started.
logger (17.06.2020 10:17:13): message above repeats 1 time.
logger (17.06.2020 23:51:19): connection reestablished.
logger (17.06.2020 23:51:19): unexpected 0 bytes.
logger (17.06.2020 23:51:19): disconnect station 0 (GW1000): response without data
logger (17.06.2020 23:51:49): connect station 0 (GW1000 via th).
logger (17.06.2020 23:51:49): unexpected 0 bytes.
logger (17.06.2020 23:51:49): disconnect station 0 (GW1000): response without data
logger (17.06.2020 23:52:19): connect station 0 (GW1000 via th).
logger (17.06.2020 23:52:19): unexpected 0 bytes.
logger (17.06.2020 23:52:19): disconnect station 0 (GW1000): response without data
logger (17.06.2020 23:52:49): connect station 0 (GW1000 via th).
logger (17.06.2020 23:52:49): unexpected 0 bytes.
logger (17.06.2020 23:52:49): disconnect station 0 (GW1000): response without data
logger (17.06.2020 23:53:19): connect station 0 (GW1000 via th).
logger (17.06.2020 23:53:19): unexpected 0 bytes.
logger (17.06.2020 23:53:19): disconnect station 0 (GW1000): response without data
logger (17.06.2020 23:53:49): connect station 0 (GW1000 via th).
logger (17.06.2020 23:53:49): unexpected 0 bytes.
logger (17.06.2020 23:53:49): disconnect station 0 (GW1000): response without data
logger (17.06.2020 23:54:19): connect station 0 (GW1000 via th).
logger (17.06.2020 23:54:19): unexpected 0 bytes.
logger (17.06.2020 23:54:19): disconnect station 0 (GW1000): response without data
logger (17.06.2020 23:54:49): connect station 0 (GW1000 via th).
logger (17.06.2020 23:54:49): unexpected 0 bytes.
logger (17.06.2020 23:54:49): disconnect station 0 (GW1000): response without data
logger (17.06.2020 23:55:19): connect station 0 (GW1000 via th).
logger (17.06.2020 23:55:19): unexpected 0 bytes.
logger (17.06.2020 23:55:19): disconnect station 0 (GW1000): response without data
logger (17.06.2020 23:55:49): connect station 0 (GW1000 via th).
logger (17.06.2020 23:55:49): unexpected 0 bytes.
logger (17.06.2020 23:55:49): disconnect station 0 (GW1000): response without data
system (17.06.2020 23:55:57): stop of logging process initiated.
system (17.06.2020 23:56:04): start of logging process initiated.
logger (17.06.2020 23:56:05): historical data loaded (69 records).
logger (17.06.2020 23:56:05): data logger (version 5.1d, build 3113) started.
logger (17.06.2020 23:56:05): connect station 0 (GW1000 via TCP/IP).
logger (17.06.2020 23:56:09): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (17.06.2020 23:56:09): services paused.
logger (17.06.2020 23:56:16): sensors are now providing data.
logger (17.06.2020 23:56:16): services started.
logger (17.06.2020 23:56:16): message above repeats 1 time.
logger (18.06.2020 06:24:49): connection reestablished.
logger (18.06.2020 06:24:49): unexpected 0 bytes.
logger (18.06.2020 06:24:49): disconnect station 0 (GW1000): response without data
logger (18.06.2020 06:25:19): connect station 0 (GW1000 via th).
logger (18.06.2020 06:25:19): unexpected 0 bytes.
logger (18.06.2020 06:25:19): disconnect station 0 (GW1000): response without data
logger (18.06.2020 06:25:49): connect station 0 (GW1000 via th).
logger (18.06.2020 06:25:49): unexpected 0 bytes.
logger (18.06.2020 06:25:49): disconnect station 0 (GW1000): response without data
logger (18.06.2020 06:26:19): connect station 0 (GW1000 via th).
logger (18.06.2020 06:26:19): unexpected 0 bytes.
logger (18.06.2020 06:26:19): disconnect station 0 (GW1000): response without data
logger (18.06.2020 06:26:49): connect station 0 (GW1000 via th).
logger (18.06.2020 06:26:49): unexpected 0 bytes.
logger (18.06.2020 06:26:49): disconnect station 0 (GW1000): response without data
logger (18.06.2020 06:27:19): connect station 0 (GW1000 via th).
logger (18.06.2020 06:27:19): unexpected 0 bytes.
logger (18.06.2020 06:27:19): disconnect station 0 (GW1000): response without data
logger (18.06.2020 06:27:49): connect station 0 (GW1000 via th).
logger (18.06.2020 06:27:49): unexpected 0 bytes.
logger (18.06.2020 06:27:49): disconnect station 0 (GW1000): response without data
logger (18.06.2020 06:28:19): connect station 0 (GW1000 via th).
logger (18.06.2020 06:28:19): unexpected 0 bytes.
logger (18.06.2020 06:28:19): disconnect station 0 (GW1000): response without data
logger (18.06.2020 06:28:49): connect station 0 (GW1000 via th).
logger (18.06.2020 06:28:49): unexpected 0 bytes.
logger (18.06.2020 06:28:49): disconnect station 0 (GW1000): response without data
logger (18.06.2020 06:29:19): connect station 0 (GW1000 via th).
logger (18.06.2020 06:29:19): unexpected 0 bytes.
logger (18.06.2020 06:29:19): disconnect station 0 (GW1000): response without data
system (18.06.2020 06:29:40): stop of logging process initiated.
system (18.06.2020 06:29:47): start of logging process initiated.
logger (18.06.2020 06:29:48): historical data loaded (69 records).
logger (18.06.2020 06:29:48): data logger (version 5.1d, build 3113) started.
logger (18.06.2020 06:29:48): connect station 0 (GW1000 via TCP/IP).
logger (18.06.2020 06:29:52): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (18.06.2020 06:29:52): services paused.
logger (18.06.2020 06:29:59): sensors are now providing data.
logger (18.06.2020 06:29:59): services started.

I do not know what "via th" means when it tries to reconnect after a 0 byte issue.

The stop and start of the logger process was my fix script automatically correcting the problem.

Posted: **Thu Jun 18, 2020 7:36 pm**

I'm on 4 days running with no data loss. My Messages log is very short...no incidents.
Meteobridge 4.3 (Jun 14 2020, build 13564), FW 1.4
MR3020 hw version 1.
My Meteobridge is not using Ethernet, it is connected via WiFi.

Also notice my GW1000 connects via TCP/IP not th.

Code: Select all

wnetd  (14.06.2020 08:47:50): process started.
system (14.06.2020 08:47:50): start of logging process initiated.
wnetd  (14.06.2020 08:47:51): send data thread started (pid:2245 tid:2247)
logger (14.06.2020 08:47:51): historical data loaded (30 records).
logger (14.06.2020 08:47:51): data logger (version 5.1d, build 13564) started.
logger (14.06.2020 08:47:52): connect station 0 (GW1000 via TCP/IP).
logger (14.06.2020 08:47:55): sensors are now providing data.
logger (14.06.2020 08:47:55): services started.

Posted: **Thu Jun 18, 2020 7:51 pm**

Thanks for spotting this. It is a bug that can also impact the whole reconnect procedure. Just released update fixes this.

Posted: **Thu Jun 18, 2020 9:22 pm**

admin wrote: ↑Thu Jun 18, 2020 7:51 pm Thanks for spotting this. It is a bug that can also impact the whole reconnect procedure. Just released update fixes this.

Updated, we'll see if it happens again. Thanks!

meteohub.de

Ecowitt GW1000 and Meteobridge

Re: Ecowitt GW1000 and Meteobridge

Re: Ecowitt GW1000 and Meteobridge

Re: Ecowitt GW1000 and Meteobridge

Re: Ecowitt GW1000 and Meteobridge

Re: Ecowitt GW1000 and Meteobridge

Re: Ecowitt GW1000 and Meteobridge

Re: Ecowitt GW1000 and Meteobridge

Re: Ecowitt GW1000 and Meteobridge

Re: Ecowitt GW1000 and Meteobridge

Re: Ecowitt GW1000 and Meteobridge