[HELP] Traccar “Unknown device” with Mictrack MT710

My MT710 sends to 5030/tcp and Traccar detects mictrack, but messages are rejected as “Unknown device.”

Log sample:

INFO: [Txxxx: mictrack < 18.159.xx.xx] #866392069989303#MT710#0000#AUTO#1
#4216$GPRMC,121530.00,A,4005.8351,N,00212.4729,W,,192.70,051025,,,A*5F
##
WARN: Unknown device - #866392069989303#MT710#0000#AUTO#1

Unique IDs tried (no luck):

• 866392069989303 (IMEI only)
• #866392069989303#MT710#0000#AUTO#1
• 866392069989303#MT710

Also tried database.registerUnknown=true → still not auto-created.

Device / network:

• MT710, FW SV: V2.1.8, APN iot.1nce.net, NWM:0,0,0, NET:TCP
• SRV: ona.elrocho.es:5030 (raw TCP, no proxy/tunnel)
• tcpdump confirms payload reaching port 5030 from public IPs.

Question:
What Unique ID does the mictrack decoder expect for MT710 in current Traccar?
Is any extra server property needed, or should I use a different protocol/port for this model?

(Also tried to add the device in demo.traccar.org without success.)

Something doesn't add up. Port 5030 is TLT-2H. Mictrack port is 5191. What you have in the logs is TLT-2H format, but for some reason it shows mictrack port. So either you misconfigured port on the device or you misconfigured port on the server.

Thanks! You were right — it was a port/protocol mix-up on my side.

• My MT710 was sending frames like #866392069989303#MT710#0000#AUTO#1 ... $GPRMC...##, i.e. TLT-2H format.
• I had configured the server with <entry key='mictrack.port'>5030</entry>, so Traccar was labeling the connection as “mictrack” on 5030, but the payload was actually TLT-2H.
• To make it worse, earlier I briefly had a Cloudflare Tunnel that was proxying HTTP to port 5030, which added noise (GET / in the logs). I removed that and exposed raw TCP.

Fix:

• Switched config to <entry key='tlt2h.port'>5030</entry> (and removed mictrack.port).
• Opened 5030/TCP directly (router/NAT + UFW).
• Kept Unique ID = IMEI (866392069989303).

After that, the device came online immediately and positions decode fine.

Appreciate the nudge — the hint about 5030 = TLT-2H vs 5191 = Mictrack was exactly the issue.

Port 5030 is the default for tlt2h, so you don't need to change anything in the config at all.

Thanks a lot for the quick help and the clear guidance. Really appreciate the support you provide here, especially for newcomers like me

Try UDP to reduce the bandwidth ~2x. Traccar supports it after this update:
https://github.com/traccar/traccar/issues/5307

Thanks, I'm already using UDP and I actually see less jumps in the results, I think everything is working correctly now

That's great! Just getting used to mine again after a long time of not using.

Question for this group, on v6.1 i am finding the same looks like the MT710 is having issues
my config is <entry key='tlt2h.port'>5030</entry>,

But i feel my traccar server is not decoding correctly
Seems now not to be reporting battery

I am running the server on a ec2 machine, never had an issue but now seem to be having issues

Logs?