meteohub.de

Posted: **Wed Apr 10, 2024 7:38 pm**

I recently moved from TP Link to RPi for my MB platform. I was getting somewhat frequent lock-ups and figured it could use the extra memory. The TP was running 95% plus all the time.

Now on the RPi it is even worse.
It loses contact with two WiFi Loggers and one Ethernet logger.
I have to re-boot the MB.
Everything is on reserved IP and running straight to my router's WiFi and ethernet. The Mesh System is still running in the house but not used by MB or Loggers.

Below is the latest log while it is not receiving any data. Live Data Tab on MB has this message:

"Data logger momentarily cannot provide data. Please try again in a minute. If it does not show up later, please also check weather station selection on "Station" tab."

The 192.168.2.46 IP mentioned in the log is the main WiFi Logger in use.

Some of the log deleted as is was too big for message. It is just the same message over and over.

Any idea what could be causing this?

Thanks

D

Code: Select all

logger (10.04.2024 07:56:36): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 07:57:02): message above repeats 12 times.
logger (10.04.2024 07:57:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 07:57:07): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 07:57:31): message above repeats 7 times.
logger (10.04.2024 07:57:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 07:57:36): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 07:58:04): message above repeats 10 times.
logger (10.04.2024 07:58:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 07:58:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 07:58:31): message above repeats 7 times.
logger (10.04.2024 07:58:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument



logger (10.04.2024 08:10:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:10:08): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:10:34): message above repeats 8 times.
logger (10.04.2024 08:10:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:10:39): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:11:04): message above repeats 12 times.
logger (10.04.2024 08:11:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:11:09): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:11:33): message above repeats 7 times.
logger (10.04.2024 08:11:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:11:37): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:12:04): message above repeats 11 times.
logger (10.04.2024 08:12:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:12:07): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:12:35): message above repeats 7 times.
logger (10.04.2024 08:12:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:12:36): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:13:05): message above repeats 10 times.
logger (10.04.2024 08:13:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:13:07): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:13:34): message above repeats 7 times.
logger (10.04.2024 08:13:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:13:36): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:14:05): message above repeats 10 times.
logger (10.04.2024 08:14:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:14:06): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:14:35): message above repeats 7 times.
logger (10.04.2024 08:14:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:14:39): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:15:05): message above repeats 10 times.
logger (10.04.2024 08:15:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:15:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:15:35): message above repeats 8 times.
logger (10.04.2024 08:15:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:15:40): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:16:05): message above repeats 11 times.
logger (10.04.2024 08:16:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:16:06): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:16:31): message above repeats 7 times.
logger (10.04.2024 08:16:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:16:36): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:17:03): message above repeats 12 times.
logger (10.04.2024 08:17:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:17:06): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:17:33): message above repeats 8 times.
logger (10.04.2024 08:17:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:17:38): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:18:04): message above repeats 10 times.
logger (10.04.2024 08:18:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:18:11): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:18:34): message above repeats 7 times.
logger (10.04.2024 08:18:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:18:40): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:19:05): message above repeats 11 times.
logger (10.04.2024 08:19:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:19:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:19:35): message above repeats 8 times.
logger (10.04.2024 08:19:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:19:40): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:20:05): message above repeats 11 times.
logger (10.04.2024 08:20:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:20:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:20:32): message above repeats 7 times.
logger (10.04.2024 08:20:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:20:37): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:21:03): message above repeats 10 times.
logger (10.04.2024 08:21:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:21:06): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:21:32): message above repeats 10 times.
logger (10.04.2024 08:21:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:21:37): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:22:04): message above repeats 11 times.
logger (10.04.2024 08:22:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:22:09): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:22:32): message above repeats 7 times.
logger (10.04.2024 08:22:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:22:36): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:23:04): message above repeats 10 times.
logger (10.04.2024 08:23:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:23:08): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:23:35): message above repeats 8 times.
logger (10.04.2024 08:23:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:23:41): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:24:04): message above repeats 9 times.
logger (10.04.2024 08:24:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:24:06): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:24:33): message above repeats 8 times.
logger (10.04.2024 08:24:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:24:38): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:25:04): message above repeats 10 times.
logger (10.04.2024 08:25:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:25:08): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:25:33): message above repeats 7 times.
logger (10.04.2024 08:25:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:25:36): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:26:04): message above repeats 10 times.
logger (10.04.2024 08:26:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:26:07): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:26:33): message above repeats 10 times.
logger (10.04.2024 08:26:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:26:40): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:27:05): message above repeats 13 times.
logger (10.04.2024 08:27:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:27:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:27:32): message above repeats 6 times.
logger (10.04.2024 08:27:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:27:37): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:28:04): message above repeats 10 times.
logger (10.04.2024 08:28:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:28:07): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:28:32): message above repeats 8 times.
logger (10.04.2024 08:28:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:28:37): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:29:04): message above repeats 11 times.
logger (10.04.2024 08:29:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:29:08): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:29:34): message above repeats 8 times.
logger (10.04.2024 08:29:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:29:39): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:30:04): message above repeats 11 times.
logger (10.04.2024 08:30:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:30:09): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:30:35): message above repeats 8 times.
logger (10.04.2024 08:30:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:30:40): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:31:04): message above repeats 9 times.
logger (10.04.2024 08:31:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:31:07): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:31:32): message above repeats 10 times.
logger (10.04.2024 08:31:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:31:37): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:32:04): message above repeats 11 times.
logger (10.04.2024 08:32:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:32:07): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:32:32): message above repeats 7 times.
logger (10.04.2024 08:32:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:32:36): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:33:04): message above repeats 10 times.
logger (10.04.2024 08:33:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:33:08): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:33:34): message above repeats 8 times.
logger (10.04.2024 08:33:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:33:39): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:34:05): message above repeats 10 times.
logger (10.04.2024 08:34:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:34:10): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:34:34): message above repeats 7 times.
logger (10.04.2024 08:34:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:34:37): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:35:05): message above repeats 10 times.
logger (10.04.2024 08:35:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:35:07): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:35:32): message above repeats 7 times.
logger (10.04.2024 08:35:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:35:37): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:36:04): message above repeats 10 times.
logger (10.04.2024 08:36:06): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:36:07): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:36:29): message above repeats 9 times.
logger (10.04.2024 08:36:36): station 0 (Vantage), error make socket 192.168.2.46: port 22222: Invalid argument
logger (10.04.2024 08:36:36): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:36:49): message above repeats 4 times.
logger (10.04.2024 08:36:50): error while doing accept on socket 5558 (22): Invalid argument
logger (10.04.2024 08:36:55): message above repeats 98 times.
logger (10.04.2024 08:36:55): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (10.04.2024 08:36:55): message above repeats 2 times.
logger (10.04.2024 08:36:55): error while doing accept on socket 5558 (22): Invalid argument
logger (10.04.2024 08:37:00): message above repeats 95 times.

