How make the server answer a specific response?

Hi. I am having disconnecting issues with pet trackers (more than one, all identical, working on port 5015). Working with two different providers, both of them, via sniffing my traffic, are telling me that the problem is that the server give wrong answer to some strings sent from the trackers. Please find attached a screenshot of the sniffer.
Both providers told me that I need to make the server to answer (automatically) the tracker with "8001" when the trackers send:

1. Provider 1: 7E 0F A0 00 08 01 91 75 67 39 02 00 16 00 00 00 00 00 00 2B 00 23 7E
2. Provider 2: 7E 0F A0 00 08 01 91 75 67 39 02 01 B3 00 00 00 00 00 00 2C 00 80 7E

Is it feasible to program a specific response from the server to a specific string received from the trackers?

Thanks.

Please provide the protocol documentation and full connection session log.

Hi. Sorry for the delay. I was held in a health issue. I am enclosing here what you ask.
Thanks.
https://drive.google.com/file/d/1K3qArwzLE7xE0ImS4-EUWPg3HG3hvGPF/view?usp=drive_link, https://drive.google.com/file/d/1cvR3XoEqhlX9sjFkrqBxdcd_L1Ase90S/view?usp=drive_link

David.-

This doesn't look like Traccar logs.

Oh, I thought you were referring to the sniffer log. Here you can find the full day log (it´s not gigantic; we are just in test phase), and also what I think it is the part of the log during the time that it was sniffed. I say THINK because it involves my local time (Chile), server´s time (USA) and the sniffer time (Mainland China). I gave it a few minutes before and after.
THANKS!

https://drive.google.com/file/d/1EI-FI6qSrP2yptvHFz7tACIZYxfVA3FS/view?usp=sharing, https://drive.google.com/file/d/1ln8ewtD7UW2Z6zkrsN1UVYMumqGv-k2j/view?usp=sharing

I don't see anything about message type 0x0fa0 in the protocol documentation. Is the document incomplete/incorrect?

You are completely right. I will dig into it and come back. Thanks.

This is a subset (perhaps more updated) of a few commands. Please see line 29.

https://docs.google.com/spreadsheets/d/11Jbwbudf-DF5uW9grk7RghKfTH9CKjuc/edit?usp=sharing&ouid=106711162848733147957&rtpof=true&sd=true

David.-

OK, this one does seem to mention it, but nothing about ACK response format.

Hi Tananaev. I was discussing it with the tracker manufacturer, and he told me:
"The 0FA0 data is a customized data packet for pets. When used as a heartbeat packet, the customer platform needs to add an additional protocol to obtain the complete data
If the server does not respond to the 0x0fa0 packet, it will not be able to obtain the charging status, buzzer, sound, and other status, as this packet contains this information
Check this ,this is not difficult".

Also, he sent me the picture you can see attached.

I´ve downloaded the suggested file as well: https://drive.google.com/file/d/1jgQytSmnyoXt1lhhrgG6t6gRJ9wKo7SP/view?usp=sharing

Thanks.

What document is this picture from? Why is it not part of the official protocol documentation?

I feel Chinese manufacturers are not too happy to share all of their information. They give me it drop by drop.
Please kindly see the attached file I just got my hands into.
Specially rows 158 to 167.

https://docs.google.com/spreadsheets/d/1PySxMVfd5K1KfPZohZXD87q0l_3EPONb/edit?usp=sharing&ouid=106711162848733147957&rtpof=true&sd=true

I guess this sheds some light about it.

OK. We don't support it currently, so there are 3 main options to proceed:

1. You can submit a pull request with the change to support this.
2. You can file a file a feature request for us to support it. Note to prioritize we would need to see a significant interest in this.
3. Use our professional services to implement it.