Weired characters after HexDecode of tracker-server.log
There is a reason for logging data in HEX format. It's a binary message, so using HEX decoder for it doesn't make any sense.
I don't think it's a message from your VT300 or even Traccar Client app.
Well, this is somehow funny. I wiped cache and App data for the Client App on Android and set server and port again. After that, it worked immediately - without touching the server in any way (17:21:34 in the log).
2017-05-08 17:21:34 DEBUG: [DB854CE9: 5055 < 89.183.57.78] HEX: 474554202f3f69643d3835383537342674696d657374616d703d31343934323536383934266c61743d35322e3439323233393434266c6f6e3d392e38393434393934352673706565643d322e313338323238343436333434383532342662656172696e673d3334372e3339393939333839363438343426616c7469747564653d3131352e3026626174743d33322e3020485454502f312e310d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f696420372e312e313b204f4e45504c5553204133303033204275696c642f4e4d46323646290d0a486f73743a20766f622e64646e732e6e65743a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a0d0a
2017-05-08 17:21:34 DEBUG: [DB854CE9: 5055 > 89.183.57.78] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2017-05-08 17:21:34 INFO: [DB854CE9] id: 858574, time: 2017-05-08 17:21:34, lat: 52.49224, lon: 9.89450, speed: 2.1, course: 347.4
2017-05-08 17:22:05 INFO: [33350EA4] connected
2017-05-08 17:22:06 DEBUG: [33350EA4: 5055 < 89.204.137.182] HEX: 2424007e8621700173878099553136303231302e3030302c412c353232392e353234322c4e2c30303935332e363732352c452c302e30302c3130312c3037303531372c2c2a30337c302e397c35307c323030307c303030342c303030347c303130363030303732384136424639397c31337c303235384546413322d30d0a
2017-05-08 17:22:06 WARN: [33350EA4] error - empty text - IllegalArgumentException (...)
2017-05-08 17:22:06 INFO: [33350EA4] disconnected
Now my VT300 acts a little different (17:22:06 in the log). Hex-decoding the DEBUG info give me
$$????U160210.000,A,5229.5242,N,00953.6725,E,0.00,101,070517,,*03|0.9|50|2000|0004,0004|0106000728A6BF99|13|0258EFA3??
Is this correct Meiligao protocol?
Thank you for your support. :)
And you are still doing it. There is no need to post "decoded" message.
As for the protocol, it does look like Meiligao. Not sure why you don't just try it yourself.
Hi, I don't get it.
I installed Traccar Server for Linux on Raspian / Apache (latest versions each), created port forwarding on my router, everything went well and runs smoothly. Except: My devices aren't tracked.
I was looking for information in the tracker-server.log when the devices are connecting. But after Hex-Decoding here: https://www.traccar.org/hex-decoder/
It's looking like this:
This is the same for my VT300 device as well as for the Android App.
I connected to 5055 Port with my browser and got these usual http header information - this OK.
But what is happening for the devices?
Any idea?
Thank you in advance and kind regards..
VoB