Posted: **Thu Apr 11, 2024 12:01 am**

Which model of SD card are you using?

Posted: **Thu Apr 11, 2024 12:47 am**

Greenliant 8GB

Posted: **Thu Apr 11, 2024 2:38 pm**

Error message tells that Meteobridge cannot establish a pipe (/dev/meteobridge) to connect logger with service event handler.
This might be a specific issue with your RPI install. If you provide me remote login, I can have a closer look.
Please send credentials to "info(at)meteobridge.com".

Posted: **Sat Apr 13, 2024 4:19 pm**

Any chance you can take a look while it is in error? I will leave it for a bit to see if you happen to be on line.

Thanks

D

Posted: **Sat Apr 13, 2024 4:33 pm**

No idea, did you install something additionally on the RPI? Looks like it runs out of sockets after a while.

Posted: **Sat Apr 13, 2024 4:35 pm**

Now that I just post that.....just as I browsed to the Loggers web interfaces, the MB started getting data again.

Are the loggers at fault? Going to sleep? I have the Stay Alive selection active.

Thanks

D

Posted: **Sat Apr 13, 2024 4:39 pm**

admin wrote: ↑Sat Apr 13, 2024 4:33 pm No idea, did you install something additionally on the RPI? Looks like it runs out of sockets after a while.

Initially I tried to have it connected to a UPS but that unit does not work the way I expected it to. It is one of these types:

https://geekworm.com/products/raspberry ... ment-board

and needs communication from a program on the RPi to be properly set up.

Is it possible that unit tried to communicate on the COMM pins and affected the MB OS?

But I was having this issue before migrating from the TP Link to the RPi

Thanks

D

Posted: **Sat Apr 13, 2024 4:41 pm**

It quite often goes for about two minutes, not uploading anything to WU or W34, then starts back up. All the while the Live Data page on MB seems fine.

Thanks

D

Posted: **Sat Apr 13, 2024 4:49 pm**

I recommend to check what is flooding the sockets by "netstat -nap" when problem shows up again.

May be one of the loggers does keep sockets stalled/open may be because of timing issues. You are not using Davis loggers but 3rd party stuff, some using WiFi.

Posted: **Sat Apr 13, 2024 4:57 pm**

192.168.2.46 seems to misbehave, lots of "CLOSE_WAIT" connections.

Code: Select all

