Vehicle Detail Page

The Vehicle Detail Page provides comprehensive information about a single vehicle and allows operators to control, monitor, and manage that vehicle in real-time. This guide covers all features available on the detail page.

Accessing the Vehicle Detail Page

Navigate to the Vehicle Detail Page by:

1. From the Vehicles list, click View on any vehicle row
2. Direct URL: /dashboard/vehicles/[vehicle-id]

Page Layout Overview

The Vehicle Detail Page is organized into several sections:

1. Header - Vehicle identity, subaccount, and primary controls
2. Quick Actions Bar - Frequently used commands and actions
3. General Info Card - Static vehicle information
4. Status & Telemetry Card - Live real-time data from the IoT device
5. Recent Tasks - Open service tasks and work orders
6. End-of-Ride Photos - Recent parking proof images
7. Recent Rides - Latest rental history
8. IoT Commands - Full command panel for device control
9. Location Map - Current and historical GPS positions

---

Header Section

Vehicle Identity

The header displays:

• Vehicle ID/Number: The primary identifier (e.g., "VH-001", "SCOOTER-123")
• Subaccount Badge: Shows the subaccount name, city, and state
• Vehicle Model: The model/type of vehicle

Lock/Unlock Buttons

The most important controls are prominently displayed:

Button States:

• Disabled (faded): Vehicle is already in that state
• Active: Click to send command
• Loading (spinner): Command is being sent

The buttons automatically detect the current lock status and disable when already in that state.

---

Quick Actions Bar

A horizontal bar containing frequently-used controls:

Sound Vehicle Button

• Purpose: Plays an audible alarm on the vehicle to help locate it
• Use Case: Finding a vehicle in a crowded parking area or verifying you're at the right scooter
• Disabled State: Shows tooltip explaining why if protocol doesn't support sound

Command by IoT Model:

Unlock Battery Button

• Purpose: Unlocks the battery compartment for swapping
• Use Case: Battery swap operations for swappable battery vehicles
• Color: Amber to indicate caution

Command Lookup Sequence (tries each in order until one works):

1. UNLOCK_BATTERY_LOCK (Segway Max Plus)
2. BATTERY_LOCK_UNLOCK (Okai/Queclink)
3. CONTROL_EXTERNAL_LOCKS with operation=1 (Omni SCOR)

Start/End Trip Launcher

Dynamic button that changes based on whether an active ride exists:

No Active Ride:

• Shows Start Trip button
• Opens the staff-initiated ride flow
• Used for: Testing, demonstrations, repositioning

Active Ride Exists:

• Shows View Active Ride link
• Links to the ride detail page
• Shows ride number for identification

Vehicle Actions Menu

Additional actions available in the dropdown:

---

General Info Card

Static information about the vehicle configuration:

Inline Status Editor

Click the status badge to change the vehicle's status directly from this page. Available statuses:

• Available
• Available (Hidden)
• In Use
• Transportation
• Maintenance
• Charging
• Storage
• Offline
• Not Ready

---

Status & Telemetry Card

This card displays real-time data from the IoT device and updates automatically via WebSocket subscription.

Battery Information

Color Coding:

• Green (>50%): Good
• Yellow (21-50%): Monitor
• Red (0-20%): Needs charging

Lock Status

Shows current lock state:

• Locked: Vehicle is secured, throttle disabled
• Unlocked: Vehicle can be ridden
• Unknown: No recent status from device

Ignition Status

For vehicles with ignition sensing:

• On: Vehicle is powered on
• Off: Vehicle is powered off

Odometer

Total distance traveled by the vehicle in kilometers. Sources may include:

• Built-in vehicle odometer
• IoT-calculated distance from GPS
• Aggregated ride distances

Location

Current GPS coordinates with timestamp:

• Shows latitude and longitude
• Indicates when location was last updated
• Link to view on external map

Signal Information

Cellular connectivity data:

• Signal Strength: Cellular signal quality
• Last Signal: When device last communicated

Ride Statistics

Quick stats about rental activity:

• Total Rides: Number of completed rentals
• First Ride: When the vehicle was first rented
• Last Ride: Most recent rental date

Error Codes

If the vehicle is reporting errors:

• Displays current error code(s)
• Shows error message description
• Critical for diagnosing issues

