Use Vehicles > Events to review commands sent from Track My Ride to hardware trackers and the responses returned by those trackers. This audit trail helps you confirm whether a configuration change, output action, diagnostic request or other remote command has reached a tracker.
Despite the tab name, this page is not a live history of driving events such as ignition changes, movement, panic-button activations or zone entries. It records outbound hardware commands and their replies. Use alerts, reports or tracker data views for driving and input events.
Before you start
The Events tab is available to accounts with hardware trackers. You need access to Vehicles. Note the vehicle and approximate time of the action you are investigating.
A tracker must connect to receive queued commands and return a response. Trackers that are asleep, offline or outside mobile coverage may remain queued until their next connection. Do not repeatedly send the same output or configuration command while waiting.
Steps
- Open Vehicles > Events.
- Find the vehicle and command. The newest records appear first, and the page shows up to the 100 most recent user-visible hardware commands.
- Read Type and Description to identify what Track My Ride requested.
- Check Sent at. Queued means the command has been created but no transmission time has been recorded. A date and time means it was sent to the tracker.
- Check Response for the result returned by the tracker. A response may confirm a new value, current status or output state.
- Use the table search, sorting and page controls to narrow or move through the results.
- Select Refresh when you are waiting for a queued command or response. The page also refreshes automatically about every 60 seconds while open.
Understand the columns
Date
When Track My Ride created the command. Times are displayed using the vehicle's configured timezone and daylight-saving setting.
Vehicle
The vehicle whose hardware tracker is the command target.
Type
The command category assigned by Track My Ride.
Description
A readable summary of the requested action or setting.
Sent at
When the command was transmitted. Queued means it has not yet been recorded as sent.
Response
The reply recorded from the hardware tracker. It may show a confirmed setting, diagnostic information, or an output result. A blank value means no response is recorded yet.
Understand command types
config update
Changes a tracker parameter such as sleep mode, heartbeat, engine detection, voltage threshold or another supported setting.
config request
Requests the current value of a tracker setting.
output control
Changes a supported physical output and may include its resulting state and duration.
device reset
Requests a remote tracker restart.
diagnostics
Requests tracker, firmware, network, GPS, I/O or other diagnostic information.
GPS record request
Requests a recent GPS record or coordinates from the tracker.
battery request
Requests current battery information from a compatible tracker.
online FOTA
Starts supported online diagnostics or firmware over-the-air (FOTA) work. FOTA updates tracker software over the mobile network. Keep the tracker powered and connected while this runs.
command
A supported command that does not fit one of the more specific categories. Use its description and response for context.
Available types and response wording vary by tracker model. Some responses are translated into readable confirmations, while specialised diagnostic replies may remain technical.
Follow a command through its stages
- Created: A row appears with the request time in Date.
- Queued: Sent at shows Queued while Track My Ride waits for an opportunity to transmit the command.
- Sent: Sent at changes to a date and time after transmission is recorded.
- Responded: Response contains the reply after Track My Ride receives one from the tracker.
A send time confirms that transmission was recorded. It does not confirm that the requested physical action was completed safely. For an output command, verify the expected equipment state using your organisation's safe operating procedure. For a configuration update, check the readable response and then confirm future tracker behaviour.
What happens next
The page retains the command among the most recent 100 records until newer commands replace it in this view. A successful response confirms what the tracker reported at that time. Configuration changes affect future tracker behaviour and do not alter historical journeys or events.
Troubleshooting
- If a command stays Queued, check the vehicle's last communication and power status. A sleeping tracker may receive it at its next scheduled check-in or when it wakes.
- If Sent at has a time but Response is blank, refresh after the tracker next communicates. A blank response alone does not identify whether the command failed, the reply is delayed or that command produces limited response data.
- If the response reports a different value than expected, reopen the vehicle settings and verify the selected option before sending another change.
- If no row appears, confirm you are looking at the correct vehicle, clear the table search and remember that only the latest 100 user-visible hardware commands are shown.
- If the displayed time is wrong, check the vehicle's timezone and daylight-saving setting.
- If a safety-related output has an unexpected result, stop issuing commands and have the installation checked by a qualified person.