Suntech ST300 sends Driver ID, but Traccar does not set driver state (attribute copy is misleading)

Halisson a day ago

Hello everyone,

I’m troubleshooting a Suntech ST300 + Traccar setup related to driver identification and would like to confirm whether this behavior is expected.

Scenario

Device: Suntech ST300

Protocol: Suntech (ST300STT / ST300ALT)

Driver ID example: 0104CE0A010000

Traccar running in Docker

Firmware updated by Suntech to support driver ID

Log evidence (raw data received by Traccar)

Below are real log lines directly from Traccar, filtered by device ID:

2026-01-08 15:54:44  INFO: [T9f302ac4: suntech < 200.233.216.60] ST300ALT;807600942;45;319;20110101;00:01:29;117751;-12.427132;-038.330010;000.000;000.00;0;0;96492293;12.25;100010;59;117902;0.0;0;0104CE0A010000;1
2026-01-08 15:54:45  INFO: [T9f302ac4: suntech < 200.233.216.60] ST300ALT;807600942;45;319;20110101;00:01:34;117751;-12.427132;-038.330010;000.000;000.00;0;0;96492293;12.29;100000;60;117902;0.0;0;0104CE0A010000;1
2026-01-08 15:54:47  INFO: [T9f302ac4] id: 807600942, time: 2010-12-31 21:01:29, lat: -12.42713, lon: -38.33001, course: 0.0
2026-01-08 15:54:48  INFO: [T9f302ac4] id: 807600942, time: 2010-12-31 21:01:34, lat: -12.42713, lon: -38.33001, course: 0.0
2026-01-08 15:56:04  INFO: [T9f302ac4: suntech < 200.233.216.60] ST300STT;807600942;45;319;20110101;00:04:02;117751;-12.427132;-038.330010;000.000;000.00;0;0;96492293;12.25;100000;2;0001;117905;0.0;1;0104CE0A010000;1
2026-01-08 15:56:07  INFO: [T9f302ac4] id: 807600942, time: 2010-12-31 21:04:02, lat: -12.42713, lon: -38.33001, course: 0.0
2026-01-08 15:57:13  INFO: [T9f302ac4: suntech < 200.233.216.60] ST300STT;807600942;45;319;20110101;00:05:02;117751;-12.427132;-038.330010;000.000;000.00;0;0;96492293;12.25;100000;2;0002;117906;0.0;1;0104CE0A010000;1
2026-01-08 15:57:17  INFO: [T9f302ac4] id: 807600942, time: 2010-12-31 21:05:02, lat: -12.42713, lon: -38.33001, course: 0.0
2026-01-08 15:58:03  INFO: [T9f302ac4: suntech < 200.233.216.60] ST300STT;807600942;45;319;20260108;18:57:47;117751;-12.427132;-038.330010;000.000;000.00;2;0;96492293;12.25;100000;2;0003;117906;0.0;1;0104CE0A010000;1
2026-01-08 15:58:06  INFO: [T9f302ac4] id: 807600942, time: 2026-01-08 15:57:47, lat: -12.42713, lon: -38.33001, course: 0.0

What we see

The driver ID is clearly present in the raw packets (0104CE0A010000)

Data is consistent and continuously sent

Traccar receives and parses the message, but…

What Traccar does NOT do

No driverUniqueId is created

No real-time driver state

No native driver association

Attribute copy workaround (problematic)

Using attribute copy / custom attributes, we can:

Show a driver ID in the UI

But this causes serious issues:

❌ Not real-time

❌ UI may show a driver while someone else is actually driving

❌ No proper driver history or reports

❌ Only visual, not functional

Question to the community

Is this behavior expected for the Suntech protocol?
Is there an official way for ST300 to send the driver ID as a native Traccar driver (driverUniqueId), or is custom protocol parsing the only correct solution?

Thanks.

Anton Tananaev a day ago

What's your configuration. I believe Suntech protocol requires a bunch of configuration params if you need advanced attributes.

Halisson a day ago

Hi Anton, thanks for the reply.

The configuration has already been reviewed together with Suntech technical support, following the official documentation, and the firmware was updated by the manufacturer.

Summary:

Suntech ST300

Suntech protocol (ST300STT / ST300ALT)

Firmware with driver ID support

Driver ID (0104CE0A010000) is consistently present in the raw packets

Traccar receives the data, but it is not mapped to driverUniqueId, so no native driver state is created.
We tested attribute copy, but it is not real-time and may display an incorrect driver.

The question is straightforward:
Is there any specific Suntech parameter that allows the driver ID to be recognized as a native Traccar driver, or is custom protocol parsing currently the only correct solution?

If there is any recommended set of parameters for advanced attributes / driver handling, I’m happy to validate it.

Thanks.

Anton Tananaev a day ago

I think you misunderstood. I'm talking about server configuration.