False Ignition On/Off Notifications – Seeworld R12L (GT06 protocol)

Hello everyone,
I am currently facing an issue with a Seeworld R12L GPS device using the GT06 protocol in Traccar.

The problem is that Traccar generates Ignition On and Ignition Off notifications that do not reflect the real vehicle status.

The vehicle remains turned on, and the ACC line is properly wired and physically stays ON. However, Traccar intermittently generates Ignition Off events while the engine is still running.

This creates incorrect ignition state transitions in the system, even though the vehicle ignition never changes.
Device details:
Manufacturer: Seeworld
Model: R12L
Protocol: GT06
Ignition source: ACC wired directly to vehicle ignition

I am sharing the official protocol documentation provided by the manufacturer for reference.
https://www.traccar.org/protocol/5023-gt06/GT06_GPS_Tracker_Communication_Protocol_v1.8.1.pdf

I would like to understand:
Whether this could be related to how Traccar interprets the ACC or ignition value from this specific device.

If there are known compatibility issues between Seeworld R12L and the GT06 decoder.

If any specific server configuration parameter could help improve ignition detection accuracy.

If needed, I can also provide raw hexadecimal logs from the device for further analysis.

Any guidance or feedback would be greatly appreciated.

Thank you in advance.

You have to provide logs.

Reportes
Registros

Identificador	Protocolo	Datos
354778342368134	gt06	78781f121a03010f2815cb007f451f07f2e0c2285d22000000000000000000d8944b0d0a

354778342368134	gt06	78781f121a03010f281fcb007f479a07f2e75c265d22000000000000000000d920cf0d0a

354778342368134	gt06	78781f121a03010f2829cb007f498507f2ecd1275d22000000000000000000da00790d0a

354778342368134	gt06	78780a134605640f0200dbec8f0d0a

354778342368134	gt06	78781f121a03010f2833cb007f4cb607f2f40f2e5d2b000000000000000000dcd02f0d0a

354778342368134	gt06	78781f121a03010f2901cb007f51c407f2faad355d3b000000000000000000ddf2620d0a

354778342368134	gt06	78781f121a03010f290bcb007f59d407f3009d3b5d47000000000000000000de02e20d0a

354778342368134	gt06	78781f121a03010f2915cb007f62fb07f30683405d46000000000000000000df9beb0d0a

354778342368134	gt06	78781f121a03010f291fcb007f6bb207f30c2d325d47000000000000000000e01a510d0a

354778342368134	gt06	78781f121a03010f2929cb007f738e07f31119385d47000000000000000000e1afe70d0a

354778342368134	gt06	78781f121a03010f2933cb007f7bc707f3164d355d4a000000000000000000e254990d0a

And have you verified it against the documentation? Which ones are incorrectly decoded as ignition on/off when you didn't expect it?

I haven't done it; my knowledge doesn't extend that far at the moment.

Well, at the very least you have to tell us which of those log samples returned incorrect results.

354778342368134	gt06	78781f121a03010f2915cb007f62fb07f30683405d46000000000000000000df9beb0d0a

354778342368134	gt06	78781f121a03010f291fcb007f6bb207f30c2d325d47000000000000000000e01a510d0a

354778342368134	gt06	78781f121a03010f2929cb007f738e07f31119385d47000000000000000000e1afe70d0a

354778342368134	gt06	78781f121a03010f2933cb007f7bc707f3164d355d4a000000000000000000e254990d0a

These are the ones that generate the event that is not real.

I just tested all of those samples and they all decode to ignition false.

The app is generating ignition on and off events. The vehicle has been running for more than 2 hours.

My interpretation is that 7878 1f 12 is a GPS and LBS packet and contains no ignition information. You might want to enable copy attributes in the Traccar configuration file:

  <entry key='processing.copyAttributes.enable'>true</entry>
  <entry key='processing.copyAttributes'>ignition</entry>

Don't forget to restart the Traccar server.