Intermittent connectivity with GV500MAP

I'm trying out the Queclink GV500MAP with a Hologram sim and there's very intermittent connectivity. I will get a 10 hour stretch of reliable connection then it will drop out again for hours at a time. Here are the troubleshooting steps I've gone through so far:

• Traccar is up to date
• Confirmed cell connection is reliable via Hologram's dashboard
• Taken device on a road trip to allow connection to alternative towers
• Tried multiple configuration settings such as reporting frequency, long vs short connection, heartbeat settings, and disabling low power modes.
• Confirmed port and protocol settings are as described in the documentation and set via the config file (GL200 / port 5004)
• Confirmed the server is not resource constrained

The GV500MAP certainly has the right bearer and backend settings as it does report and show connected, just intermittently as described. My current device config is as follows:

• Bearer settings: APN: Hologram, APN auth: no auth, Network mode: Auto LTE First & EGPRS, LTE Mode: CAT-M1 First > EGPRS > CAT-NB
• Backend settings: TCP short connection preferred mode, server address with port 5004
• Report Information: Fixed Timing Report, 30 second send interval, 180 second IGF interval, report period disabled to allow all day reporting
• Global device config: No power saving, AGPS enabled, the rest is set as default

Server logs seem to indicate the device is closing the socket still:

2024-10-26 13:59:26  INFO: [Tf9a87a2f: opengts > 162.142.125.197] HTTP/1.1 400 Bad Request\r\ncontent-length: 0\r\n\r\n
2024-10-26 13:59:26  INFO: [Tf9a87a2f: opengts > 162.142.125.197] HTTP/1.1 400 Bad Request\r\ncontent-length: 0\r\n\r\n
2024-10-26 13:59:26  WARN: [Tf9a87a2f] error - Connection reset - SocketException (...)
2024-10-26 13:59:26  INFO: [Tf9a87a2f] disconnected
2024-10-26 14:52:01  INFO: [T1e39e59f] connected
2024-10-26 14:52:01  INFO: [T1e39e59f: startek < 184.105.139.69] <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' xml:lang='en-US' to='.' version='1.0'>
2024-10-26 14:52:05  INFO: [T1e39e59f] disconnected
2024-10-26 15:12:21  INFO: [Taad1485d] connected
2024-10-26 15:12:21  INFO: [Taad1485d: startek < 184.105.247.195] <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' xml:lang='en-US' to='.' version='1.0'>
2024-10-26 15:12:25  INFO: [Taad1485d] disconnected

Is there something I'm just overlooking here? Thanks in advance

The log you provided doesn't make any sense. It's not even the right ports.

It's from tracker-server.log, is there somewhere else I need to be looking?

That's the right file.

Looking a little closer, I'm getting a ton of logs related to protocols I'm not using. This server only has a single device on it which is set to gl200 using the info in my original post. Does Traccar attempt to try other protocols if one fails? This isn't making sense.

Traccar doesn't try other protocols. It's probably just some noise. So you need to find the relevant logs for your device.

You can disable unused ports if you want.

Reading past posts, it looks like that would be done by explicitly setting the port and protocol in traccar.xml - is that correct? Because I already have this set in mine:

<entry key='gl200.protocol'>gl200</entry>
<entry key='gl200.port'>5004</entry>

<entry key='protocols.enable'>gl200</entry>

Ah missed that thank you. That seems to have stopped the noise but the device is going on 18 hours disconnected and I'm not sure why.

If there's nothing in the logs, it's probably some device or network issues.