Getting Started with the Car App

The Car App runs on BYD vehicles with DiLink head units. It shows live vehicle telemetry, provides local climate and access controls, records trip and charging history, supports voice commands and automation rules, and connects the Companion App and Home Assistant integrations.

What the Car App does

• Shows live DiLink vehicle data such as battery state of charge, range, power, temperatures, odometer, speed, doors, locks, windows, TPMS, seat heat, steering wheel heat, and motor data where the vehicle reports those values.
• Provides local vehicle controls through the DiLink control layer, including climate and access-related actions where supported by the vehicle firmware.
• Records trip and charging history.
• Supports voice commands and automation rules where the required app permissions and vehicle capabilities are present.
• Publishes vehicle state and events to the cloud so the Companion App, Telegram, and T-Box features can work remotely.
• Pushes Home Assistant webhook data when Home Assistant sync is configured.
• Shows and manages T-Box pairing/update features when a T-Box is present.

Main Dashboard

The main dashboard shows the vehicle state in real time. Core values include battery state of charge, range, current power, odometer, speed, battery and motor temperatures, doors, locks, windows, trunk, TPMS, and heating states. If the vehicle does not expose a sensor, the Car App shows an empty or unavailable value instead of inventing one.

The dashboard also includes calculated values. The Car App can show prognosed range from battery charge, battery capacity, and previous efficiency, plus current range based on the active trip. These estimates become more useful after several completed charging cycles.

Battery and Charging

The battery area is for a quick high-voltage battery check. Where the vehicle exposes the data, the Car App shows SOH, voltage, current, power, minimum and maximum battery temperature, weakest and strongest cell voltage, and the difference between them.

The cell-voltage difference helps surface possible battery imbalance. Treat it as owner-facing reference data, not a replacement for official BYD service diagnostics.

The Car App also records charging history: completed sessions, added energy, charge change, duration, and related values where DiLink provides them.

Trips and Efficiency

The Car App tracks the current trip, the current cycle between charging sessions, and local all-time totals. These views can show distance, energy used, average speed, drive time, and efficiency in kWh/100 km.

Some values can include climate consumption and other usage when the vehicle reports them through DiLink. Trip history is useful for comparing route, weather, driving style, and real-world range.

Voice Control

The Car App includes a voice assistant for Ukrainian and English commands. Recognition runs on the head unit through VOSK, without API keys and without sending voice audio to Cloud.

Voice commands can launch navigation or music, control climate, heating, seat ventilation, windows, sunroof, sunshade, locks, and trunk. Each action still depends on the vehicle model, DiLink firmware, Car App permissions, and whether the related app is configured, such as navigation.

In settings you can enable wake-phrase mode or push-to-talk, choose the navigation app, disable commands you do not need, and configure quick-action button behavior.

Automations and Quick Actions

Automations execute an action when the vehicle enters a selected state and a sensor condition is true. For example, a rule can turn on steering-wheel or seat heating in cold weather, or open the panoramic sunshade after the vehicle starts, if that action is supported by the specific model.

Each rule has a name, enabled toggle, condition, vehicle state trigger, and action. Some actions support an auto-revert timer, such as turning climate or heating off after a selected duration.

The floating quick-action button gives access to common commands over other apps on the head unit. If push-to-talk is enabled, a short tap can start a voice command, while a long press opens the quick-action panel.

Connectivity and Integrations

Internet is needed for license checks, Companion App pairing, Telegram, remote commands, logs, and T-Box communication. The local DiLink dashboard can show vehicle data without internet, but none of the connected features will work without it.

Home Assistant receives data through a webhook when the integration is installed and its URL is added in the Car App. Telegram can send charging notifications, charging-gun events, trip summaries, and other events if the feature is available in your license and Car App version.

Some Car App versions include a setting to keep Wi-Fi active after the vehicle turns off. Use it only if it appears in your installed version and matches your connectivity setup.

Compatibility

