You must certify your logs before reviewing any carrier edits. Carriers may suggest an edit to your logs. These edits are sent to you for review.
-
To review edits, tap Review Carrier Edits.
-
You can switch between Edited Log and Original Log to compare the suggested changes with the original.
-
To accept an edit, tap the check mark next to the change suggestion. To reject an edit, tap the X near the change suggestion.
-
Confirm by selecting Certify and Submit.
Uncertified log alerts will appear upon sign in and sign out if you forget to certify your logs.
-
To review uncertified logs, select Review and certify.
Review all log dates listed.
-
To certify all logs, select Agree - Submit.
Unassigned Hours alerts will appear if your selected vehicle has unassigned hours. After sign in, you can use the Samsara Driver App to claim these unassigned hours.
-
Review the Unassigned Hours notification.
-
Claim or reject unassigned hours, as appropriate.
Tap Claim to claim unassigned hours or select Not mine if no unassigned hours belong to you.
Diagnostic and malfunction errors are displayed on the Hours of Service screen. The following table describes the types of errors you might see on the Samsara Driver App and the steps to resolve them.
Diagnostic / Malfunction |
Troubleshooting Steps |
Resolution |
---|---|---|
Power Compliance (D) The Vehicle Gateway was unable to read the engine’s power status. |
|
This event resolves automatically after 5 minutes. However, the event will trigger again if issues remain. |
Power Compliance (M) The Vehicle Gateway recorded over 30 minutes of driving time without power in the last 24 hours. |
|
This event resolves after the total driving time without power drops below 30 minutes in the last 24 hours. |
Engine Synchronization (D) The Vehicle Gateway was unable to read engine data such as the odometer or engine hours. |
|
This event resolves automatically after 5 minutes. However, the event will trigger again if issues remain. |
Engine Synchronization (M) The Vehicle Gateway recorded over 30 minutes of driving time without receiving engine data in the last 24 hours. |
|
This event resolves after the total time without required data elements drops below 30 minutes in the last 24 hours. |
Timing (M) The Vehicle Gateway is out of sync with the global UTC clock by at least 10 minutes. |
|
This event resolves when the device clock is synchronized with a trusted source of time. |
Positioning (M) The Vehicle Gateway recorded over 60 minutes of driving time without receiving a location in the last 24 hours. |
|
This event resolves after the total time without location data drops below 60 minutes over the last 24-hour period |
Data recording (M) ELD storage is full (mobile app or Vehicle Gateway). |
|
This event resolves immediately when storage is available. |
Missing required data elements (D) Location information was missing from a duty status change event. |
|
This event resolves when all duty status change records have a valid location. |
Unidentified Driving (D) The Vehicle Gateway recorded over 30 minutes of driving time without an assigned driver in the last 24 hours. |
|
This event resolves after the total unassigned time drops below 15 minutes for the last 7 days. When this condition is met, all other active Unidentified Driving events are resolved as well. |
Data Transfer (D) Data transfer (email) failure has occurred in the past 7 days. |
Notify your fleet administrator of the event within 24 hours. |
This event resolves when the next data transfer test is successful. |
Data Transfer (M) Data transfer (email) failure has occurred at least 3 times in the past 72 hours. |
Notify your fleet administrator of the event within 24 hours. |
This event resolves when the next data transfer test is successful. |
To view errors in the Samsara Driver App:
-
For drivers in the United States, from the Hours of Service view, tap the error above the driving status to view error details. For drivers in Canada, from the Hours of Service view, tap D (diagnostic) or M (malfunction) to view error source.
Top: United States; Bottom: Canada
Click Done to return to the Hours of Service view.
Resolve the issue using the recommendation in the table or contact your fleet administrator.
Duty status changes require location information for log entries. In cases where the Samsara Driver App cannot properly identify the location, you must manually add a location to avoid a violation at a roadside inspection or audit.
When you change your duty status without a manual or automatically detected location, the Samsara Driver App provides a notification about the missing location:
![]() |
You can then choose from two options: You can proceed to set your duty status with a blank location, or you can choose to cancel and manually add the location before proceeding with duty status selection.
![]() |
After you Save your location, Samsara will use it to identify your location in related logs.
Note
Limited ELD connection prompts are available for drivers in Canada.
To ensure uninterrupted vehicle data is available with your driving activities, Samsara continuously monitors data connections and alerts you to adverse events.
According to 4.6.1.2 (d) of the Canadian ELD Technical Standards, Samsara is required to inform drivers when ELD vehicle data is missing and how it impacts compliance. As a result, you will receive an alert banner in the Samsara Driver App dashboard when no ELD vehicle data is being received and can tap the alert banner for a more detailed explanation of the incomplete data risk.
|
|
If you try to change your duty status while you have a Limited ELD connection, the Samsara Driver App also displays a notification. In addition, the Personal Conveyance and Yard Move statuses are grayed out and not available for duty status change selection.
![]() |
There are three main causes for a Limited ELD connection:
You selected a vehicle in the Samsara Driver App but the engine is off
Lack of cell service or hotspot connection
ELD is disconnected
To resolve the Limited ELD connection, adjust the connection between the Vehicle Gateway and the vehicle. If the cause was the vehicle engine connection, after powering on the engine and restoring ELD connection, the banner will resolve itself within 1 minute. If the cause was network connectivity, banner should resolve within 10 seconds. If the alert persists after adjustment, contact Samsara Support or your fleet administrator. If you elect to continue without fixing the issue, you will receive a reminder alert of the Limited ELD connection when you change duty status.
If your fleet administrator has designated you as a driver who is exempt from use of an ELD, you will not be able to use HOS functionality while using the Samsara Driver App.
To keep you informed about HOS Configuration Changes, the Samsara Driver App notifies you when a fleet administrator changes your ELD policy. If your fleet administrator designates you as an ELD exempt driver, will see the following alert when you access the HoS tile:
Top: United States; Bottom: Canada
![]() |
![]() |
If you are not required to use an ELD, you can still use the Samsara Driver App for other features and avoid Hours of Service violation notifications.
To ensure uninterrupted vehicle data is available with your driving activities, Samsara continuously monitors data connections and alerts you to adverse events. You will receive an alert banner in the Samsara Driver App dashboard when you sign into the app without selecting a vehicle:
![]() |
If you attempt to change Duty Status without first selecting a vehicle, you will be prompted again to alert you to the lack of vehicle assignment:
![]() |
Tap OK to continue. To clear the alert, you must select a vehicle. If your vehicle is not available to select, contact Samsara Support or your fleet administrator.
When your fleet administrator changes your HOS configuration, the Samsara Driver App displays an alert to keep you informed on any policy changes. If you receive an alert, review the changes carefully and then click OK to dismiss them. If you have any questions about the configuration change, contact your fleet administrator.
![]() |
Note
Unauthenticated Driving is supported on Samsara Driver App 2130.300 and later versions.
Unauthenticated Driving is supported for drivers who are physically in Canada.
To ensure accuracy in driver reporting, the Samsara Driver App prompts you to authenticate if you start driving your vehicle under the below conditions:
The Samsara Driver App is actively open on your device
Your device is connected to the Samsara Vehicle Gateway (e.g. using the Vehicle Gateway hotspot)
Your vehicle is in Canada
This prompt will remind you to sign into the vehicle:
While the vehicle is in motion, the OK button will be disabled. However, after the vehicle comes to a stop, you can dismiss the prompt and sign in.
If you take no action, the prompt will automatically dismiss itself in 5 seconds.
If there are multiple devices connected to the Vehicle Gateway, this prompt will appear on each device where someone has not logged in (while the Samsara Driver App is actively open).
For drivers in Canada, to help you avoid and address violations, the Samsara Driver App pushes notifications to your mobile device. For each notification, the app indicates the specific driving limit or rule in the notification header and provides additional information about the specific event in the notification body.
The app pushes notifications to your phone 30 minutes in advance of receiving a violation as long as you are in an on duty state (Driving, On Duty, Yard Move). When the violation occurs, the app pushes an additional notification to your phone.
![]() |
The Samsara Driver App pushes notifications for the following events.
Cycle on duty hours limit
Max driving hours before reset (shift driving hours)
Max on duty hours before reset (shift on duty hours)
Shift limit
Daily 10 hours off duty
Max driving hours in a day (based on day start time)
Max on duty hours in a day (based on day start time)
Deferral of Off Duty: Minimum 20 hours rest over 2 days
Deferral of Off Duty: Maximum 26 hours driving over 2 days
Deferral of Off Duty: deferred time must be added to core rest break on Day 2
Cycle 2: 24 hours off duty after reaching 70 hours of on duty time
24 consecutive hours off duty in previous 14 days
Comments
0 comments
Article is closed for comments.