[Revisit Feature Request] BLE: Support for Specifying HomeLink Device to Trigger (API Parity with In-Vehicle UI)

[hleao]

Hi team,

I’d like to revisit a previously closed request (#4) regarding support for selecting which HomeLink device to trigger from the API.

---

Summary of the missing feature

• In-vehicle: Tesla already supports multiple HomeLink devices and the driver can choose which device to activate from the car’s UI.
• In API: The current API only allows triggering the first configured device. There is no way to specify which HomeLink device to trigger.

This creates an inconsistency between the in-car experience and what developers can offer through integrations.

---

Why this matters

I sell a product that integrates with Tesla vehicles and many of my customers have multiple garage doors configured.
Without the ability to select a specific HomeLink device, users cannot choose which door to open, even though they can do this from the car.

This limits the potential of HomeLink integrations.

---

Proposed feature

Extend the existing VehicleControlTriggerHomelinkAction request in the BLE API with a new optional property to specify the target HomeLink device.

Possible properties:

• homelink_device_index
• homelink_device_id
• homelink_device_name

Behavior:

• If provided, the specified device is triggered.
• If omitted, default behavior remains unchanged.

This keeps backward compatibility while allowing proper support for multiple HomeLink devices.