The code is built for BYD DiLink vehicles. The Car App contains a DiLink firmware table for DiLink 3.0, 4.0, 5.0, 5.1, and 6.0 variants and model families including Song Plus, Song L, Tang, Han, Seal, Seagull, Atto 3, Denza, and others.

Caution

Supported features still depend on the exact vehicle firmware and available DiLink feature IDs. The docs cannot promise that every control or sensor exists on every BYD model.

Installation

The Car App is installed manually on the DiLink head unit. Updates are installed the same way — download the newer APK and reinstall it.

Download the app

Download the latest BYD EV Pro APK from the Releases page. Choose the most recent stable BYD EV Pro release.

Enable ADB on the head unit

The Car App needs ADB (Android Debug Bridge) enabled on the head unit before it can connect.

Caution

Enabling ADB on DiLink 5.0 and newer usually requires a paid unlock procedure; on DiLink 3.0/4.0 it is simpler. The exact steps differ by model and DiLink version — search for the ADB unlock procedure for your specific vehicle.

Once ADB is enabled, turn on Wireless ADB debugging and Debug mode when USB is connected in the head unit’s Developer Options.

Install the APK

1. From a computer: connect to the head unit with Android platform tools installed and run adb install with the downloaded APK.
2. Or via USB stick: copy the APK to the root of a FAT32-formatted USB stick, insert it into the head unit, open the head unit’s File Manager, and tap the APK. Allow installation from unknown sources if prompted.

Disable the self-start restriction

Caution

After every install or update, the head unit may add the Car App to its self-start restriction list. If that restriction stays on, the head unit kills the app in the background and it disconnects while you drive. Open Settings → Apps → Self-Start Management, find BYD EV Pro, and make sure the self-start restriction is off. Repeat this after every update.

Updating

To update, download the newer APK from the Releases page and reinstall it with the same steps above. Your data is kept. After updating, check the self-start restriction again. An in-app updater is in development and will be documented here once it is available.

Prerequisites

• A BYD vehicle with a DiLink head unit that can run the Car App.
• The latest BYD EV Pro APK, downloaded from the Releases page.
• ADB enabled on the head unit (see Installation above) — required before the Car App can connect.
• Internet access from the head unit for license checks, Companion App pairing, remote commands, and logs.
• Vehicle permissions requested by the Car App, including DiLink access where the firmware exposes it.
• Access to required DiLink/ADB system permissions if the official installation or support flow asks you to enable them.
• T-Box hardware only if you need T-Box-only behavior such as proximity unlock, T-Box GPS/state, or T-Box command routing.

First run

1. Open BYD EV Pro on the DiLink head unit.
2. Keep the head unit awake while the app connects to the DiLink data layer.
3. On the very first connection, accept the Allow USB debugging? dialog on the head unit — tap Always allow. The connection indicator turns green once the connection is trusted.
4. Confirm the dashboard starts receiving live vehicle values.
5. Open the license area to restore an existing license or explicitly start a trial if the app offers that action.
6. Configure optional integrations only after the Car App is receiving vehicle data.

The Car App loads vehicle configuration from its bundled assets, so the dashboard can start even without internet. Internet is still needed for license checks, pairing, remote commands, logs, and connected features.

Optional next steps

• Pair the Companion App by scanning a QR from the Car App.
• Pair a T-Box if you need proximity behavior, T-Box GPS, or T-Box command routing.
• Configure Home Assistant if you want webhook-driven sensors and a device tracker.

Troubleshooting

If the dashboard does not receive vehicle data, keep the head unit awake and restart the Car App once. If connected features like Companion App or Telegram stop working but the dashboard is fine, check internet connectivity and license status.

The Car App shows a connection indicator. When contacting support, report its colour:

• Grey — not connected. ADB is not enabled on the head unit.
• Blue (pulsing) — connecting. The connection key has not been trusted yet; accept the Allow USB debugging? dialog on the head unit.
• Green — fully connected.
• Red — error. The vehicle service is temporarily unavailable; restart the Car App, and reboot the head unit if it persists.