Troubleshooting

This page covers the most common problems across all parts of BYD EV Pro. If your issue is not here, check the relevant setup page for that component.

Car App

Dashboard shows no vehicle data

The Car App connects to vehicle data through the DiLink layer. If values are missing:

Keep the head unit screen awake — DiLink may disconnect if the display turns off.
Restart the Car App once and wait about 30 seconds.
If the dashboard still shows no data, check that the Car App has the necessary DiLink permissions. Some values require explicit app permission grants on first run.

Dashboard shows data but Companion App or Telegram stop working

This means the Car App can reach the vehicle but not the internet. Check:

Wi-Fi or mobile data connectivity on the head unit.
License status — open the license section in the Car App and confirm it shows trial or active. If it shows expired or unknown, licensed features will be unavailable.

License shows as expired or unavailable

The Car App needs internet to refresh its license. If it has been offline for more than 72 hours, licensed features stop working.

Confirm internet access on the head unit (try opening a browser or checking Wi-Fi settings).
Open the Car App license section and use the Check / Restore action.
If the license is genuinely expired, contact support with the status shown in the app and the valid-until date if visible.

Voice commands are not recognized

Confirm the microphone permission is granted for the Car App.
Try switching between Ukrainian and English in the voice settings — recognition is language-specific.
Push-to-talk mode requires holding the button for the entire command. Wake-phrase mode requires speaking the phrase clearly before the command.
Voice recognition runs fully offline on the head unit. It does not require internet.

Companion App

QR scan fails or does not progress

Confirm the Companion App has camera permission on the phone.
Generate a fresh QR code in the Car App — QR codes expire.
Keep the Car App QR screen open during the entire pairing process.
Ensure there is good lighting; the QR scan fails in very dark conditions.

Pairing is rejected

The Companion App will show an error if pairing is rejected. Common causes:

Cause	What to check
License not active	Open Car App license section and confirm `trial` or `active`
Too many companions	Your license has a companion limit. Unpair an existing companion first
QR code expired	Generate a new QR in the Car App

Remote commands are not delivered

Remote commands from the Companion App go through the internet to the head unit (or T-Box). Check:

The Companion App has internet on the phone.
The head unit (or T-Box, if installed) has internet.
The Car App is not force-closed on the head unit. When the head unit is off, a T-Box is required for remote commands.

Proximity auto-lock/unlock does not work

Proximity requires T-Box. If T-Box is installed and paired:

Confirm Bluetooth is enabled on the phone.
Confirm location/background Bluetooth permissions are granted to the Companion App.
Check that the T-Box appears as paired in the Companion App settings.
If T-Box was added after the initial Companion App pairing, re-pair the Companion App with a new QR to include T-Box proximity data.
Confirm the T-Box is powered and within range.

Home Assistant

Entities do not update

Confirm the Car App is running and Home Assistant sync is enabled in Car App settings.
Confirm the webhook URL is reachable from the car/head-unit network. If Home Assistant is only accessible on your home Wi-Fi, the Car App must be on the same network.
If using a webhook secret, confirm both the Home Assistant integration options and the Car App settings use the exact same secret.
Check the Home Assistant log under Settings → System → Logs for entries mentioning byd_ev_pro, invalid_signature, or webhook errors.

Device tracker is always in the same position or empty

The GPS device tracker only updates when the Car App includes location data in its webhook. Location data comes from:

The head unit’s own GPS or location estimate while driving, if available.
T-Box GPS, if a T-Box is installed and paired.

If neither source is active, the device tracker will not update.

Integration was installed but no entities appear

After installing the HACS integration and restarting Home Assistant, you must complete setup:

Go to Settings → Devices & Services → Add Integration and search for BYD EV Pro.
Complete the setup flow to generate a webhook URL.
Paste that URL into the Car App Home Assistant settings.
Send at least one webhook from the Car App (use Test Connection if available, or wait for the next vehicle state change).

T-Box

T-Box does not appear in the Car App pairing wizard

Confirm the T-Box is powered.
Confirm Bluetooth is enabled on the head unit.
The T-Box broadcasts as EVP-tbox-XXXXXX over Bluetooth. If you see this name in the phone Bluetooth settings but not in the Car App wizard, try restarting the Car App.
If the T-Box was previously paired to a different Car App install, it may need to be reset. Check the T-Box pairing reset procedure.

T-Box pairing fails mid-way

The most common cause is loss of internet during the credential creation step. The wizard requires internet access at the point where it creates per-device credentials. Ensure the head unit has internet, then retry from the beginning of the wizard.

T-Box firmware update stalls or fails

Keep the Car App open and the phone screen active during the update.
Keep Bluetooth enabled throughout. Moving far from the vehicle during the transfer will interrupt it.
If the update fails, reopen the Car App T-Box section — it will usually offer a retry from where it left off.

License

Trial activation is rejected

One trial is allowed per vehicle (or per installation if the vehicle VIN is not available). If the VIN was already used for a trial, activation will be rejected. Contact support if you believe this is an error.

Features stopped working after 72 hours offline

The Car App caches license data locally but requires a refresh every 72 hours. If the head unit was offline for longer than that, connect to internet and open the Car App — it will refresh the license automatically.

Collecting information for support

When reporting an issue, include:

Which part of the system is affected: Car App, Companion App, T-Box, Home Assistant, or license.
The license status shown in the Car App (trial, active, expired, or unknown).
Whether the head unit has internet access at the time of the issue.
Any error messages shown in the app or in the Home Assistant log.
Whether the issue is consistent or intermittent, and when it first appeared.