Does anyone identifies this HEX?

2a68712c3335363332373038303533383332322c5650312c562c3230322c3030352c37342c35313435352c305933322c31383936362c34305937342c35323434352c333523

the hex decode is:

*hq,356327080538322,VP1,V,202,005,74,51455,0Y32,18966,40Y74,52445,35#

Yes, it's H02 protocol, port 5013.

Thank you Anton! I have already configured the device to send to 5013, and I have created a new user with identifier the IMEI of the device. Unfortunately, the user doesn’t come to online state, although server receives messages to port 5013. Do you have any idea what is happening?

What version of Traccar are you using? Where are the logs?

Hello, Anton and thank you for everything.
I bounce on this post.

I have a device H02, configure at first with the port 5001.

sudo tail -f /opt/traccar/logs/*.log | grep 5001
2018-09-11 11:01:43 DEBUG: [0b7b29ab: 5001 <160.154.128.93] HEX: 2a68712c3335363332373038303537303035312c5650312c562c3631322c3030332c3331302c393836332c30593331302c393836312c3335593331302c31303737332c323123

I find in the logs the converted exa code:

* Hq, 356327080570051, VP1, V, 612,003,310,9865,0Y310,9861,37Y310,9863,34 #

Normally it is the protocol H02 with the difference VP1 instead of V1 ...
when I configure the port in 5013 and did not declare in the server, I do not see any "Unknown device" in the logs.
And if I declare the device in the server it stays offline.

Traccar Server 4.0 on debian
Do you have an idea of ​​my problem?

Cédric

It is H02 protocol.

Thank you for your return.
But I do not understand why when I program the device on port 5013 I do not see anything in the logs

My device is actualy configured on the demo.server 5 :
52.232.22.124:5013 with the IMEI : 356327080570051

Probably the format is slightly different and we need to modify decoder.

Thank you Anton,
what is the decoder file please.
Cédric.

for my traccar platform