It is because your device is reporting driver id, or at least we interpret it as one.
Thanks Anton.
But the device hasn't changed and I haven't done any firmware update on it. The only change is the upgrade to traccar from 6.2 to 6.4.
An additional change that I see is the format of the event JSON. Here is a snippet. The event JSON is not recording powerOff alarms anymore. The powerOff event is now showing in the position attributes.
Is this an intended change? I couldn't find any references to it.
{
"event": {
"id": 2757,
"attributes": {
"driverUniqueId": "3338067"
},
"deviceId": 2266,
"type": "driverChanged",
"eventTime": "2024-09-08T14:14:34.000+00:00",
"positionId": 29467,
"geofenceId": 0,
"maintenanceId": 0
},
"position": {
"id": 29467,
"attributes": {
"alarm": "powerOff",
"ignition": false,
"motion": false,
"blocked": false,
"charge": false,
"odometer": 20700,
"rssi": 26,
"sat": 0,
"driverUniqueId": "3338067",
"batteryLevel": 242,
"iccid": "89914906200085753637",
"adc1": 65535,
"adc2": 65535,
"distance": 0.0,
"totalDistance": 0.0
},
"deviceId": 2266,
"protocol": "huabao",
...
...
...
Hi,
Below is the log output.
I don't have any drivers configured in the system, but I see a lot of these
driverChanged
events. This started after upgrade to 6.4.Any thoughts on why this might be happening?