Onboarding Checklist

Use this checklist to keep the Car App, Companion App, and optional T-Box setup separate.

1. Confirm the Car App install path

1. Confirm the product-approved APK source and DiLink sideloading path.
2. Install only from that approved source.
3. Open BYD EV Pro on the DiLink head unit.
4. Keep the head unit awake until live vehicle data appears.
5. Confirm the app can reach the relay before using license, pairing, Telegram, or remote features.

TODO: Product clarification needed — What exact public Car App installation instructions should be documented for end users?

2. Start or restore the license

The current relay and Car App code support an explicit 14-day app-tier trial. The license is checked through Cloud, cached with an HMAC signature, and feature checks fail closed when the last successful relay check is more than 72 hours old.

1. Open the Car App license area.
2. Use the trial action only for a new vehicle/install that is eligible.
3. Use restore/check for an existing license.
4. Confirm the license status is trial or active before configuring licensed features.

Caution

Older drafts mentioned a 31-day trial and a 24-hour grace period. Source code currently shows 14 trial days and a 72-hour Car App grace window.

3. Decide whether you need T-Box

Skip T-Box if you only need Car App features while the head unit is running, car-only Companion App pairing, and Home Assistant pushes from the running Car App.

Add T-Box if you need proximity auto-lock/unlock, T-Box GPS, T-Box state, OTA firmware update support, or Cloud commands handled by the T-Box.

4. Pair the T-Box, if present

Before pairing, the public docs still need product-approved physical installation requirements. At minimum, pairing requires powered T-Box hardware, a Car App/head-unit BLE connection to the T-Box, and relay connectivity so per-device Cloud credentials can be created.

1. Confirm the T-Box is powered and close enough for BLE pairing.
2. In the Car App, open the T-Box pairing wizard if it is available.
3. Wait for the scanner to find a Bluetooth device named like EVP-tbox-XXXXXX.
4. Select the matching device and connect.
5. Wait while the Car App creates per-device Cloud credentials and sends a shared secret over Bluetooth.
6. Wait for the T-Box to reboot and reconnect.

TODO: Product clarification needed — What physical T-Box power, wiring, placement, and safety checks must be completed before users start BLE pairing?

The wizard then offers an optional companion QR step. The current implementation closes the wizard from that screen; it does not itself navigate into a full companion-pairing flow.

5. Pair the Companion App

1. Open the Companion App.
2. Tap the QR scan flow.
3. In the Car App, show the companion/share pairing QR.
4. Scan the QR with the Companion App.
5. Grant the permissions requested by the Companion App for the selected pairing mode.
6. Wait until the Companion App reaches the paired/dashboard state.

Car-only QR pairing uses Cloud. T-Box pairing modes can also carry or derive a proximity secret so proximity features can work.

6. Configure Home Assistant, optional

Home Assistant receives webhook pushes from the Car App. Set up the custom integration first, copy its webhook URL, then paste that URL into the Car App Home Assistant settings if that screen is available in the installed Car App.

7. Verify the final state

• Car App dashboard shows live vehicle data.
• License status is trial or active for licensed features.
• Companion App is paired and shows vehicle state.
• T-Box status is visible only if T-Box is installed and paired.
• Home Assistant entities update after the Car App sends a webhook.

TODO: Product clarification needed — Which Telegram setup steps are ready for public user documentation, and which license tier should be described for Telegram access?