Samsara Integration is a 1.5 way integration with DRTrack, first introduced in Jan 2020 (2019.4 release). This integration enables Samsara devices and DRTrack to communicate with each other through Samsara Cloud, a web-based dashboard. Drivers will be able to view planned route data transmitted to devices, while GPS points and stop events are transmitted from DRTrack to Samsara Cloud to record trip details.
- Create a Windows Sync Service
- Adding Devices and Drivers
- Route Login Event
- Stop Arrival Event
- Stop Departure Event
- Route Log Off Event
- Samsara Integration FAQs
Create a Windows Sync Service
You will need to have an existing Samsara account with a Login ID, and a desktop or laptop computer with internet access and browser. We recommend Google Chrome, which you can download here.
Windows Sync Service will need to be created on the same server that is host to both the DRTrack URL site and Samsara Cloud Sync Service.
1. Download/Save contents of Samsara Cloud Sync Service in new folder named SamsaraSync
2. Open the Windows command prompt and type the following:
sc create DRTrackSamsaraSync binpath= "<actual path to .exe in SamsaraSync folder>"
Note: You must have a space after binPath= and quotation marks around the actual exe path.
3. Go to DRTrack Admin→ Site→ Settings & Configuration and update the following INI settings:
- EnableSamsara = TRUE
- SamsaraGpsApiUrl = https://api.samsara.com/v1/fleet/locations
- SamsaraToken = (assigned automatically by Samsara, and will replace the default settings)
- SamsaraGroupId = (assigned automatically by Samsara, and will replace the default settings)
- SamsaraAssignDriverApiUrl = https://api.samsara.com/v1/fleet/drivers/
- SamsaraUpdateRouteApiUrl = https://api.samsara.com/v1/fleet/dispatch/routes
The Samsara Integration with DRTrack is now complete.
Adding Devices and Drivers
Device Records can be added or deleted in DRTrack (Device Manager), or in Samsara Cloud. Device information is communicated both ways (2-way) between DRTrack and Samsara.
Driver Records should be entered in DRTrack (Driver Manager). Driver information is only communicated one-way, from DRTrack to Samsara. (Two-way communication is expected in future updates)
If drivers are added in Samsara and not in DRTrack, then the routes should be exported from DRTrack to Samsara without driver assignments. Drivers can then be manually assigned to a route in Samsara.
Routes can be exported from DRTrack to Samsara with device and driver pre-assignments already made, without having to first enter the device or driver records in Samsara Cloud. When Samsara receives a pre-assigned route and the driver and/or device record is not already in Samsara, the device and/or driver Record will be automatically created by Samsara.
Routes created in DRTrack can be assigned drivers and devices before export to Samsara Cloud. After the routes have been successfully exported, drivers can view assigned routes on their devices after they’ve logged in.
Route Login Event
When Auto Login Pre-assignment task is enabled in DRTrack for the branch, Scheduled Task will run periodically (5 minutes) to look for any pre-assigned routes. When pre-assigned routes are found, DRTrack will create a Route Login event based on the pre-assignment data.
If a driver logs in to a pre-assigned route on a mobile device and an Auto Login has occurred for the same route by a Scheduled Task, then the time stamp for Route Login event will reflect the earliest time as the actual event time in DRTrack.
Stop Arrival Event
When GeoFence Stop Detection is enabled, DRTrack will record a Stop Arrival event when the Lat/Long GeoFence is breached by arrival of the driver at a scheduled stop on the assigned route. The timestamp of the event will reflect as the actual Stop Arrival time DRTrack.
Stop Departure Event
When GeoFence Stop Detection is enabled, DRTrack will record a Stop Departure event when the Lat/Long GeoFence is breached by departure of the driver at a scheduled stop on the assigned route. The timestamp of the event will reflect as the actual Stop Departure time in DRTrack.
Route Log Off Event
When GeoFence Stop Detection is enabled, DRTrack will record a Route Log Off event when the Lat/Long GeoFence of the end terminal is breached by return of the driver after route completion. The timestamp of the event will reflect as the actual Route Log Off time in DRTrack.
When Auto Log Off task is enabled in DRTrack for the branch, Scheduled Task will run periodically (5 minutes) to look for routes with Auto Log Off enabled. When routes with Auto Log Off are found, DRTrack will create a Route Log Off event based on the Auto Log Off data.
If a driver logs off upon return to the terminal and an Auto Log Off occurs for the same route by Scheduled Task, then the time stamp for Route Log Off will reflect the earliest time as the actual event time in DRTrack.
Samsara Integration FAQs
Where should drivers be entered; Samsara Cloud or DRTrack?
Enter drivers in DRTrack.
With current integration, driver information flows in one direction only; DRTrack will update driver records in Samsara. If entered in Samsara first, records should be manually input in DRTrack.
Samsara/DRTrack customer reports that drivers are showing in Samsara Cloud but not in DRTrack.
1. Delete drivers from Samsara Cloud.
1. Add drivers in DRTrack.
3. Run Sync service (manually or automatic).
4. Verify that driver info was updated in Samsara
Sync is currently set to run automatically every 10 hours.
How do I handle drivers that were input into Samsara Cloud first?
Export the unassigned route from DRTrack to Samsara.
Manually assign the route in Samsara.
Where should devices be entered; Samsara Cloud or DRTrack?
Devices can be entered in either DRTRack (recommended) or Samsara.
With current integration, device information flows in both directions between DRTrack and Samsara.
What mobile device type(s) can be used with Samsara/DRTrack Integration?
Device does not appear in the correct branch in DRTrack
Check DRTrack Device Manager to find where (branch) the device is assigned; reassign it to the correct branch.
Check the sync settings to see if devices are automatically assigned to the default branch. Correct if necessary.
How do I delete/remove a device?
Delete device in DRTrack.
Deactivate device in Samsara.
DRTrack: Use Device Manager to locate the device and delete it.
Samsara: In Samsara Dashboard, go to Settings > Gateways. Find the device in the table. On the right side of the table, select the three dots then Deactivate Gateway.
What information is required in a JIRA ticket to report an issue with a device/driver?
1. DRTrack site URL
2. Self hosted or no?
3. Device/Driver ID
4. Was device/driver manually input in DRTrack or Samsara?
5. Samsara Login ID
6. Is Samsara the only fleet tracking integration?
Explain the current issue thoroughly, including actions prior to experiencing the issue and any steps taken to correct the issue. Attach screen shots when possible. List additional integrations if Samsara is not the only one.