Does your IP logger have any keep alive strategy? Or, if there is no activity for a while, does it drop the connection?
ut, until @WiFiLogger gets back to us, we'll never know what the issue is.
Tom
I am very sorry for the delay. I had a lot of urgent work before vacations all ASAP.
I would like to describe connection in WiFiLogger now.
There is 3 options, but "Collision" I have not tested and maybe it is not finished. Collision is when WiFiLogger internal functions are able to read station even if TCP port 22222 is opened.
Other more civilized options are:
- "PAUSE with Disconnection"
- "PAUSE"
In general WL IP and WiFiLogger need to make access to console to read data for export. So disconnection option in Cumulus and WeeWX is very needed for proper working.
This is part on PC software like Cumulus, WeatherLink and WeeWX.
On WiFiLogger there are also such options:
WiFiLogger can't disconnect port 22222 every 1 minute, because reading of archive records 513 pages takes 2 minutes 15 sec. And uploading firmware to console takes about 5-7 minutes. But anyway it needs to take care of own export options e.g. to WL.COM, or WU if those are enabled.
So "PAUSE with Disconnection" will close TCP port if there is no command send to console via this port for 60 sec.
Cumulus is sending one command to console to receive continue readings of LOOP. So here is little problem, because one command is sent on the beginning then there is no TX data to console, so WiFiLogger will close such port after 60 sec.
No problem if Cumulus has set discon period. It is closing connection itself every 1 minute.
option "PAUSE" is blocking WiFiLogger against reading console when TCP port is OPEN.
Here, please note that TCP port 22222 will be closed and opened for new software connection.
e.g. WeatherLink PC is reading data via TCP port. Then we opening Cumulus and Cumulus is starting to read console on port 22222. So Cumulus is closing TCP port for WeatherLink PC and new socket is opened for Cumulus. Ofcourse WL PC can make reconnection and close socket for Cumulus.
On the begining it was different. TCP port was assigned to first software. New TCP socket was not opened, before first one was closed.
But Cumulus was making reconnections without closing old port. So Cumulus was trying to open sockets 10 times to access console, but was not releasing first socket which WiFiLogger was reserving for it.
Now new connection drop old.
Also WiFiLogger is working in main loop. TCP port is maintain in same loop where exports to weather services (WL.com, Wu etc....) are made. If connection to WU will be invalid then TIMEOUT for socket is 15 sec. So WeeWX will not have access to console.
On the other hand users knows about that and they are closing all exports and other activities of WiFiLogger, leaving just TCP port access.
In general connection to WeeWX is working fine, but WiFiLogger has a few routines to reboot itself if needed.
I had info from clients that WeeWX with WiFiLogger crash every 4 days. So 4 days it is not issue with TCP port access which can be reset every 1 minute. It is more like WiFiLogger is rebooting. After reboot It takes minimum 8 sec. to works again, sometimes more when archive records have problem to read on the beginning.
I do believe that here will be main problem.
On the other hand why WeeWX is crashing?