Troubleshooting-First Support
Resolve connection, Fleet Telemetry, data gaps, and command failures with symptom-driven guides.
Example: link failed, virtual key, no notifications, missing data
Support Categories
Filter Docs
Results: 6
Troubleshooting Documents
02
Fleet Telemetry
Virtual key, streaming, firmware, telemetry config
6 docs
How to Check Fleet Telemetry Status
Status check separates firmware, data streaming, and key pairing failures.
View Document →
Vehicle Software Update Required (firmware_update_required)
Telemetry collection is unstable when firmware prerequisites are not met.
View Document →
Data Streaming Setting Required (data_streaming_required)
Telemetry fields stay empty if third-party streaming is disabled in vehicle.
View Document →
Virtual Key Pairing Required (key_pairing_required)
Virtual key is missing or pairing is broken.
View Document →
When Telemetry Config Reset Is Needed
If specific fields remain empty for long periods, reapplying telemetry config is required.
View Document →
Impact of Disabling Location Data
If location data is disabled, map/route/address features are limited.
View Document →
Support Workflow
Required Info Before Contact
Including these details will significantly reduce handling time.
- Vehicle identifier (VIN or last 6 digits)
- App version, OS version, and device model
- Issue timestamp (with time zone)
- Failed feature name, error text, and screenshots
- Exact reproduction steps