Skip to content

Home Assistant Integration Setup

The BYD EV Pro Home Assistant integration is a custom integration in ev-pro-ha-integration. It registers a webhook, creates sensor entities and a device tracker, and receives telemetry pushed by the Car App.

The integration defines sensors for battery, temperature, driving, charging, climate, access, windows/roof, TPMS, steering heat, seat heat, and motor speed. It also creates a GPS device_tracker from webhook location data.

The exact entities that receive values depend on what the Car App sends for your vehicle.

  • Home Assistant with HACS installed.
  • BYD EV Pro Car App installed through the product-approved APK path and receiving live vehicle data.
  • A Home Assistant webhook URL reachable from the network used by the Car App.
  • A license status that permits the Car App Home Assistant feature.
  • Home Assistant can accept inbound webhook requests from the car/head-unit network. If Home Assistant is not reachable from that network, entities will not update.

TODO: Product clarification needed — Which license tier names should public docs use for Home Assistant access?

The integration README documents HACS installation as a custom repository.

  1. Open HACS in Home Assistant.
  2. Add https://github.com/ant0nkr/ev-pro-ha-integration as a custom repository of type Integration.
  3. Install BYD EV Pro from HACS.
  4. Restart Home Assistant.
  5. Go to Settings → Devices & Services → Add Integration.
  6. Search for BYD EV Pro.
  7. Enter a vehicle name.
  8. Copy the webhook URL shown by Home Assistant.
  9. Submit again to finish setup.
  1. In the Car App, open Settings → Home Assistant if that screen is available in the installed version.
  2. Paste the webhook URL generated by Home Assistant.
  3. Optional: enter the same webhook secret in Home Assistant integration options and in the Car App.
  4. Enable sync.
  5. Use the Car App test connection action if available.

When a webhook secret is configured, Home Assistant verifies the X-Webhook-Signature HMAC-SHA256 header and rejects invalid requests.

The Home Assistant integration options can store a long-lived token and a list of script actions with Ukrainian and English voice phrases. The webhook response can return this action configuration to the Car App, but the exact user-facing setup flow in the Car App is not yet documented here.

TODO: Product clarification needed — What exact Car App voice-action setup flow should be documented after actions are configured in Home Assistant?

  • Confirm the Car App is running and Home Assistant sync is enabled.
  • Confirm the webhook URL is reachable from the car/head-unit network.
  • If using a webhook secret, confirm both sides use the same secret.
  • Check the Home Assistant log for invalid_signature, invalid_json, or unknown webhook errors.

The device tracker only updates when webhook payloads include location data.