GT06 powerOn/Off alerts

Grupo Datasoft Ltda.9 days ago

Hello everyone, happy day!

I'm facing a problem. I use Traccar 5.0, and most of my devices work with the gt06 protocol. Lately, I've noticed that the engine on and off times aren't being saved correctly in the tc_events table. Sometimes they are, sometimes they aren't. Although I can correctly see the ignition=True and ignition=False values ​​in the tc_positions, they are correctly displayed. However, this isn't reflected in the tc_events table. The insertion of these two alarms into this table is unstable. The strange thing is that the other events are inserted almost online and without any problems. Where could the problem be?

In parallel, I'm also testing and receiving alerts via SMS, and they all arrive without any problems via SMS...

It only happens to me with this protocol. Any ideas?

Esto es lo que contiene el registro de tc_positions cuando hago un apagado (se insertan dos registros en tc_positions) y no se inserta la alerta en tc_events:

When the event is successfully inserted into the tc_events table:

tc_positions:

1101716764	2025-05-22 16:45:18	gt06	63529	2025-05-22 16:45:19	2025-05-22 16:45:19	2025-05-22 16:44:01	1	3.3847294444444445	-76.54295111111111	0	0	0		{"status":68,"ignition":false,"charge":true,"blocked":false,"batteryLevel":100,"rssi":4,"raw":"78780a1344060400020040ee590d0a","distance":0.0,"totalDistance":46155.95,"ip":"190.130.115.53","motion":false,"hours":9724957000}	0	null	
1101717790	2025-05-22 16:45:20	gt06	63529	2025-05-22 16:45:20	2025-05-22 16:45:17	2025-05-22 16:45:17	1	3.3847183333333333	-76.54294222222222	0	0	0		{"sat":7,"raw":"787829a0190516152d11c7005cf6cd08365090001c0002dc01000069840000000009564d640003000041fed50d0a","distance":1.58,"totalDistance":46157.53,"ip":"190.130.115.53","motion":false,"rssi":4,"hours":9724957000}	0	{"radioType":"gsm","considerIp":false,"cellTowers":[{"cellId":6915072,"locationAreaCode":0,"mobileCountryCode":732,"mobileNetworkCode":1}]}

tc_events:

974648	ignitionOff	2025-05-22 16:45:18	2025-05-22 16:45:19	63529	1101716764		{}		0	0	0000-00-00 00:00:00

When the event is NOT inserted into the tc_events table:
tc_positions:

1101980199	2025-05-22 16:52:16	gt06	63529	2025-05-22 16:52:17	2025-05-22 16:52:13	2025-05-22 16:52:13	1	3.3842083333333335	-76.54288888888888	0	1.07991	179		{"sat":6,"raw":"787829a019051615340dc6005cf33708365030021cb302dc01000069840000000009564d64000300005bf9dd0d0a","distance":14.93,"totalDistance":46325.26,"ip":"190.130.115.53","motion":false,"rssi":4,"hours":9724957000}	0	{"radioType":"gsm","considerIp":false,"cellTowers":[{"cellId":6915072,"locationAreaCode":0,"mobileCountryCode":732,"mobileNetworkCode":1}]}	
1101982347	2025-05-22 16:52:20	gt06	63529	2025-05-22 16:52:20	2025-05-22 16:52:18	2025-05-22 16:52:18	1	3.3842355555555557	-76.54288	0	0	179		{"sat":6,"geofence":0,"raw":"78782da4190516153412c6005cf36808365020001cb31002dc01000069840000000009564d64440604ff00ff005c65a50d0a","distance":3.19,"totalDistance":46328.45,"ip":"190.130.115.53","motion":false,"rssi":4,"hours":9724957000}	0	{"radioType":"gsm","considerIp":false,"cellTowers":[{"cellId":27012,"locationAreaCode":256,"mobileCountryCode":4098,"mobileNetworkCode":220}]}
Anton Tananaev9 days ago

I recommend upgrading.

RastreameMX4 days ago

Hi good day.

@Grupo Datasoft Ltda. , in some of the positions you shared, attribute ignition is being reported, and in other some it is not being reported. That's common on some GT06 devices . Depending device you are using, you need to look if your device allow to report on extended format. By example, J16 chinese trackers by default reports on huabao protocol, if you change them to GT06 protocol (PTL_SEL=2) device indeed reports on GT06, but some attributes are missing on some positions sent to the server (just as your trouble). So, when device is configured as GT06 protocol, you need to specify GT06SEL=1 too (1 is like extended protocol, 0 is basic protocol). This is just an example.

You need to look into your device documentation, to see if it have extended GT06 protocol report programming, because to trigger ignition off event, is required to get at least one position with "ignition=false". Same to trigger ignition on event (ignition=true). When GT06 is not reporting extended, and if the position that contains ignition change get lost on the way to server (connection issues, by example), event is not being triggered.

And same that Anton told you, it's recommended to update your traccar, version 5.0 it's really old.

Greetings.