Drivers

A driver record associates a name with a driver identifier. It is separate from a user account: creating a driver does not create a login or grant access to devices.

Device-reported identification

Driver identification depends on the tracker and protocol. A device might obtain an identifier from an RFID reader, an iButton or another supported input. Traccar stores the decoded identifier in the position's driverUniqueId attribute.

1. Confirm that a position received from the device contains driverUniqueId. Use the Positions report to inspect position attributes.
2. Open Settings > Drivers and create a record with a name and an identifier matching the reported value exactly.
3. Link the driver to the relevant device or group through Connections.
4. Assign the driver record to users who need access to it through Settings > Users > Connections.

By default, the device reports who is driving. To assign a driver when the device does not report one, use the setting below.

Linked-driver fallback

For deployments where the tracker does not report driver identification, the server can fill in the identifier from a linked driver:

<entry key='processing.useLinkedDriver'>true</entry>

Add this to the configuration file and restart Traccar. It fills in driverUniqueId on new positions when the device has not supplied one. Link only one driver to each device, including drivers linked through groups, so the assignment is unambiguous.

Driver Changed events

Traccar generates a Driver Changed event when a position has a driver identifier that differs from the previous position's identifier. To receive a message, configure the corresponding notification.

If names are missing, compare the reported driverUniqueId with the driver record and check user access. If the identifier never changes, inspect the tracker configuration and incoming data; creating additional driver records alone does not change the identifier reported by the device.