root@MeteoBridge:~# netstat -nap | grep 192.168.2
tcp        0      0 192.168.2.59:53         0.0.0.0:*               LISTEN      493/dnsmasq
tcp        0      0 192.168.2.59:47606      192.168.2.58:22222      ESTABLISHED 20007/loggerd
tcp        0      0 192.168.2.59:37496      192.168.2.46:22222      CLOSE_WAIT  20007/loggerd
tcp        0      0 192.168.2.59:35682      52.22.134.222:80        TIME_WAIT   -
tcp        0      0 192.168.2.59:35680      54.159.105.134:80       TIME_WAIT   -
tcp        0      0 192.168.2.59:35624      54.159.105.134:80       TIME_WAIT   -
tcp        0      0 192.168.2.59:37498      192.168.2.46:22222      CLOSE_WAIT  20007/loggerd
tcp        0      0 192.168.2.59:37580      192.168.2.46:22222      ESTABLISHED 20007/loggerd
tcp        0      0 192.168.2.59:35734      52.22.134.222:80        TIME_WAIT   -
tcp        0      0 192.168.2.59:35752      52.22.134.222:80        TIME_WAIT   -
tcp        0      0 192.168.2.59:51182      18.245.96.5:80          TIME_WAIT   -
tcp        0      0 192.168.2.59:37486      192.168.2.46:22222      CLOSE_WAIT  20007/loggerd
tcp        0      0 192.168.2.59:51262      34.232.250.77:80        TIME_WAIT   -
tcp        0    376 192.168.2.59:50822      162.55.245.41:80        ESTABLISHED 2148/ssh
tcp        0      0 192.168.2.59:41004      192.168.2.90:22222      ESTABLISHED 20007/loggerd
tcp        0      0 192.168.2.59:37404      192.168.2.46:22222      CLOSE_WAIT  20007/loggerd
tcp        0      0 192.168.2.59:35670      54.159.105.134:80       TIME_WAIT   -
tcp        0      0 192.168.2.59:48592      18.245.96.17:80         TIME_WAIT   -
tcp        0      0 192.168.2.59:35692      52.22.134.222:80        TIME_WAIT   -
udp        0      0 192.168.2.59:53         0.0.0.0:*                           493/dnsmasq
udp        0      0 192.168.2.255:137       0.0.0.0:*                           1283/nmbd
udp        0      0 192.168.2.59:137        0.0.0.0:*                           1283/nmbd
udp        0      0 192.168.2.255:138       0.0.0.0:*                           1283/nmbd
udp        0      0 192.168.2.59:138        0.0.0.0:*                           1283/nmbd
root@MeteoBridge:~#

https://www.baeldung.com/linux/remove-c ... connection

After a connection is established, any side of the connection can end it. If the remote side ends the connection, we can’t send or receive more data. Therefore, we can only close the connection, too.

When one side closes the connection, the socket at the other side changes to the CLOSE_WAIT state. So, the CLOSE_WAIT state means the socket is closed on the remote side, and the system is waiting for the local side to close it.

Then, the only way to remove the CLOSE_WAIT socket connection is to close it. Usually, the process knows when the remote side closes the connection, and the local process closes it. This is normal behavior, so it’s uncommon to see CLOSE_WAIT sockets.

Although, if we see a CLOSE_WAIT socket, it may be because of a software bug. For example, if the process becomes unresponsive and the remote side closed the connection, the socket is never closed. So, if this happens, the socket stays in the CLOSE_WAIT state.

Let's see if the system if flooded by CLOSE_WAIT socket connections over time. If so I can try find a cure. I guess instable WiFi connection to the WiFi-Logger causes this.

Posted: **Sat Apr 13, 2024 5:13 pm**

You may have put out some puzzle pieces that I can try and assemble.

I noticed the .46 device multi entries.

Theory: It is the farthest away from MB and always has been. If there are connection issues, is it possible MB does not get the message of Socket closure?

I will do some temporary relocating of Consoles and if it pans out I have already enroute a roll of ethernet cabling to do some layout in my house. It is sorely lacking. That would allow for MB to get relocated near loggers current location and still be hardwired.

Thanks

D

Posted: **Sun Apr 14, 2024 1:00 am**

I added some code to better handle dropped sockets on the logger side. I set you station on this beta code. Please inspect if things are better now.

Posted: **Sun Apr 14, 2024 1:24 am**

Now the logs show clearly that logger 192.168.2.46 cuts the connection after 1-2 minutes.
Is there a way to tell this 3rd party product not to do so?
Or is another program also hammering onto this logger?

Posted: **Sun Apr 14, 2024 2:12 am**

Thank you for the time to look into this.

Other than the Ethernet logger, the two WiFi loggers (.46 and .58) are dedicated to provide data to MB. Ethernet, .90, does upload to WL. There is a "Keep Alive" function incorporated into the loggers. I have it turned on.

I assume I should leave the Version Control to remain on 5.7 to retain the alterations you did?

I will monitor for now.

I wonder if the Keep Alive function is a problem?

meteohub.de

MB keeps losing contact with Loggers.

MB keeps losing contact with Loggers.

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers

Re: MB keeps losing contact with Loggers