Getting Started with the Car App

The Car App is byd_ev_pro, a Flutter app for BYD vehicles with DiLink head units. The source confirms vehicle telemetry display, local controls where DiLink exposes them, trip and charging history, voice commands, automation rules, Companion App relay paths, and Home Assistant webhook support.

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 over Cloud for relay-backed features, including Companion App, Telegram, and T-Box paths.
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

Cloud is used for relay-backed features: license checks, Companion App pairing, Telegram, remote commands, logs, and T-Box paths. The local DiLink dashboard does not need Cloud at every moment, but integrations will not work without internet.

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.

Installation status

The repository contains Android APK build outputs, including byd-ev-pro/build/app/outputs/flutter-apk/app-release.apk and byd-ev-pro/build/app/outputs/apk/release/byd_ev_pro.apk.

TODO: Product clarification needed — Which public download channel should users use for the Car App APK, and what exact sideloading flow is officially supported for BYD DiLink head units?

Until that is clarified, do not follow older draft instructions that mention a specific release page, USB format, or file-manager path.

Prerequisites

A BYD vehicle with a DiLink head unit that can run the Car App.
A product-approved APK source and installation path. These docs do not yet define one.
Internet connectivity from the head unit for relay-backed license checks, 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

Open BYD EV Pro on the DiLink head unit.
Keep the head unit awake while the app connects to the DiLink data layer.
Confirm the dashboard starts receiving live vehicle values.
Open the license area to restore an existing license or explicitly start a trial if the app offers that action.
Configure optional integrations only after the Car App is receiving vehicle data.

The Car App loads an encrypted vehicle daemon asset from the APK so the dashboard can start from bundled code even without Cloud. Cloud is still used for license checks, pairing, remote commands, logs, and relay-backed 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 only relay-backed features fail, check internet connectivity and license status.

TODO: Product clarification needed — What user-visible status labels should support ask users to report for DiLink connection failures?