Driver ID by association with an EYE Beacon
You can create a computed attribute for the driverUniqueId using that attribute.
Thanks for the answer!
Will it be possible with advanced expressions to parse the various EYE Beacons MAC's from the unparsed io10828 string and store them in an ArrayList,and then compare each one with the MAC from the driver's attributes to confirm the correct driver on the FMC150 attributes?
We only support single driver id currently, so you won't be able to use multiple values.
My goal is not to have more than one driver id. I would create separate drivers, each with a MAC address of their beacon in the attribute field, and these would be associated with their corresponding devices. Then the driver would be confirmed if its own MAC was found within the io10828.
Then you probably have to adjust the source code.
Ok, thanks for helping!
By the way, just because I'm not very acostumed with the source code, would you recommend doing these changes on the Teltonika protocol files, or is there any other place I would do this?
Hi, João. Can you help sharing your traccar configuration and device configuration?
Sorry, but what traccar specific configurations are you talking about?
I'm sorry, João.
Im trying to configure a FMC150, but I don't know how to do it. We connected the device using OBD port and we want to monitoring all CAM information that we can collect, but we only get the basics GPS tracking.
The question is: can you share me you traccar and teltonika configuration?
Thank you for your feedback.
I get what you are trying to do, but I only configured my FMC150 to send the localization and I'm now trying to make the EYE Beacon associate with a driver. I haven't explored the CAM capabilities of traccar with the Teltonika devices, but I would say that if your device was correctly configured, traccar would automatically detect most of the CAM info. With this in mind, you might have some Teltonika configurations wrong.
I'm trying to associate drivers to a Teltonika EYE Beacons so I can track statistics per driver. The EYE Beacon already reports an event to the FMC150 on io10828, with a string that has the MAC address of the Beacon.
I was thinking I could somehow use the driver atribute field to save the Beacon's MAC address and then later compare it with the io10828 event to confirm the driver. Is this something that can be done with computed attributes, or is there other way of doing it?
Thanks,
João