Low Battery Handling
Low battery handling ensures customers only see vehicles with sufficient charge for their rides. The system automatically hides vehicles below a configurable battery threshold and can send email alerts to your operations team.
Overview
When a vehicle's battery drops below the minimum threshold, it's automatically hidden from the mobile app. This prevents customers from unlocking vehicles that may not complete their intended ride, reducing support issues and improving customer satisfaction.
Key Features
- Automatic hiding - Low battery vehicles removed from customer view
- Configurable threshold - Set minimum battery percentage per location
- Email alerts - Notify operations team when vehicles need charging
- Real-time monitoring - Battery levels updated via IoT telemetry
- Dashboard visibility - See all low battery vehicles in one view
How It Works
IoT device reports battery level
↓
System updates vehicle record
↓
Customer opens mobile app
↓
Nearby vehicles API checks each vehicle:
Battery >= minimum threshold?
├── Yes → Include in nearby list
│ Customer can see and unlock
└── No → Exclude from list
Vehicle hidden from app
Configuring Battery Threshold
Setting the Minimum Battery
Navigate to Settings
Go to Dashboard → Settings.
Find Vehicle Settings
Scroll to the Vehicles section.
Set Minimum Battery
Enter Minimum Battery Percent (e.g., 20).
Save Settings
Click Save to apply changes.
Recommended Thresholds
| Fleet Type | Threshold | Rationale |
|---|---|---|
| Urban scooters | 15-20% | Short trips, frequent rebalancing |
| Campus bikes | 20-25% | Moderate distances |
| Tourist e-bikes | 25-30% | Longer excursions expected |
| Delivery vehicles | 30-35% | Must complete full routes |
Default Setting
If no threshold is configured, the system defaults to 20% minimum battery.
Factors to Consider
- Average ride distance - Longer typical rides need higher thresholds
- Charging infrastructure - More chargers allow lower thresholds
- Rebalancing frequency - Frequent rebalancing enables lower thresholds
- Vehicle range - Larger battery capacity allows lower percentages
- Customer expectations - Tourism fleets may need higher buffers
Email Alerts
Enabling Low Battery Alerts
Navigate to Settings
Go to Dashboard → Settings.
Find Email Notifications
Scroll to the Email Notifications section.
Enable Alert
Toggle Low Battery Alerts to on.
Set Recipient
Enter the Operational Alerts Email address.
Save Settings
Click Save to apply changes.
Alert Triggers
| Condition | Alert Sent |
|---|---|
| Battery drops below threshold | Yes |
| Battery critically low (< 10%) | Yes (priority) |
| Multiple vehicles low | Aggregated alert |
| Battery recovered | No (silent) |
Email Content
Low battery alert emails include:
- Vehicle number and location
- Current battery percentage
- Last known GPS coordinates
- Time since last telemetry update
- Link to vehicle in dashboard
Dashboard Monitoring
Viewing Low Battery Vehicles
- Go to Dashboard → Vehicles
- Click the Battery filter
- Select Low Battery to see vehicles below threshold
Dashboard Indicators
| Indicator | Meaning |
|---|---|
| 🔴 Red battery icon | Critical (< 10%) |
| 🟡 Yellow battery icon | Low (< threshold) |
| 🟢 Green battery icon | Good (≥ threshold) |
| ⚫ Gray battery icon | No data |
Map View
The map displays battery status for each vehicle:
- Color-coded markers by battery level
- Filter to show only low battery vehicles
- Quick access to vehicle details
Mobile App Behavior
What Customers See
When a vehicle is below the minimum battery threshold:
- Not visible on the map
- Not listed in nearby vehicles
- Cannot be scanned via QR code
- Cannot be unlocked via vehicle number
Customer Experience
Customer opens app in area with 10 vehicles
↓
3 vehicles are below 20% battery
↓
Customer sees 7 available vehicles
↓
Hidden vehicles appear once charged above threshold
Active Rides
If a vehicle's battery drops during an active ride, the ride continues normally. The threshold only affects new ride starts.
IoT Battery Reporting
Telemetry Updates
Battery levels are updated via IoT device telemetry:
| IoT Provider | Update Frequency | Battery Source |
|---|---|---|
| Segway | Every 30-60 seconds | Vehicle + IoT battery |
| Omni | Configurable interval | Vehicle battery |
| Okai | Every 30 seconds | Vehicle battery |
| Queclink | Configurable interval | Vehicle battery |
Data Fields
The system tracks multiple battery values:
| Field | Description |
|---|---|
vehicle_battery_pct | Main vehicle/scooter battery |
iot_battery_pct | IoT device internal battery |
battery_voltage | Raw voltage reading |
battery_temp | Battery temperature (if available) |
Accuracy Considerations
- Reporting lag - Some delay between actual and reported levels
- Calibration - Battery percentage estimation varies by vehicle
- Temperature effects - Cold weather affects readings
- Age degradation - Older batteries may report inaccurately
Operational Best Practices
Proactive Charging
- Monitor dashboard regularly - Check low battery counts
- Set up email alerts - Get notified automatically
- Schedule charging runs - Regular rebalancing routes
- Track patterns - Identify high-drain areas
Charging Workflow
Identify Low Battery Vehicles
Filter dashboard by low battery status.
Plan Collection Route
Use map view to optimize pickup path.
Update Vehicle Status
Set vehicles to Charging status when collected.
Charge Batteries
Swap or charge batteries as needed.
Return to Service
Once charged, set status back to Available.
Response Priorities
| Battery Level | Priority | Action |
|---|---|---|
| < 5% | Critical | Immediate collection |
| 5-10% | High | Same-day charging |
| 10-20% | Normal | Next scheduled run |
| > 20% | Low | Monitor only |
Troubleshooting
Vehicles Not Hiding
- Check threshold setting - Verify
minimum_battery_percentin Settings - Verify IoT reporting - Check last telemetry timestamp
- Confirm vehicle subaccount - Setting applies per subaccount
- Check vehicle status - Must be "available" to show anyway
Incorrect Battery Readings
- Verify IoT connection - Check device is reporting
- Review telemetry data - Look for anomalies in logs
- Check calibration - Some devices need recalibration
- Contact IoT provider - May be hardware issue
Alerts Not Sending
- Verify alert enabled - Check
low_battery_alertssetting - Check recipient email - Must have
operational_alerts_emailset - Review email deliverability - Check spam folders
- Confirm threshold crossed - Alert only on threshold breach
API Reference
Get Nearby Vehicles (Mobile)
GET /api/mobile/vehicles/nearby?lat=40.7128&lng=-74.0060
Response only includes vehicles above minimum battery threshold for the subaccount.
Vehicle Battery Data
{
"id": "uuid",
"vehicle_number": "V001",
"vehicle_battery_pct": 85,
"iot_battery_pct": 92,
"last_telemetry_at": "2025-01-15T10:30:00Z"
}
Settings Structure
{
"vehicles": {
"minimum_battery_percent": 20
},
"email_notifications": {
"operational": {
"low_battery_alerts": true
},
"recipients": {
"operational_alerts_email": "ops@example.com"
}
}
}
Keep Your Fleet Charged
Proper battery threshold configuration ensures customers always have a good experience. Combined with email alerts and regular monitoring, you can maintain high fleet availability and minimize customer frustration from low-battery vehicles.