I need protocol documentation that clarifies that 101 is the SOS alarm.
With the documentation here:
See the page 17, please. Thanks!
I don't see anything about 101. The alarms from that page are already supported.
Well, maybe I can not explain it well. When I press the SOS button on my tracker, it does not send the alarm in the "alarm" field, so Traccar does not activate the web notification. What the tracker does is send it in the "terminal information" field (page 17). "101" (65 hex, 01100101 bin), then bits 3 to 5 contain the SOS (100: SOS) information. That's what I meant, I hope you understand. Thank you
I have just check your original HEX and it has 0x00 in the status field.
I think it has 0x00 in the "alarm / language" field. The status field ("Terminal Information Content" according to the documentation) is the one that is now containing the alarm information of my tracker. I think.
7878251611030C152E27CB042BED5206A91E320038FF0902D2361FAA002EEA6500640001004B1DBF0D0A // SOS Alarm!
I can see the problem now. Traccar only decodes alarm field at the moment.
Hello Anton, I'm testing a GT06 Accurate on port 5023 with the GT06 protocol. I have been able to connect it to Traccar without problems, but when I send an SOS, the web notification does not work. What I see is that the STATUS field receives an SOS (Status 101), but it does not seem like an alarm. This is the SOS message:
It seems to me that my tracker does not send the alarm data in the field that Traccar
Decodifies ("alarm / language"), it does so only in the "terminal information content" (according to protocol documentation). It's a decoding problem, I think, I'm testing. Thank you