---

Recent Tasks Card

Displays open and recently updated service tasks:

• Maintenance work orders
• Damage reports
• Inspection items
• Custom tasks

---

End-of-Ride Photos Card

Shows the last 6 parking proof photos taken by customers:

• Photos are displayed in a 3x2 grid
• Click any photo to view full size
• Photos are sorted by most recent first
• Only shows photos where customers uploaded proof

What These Photos Show

End-of-ride photos are captured when customers complete their rental:

• Confirms proper parking
• Documents vehicle condition
• Helps identify abuse or improper parking
• Required in many jurisdictions for compliance

---

Recent Rides Card

Shows the last 3 rides on this vehicle:

Click See all rides to view complete ride history for this vehicle.

---

IoT Commands Section

Expandable section providing full device control:

Accessing Commands

1. Click Show Commands to expand the section
2. View recent telemetry responses
3. Send individual commands

Password Configuration

Some IoT protocols require authentication:

• Device Password: Used for command authentication
• Auto-populated based on IoT type and subaccount settings
• Can be manually overridden if needed

Default Passwords by Protocol:

• OKAI: •••••sign in
• Queclink: •••••sign in
• Other: •••••sign in

Protocol-Specific Behavior

Omni SCOR Protocol:

• Commands sent directly without password
• Real-time bidirectional communication
• No password entry required

Segway TCP Protocol:

• Direct TCP connection to device
• Password handled at protocol level

Queclink TCP Protocol:

• Commands are sent through the Queclink TCP proxy
• Device must be online on port 9003
• Password is included in the AT command string

SMS-Based (OKAI legacy):

• Commands sent via SMS
• Response may be delayed
• Password included in command string

Available Commands

Commands vary by IoT device type but typically include:

Sending Commands

1. (If applicable) Set command parameters
2. Click Send button
3. Wait for response indication
4. View result in telemetry feed

Recent Device Responses

The telemetry feed shows the last 30 messages:

• Real-time updates: New messages appear automatically
• Expandable entries: Click to see full payload
• Copy functionality: Copy raw payload for debugging
• Type indicators: Shows message type (status, ack, heartbeat, etc.)

Command Response Status

After sending a command, you'll see one of:

• Success: Device acknowledged command
• Timeout: Device didn't respond in time
• Failed: Device rejected the command
• Sent (No ACK): Command dispatched, no confirmation

---

Location Map

Interactive map showing:

• Current vehicle position (marker)
• Location history trail (if available)
• Zone overlays (if configured)

Map Controls

• Pan/Zoom: Standard map navigation
• Satellite Toggle: Switch between map and satellite view
• Fullscreen: Expand map to full screen

Historical Tracking

The location history shows:

• GPS breadcrumb trail
• Timestamps for each point
• Movement patterns
• Time at each location

---

Real-Time Updates

The detail page automatically updates when:

• New telemetry arrives from the IoT device
• Lock status changes
• Battery level changes
• Location updates
• Ride starts or ends

Updates are pushed via WebSocket subscription to the vehicle's telemetry channel.

---

Troubleshooting on the Detail Page

Vehicle Shows "Offline"

1. Check Last Signal timestamp
2. Review recent telemetry for last messages
3. Check cellular signal strength history
4. May indicate:
   • Dead battery
   • Poor cellular coverage
   • Hardware failure

Commands Not Working

1. Verify IoT device is linked
2. Check password configuration
3. Review telemetry for error responses
4. Try STATUS command first
5. Check subaccount IoT passwords

Battery Reading Incorrect

1. Compare Vehicle Battery vs IoT Battery
2. Check if Charging indicator matches reality
3. Review telemetry for raw battery values
4. May need device recalibration

Location Not Updating

1. Check GPS signal status
2. Review last_location_update timestamp
3. Vehicle may be indoors/underground
4. IoT device GPS may need fixing

---

Best Practices

1. Check status before sending commands: Avoid redundant lock/unlock
2. Use Sound to verify: Before working on a vehicle, sound it to confirm identity
3. Review telemetry after commands: Verify device acknowledged
4. Document issues: Use notes or tasks for ongoing problems
5. Check photos regularly: Identify parking compliance issues early

---

Permissions

Access to the Vehicle Detail Page varies by role: