DriverUniqueId invalid data
It's possible that this is the value the tachograph is sending the FMC650. You can probably remove the attribute when it contains NUL using computed attributes.
Yeah, it sounds like the device is still sending the data. Do you have HEX sample?
{
"priority": 0,
"sat": 42,
"event": 187,
"io183": 0,
"io186": 0,
"io184": 0,
"io185": 0,
"io187": 0,
"io188": 0,
"io189": 0,
"io190": 0,
"io191": 0,
"io194": 1769507127,
"io192": 750156385,
"io193": 4866910,
"io196": 0,
"io195": 0,
"io198": 0,
"io197": 0,
"driverUniqueId": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000",
"distance": 0.0,
"totalDistance": 914850.1733627744,
"motion": false
}
io187 and io188 (respectively 'Driver 1 Card Presence' and 'Driver 2 Card Presence') are 0 and
io195, io196, io197, io198 (Driver 1 ID MSB,Driver 1 ID LSB, Driver 2 ID MSB,Driver 2 ID LSB) are correctily 0,
Everything seems to suggest that the error is in the mapped driverUniqueId field.
That's not HEX.
I haven't HEX at this moment, store rawdata is not enable in my conf, but i posted, the entire content on attributes field stored by traccar into DB.
It should be in logs.
On teltonika devices es. FMC650, when driver tacho card is not present, in json 'attributes' field driverUniqueId appear like this:
"driverUniqueId": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000"
\u0000 the null character is repeated, but when data is not present, driverUniqueId should not simply appear in json 'attributes' field