can't init hci: no devices available

[ViperRNMC]

Hi, I added the integration in Home Assistant, but my blue system keeps on putting the bluetooth stick to hci1. Is it possible to change it, or maybe choose the default from Home Assistant?

[11:59:33] ERROR: teslaCtrlSendKey; Error: failed to find a BLE device: can't init hci: no devices available: (hci0: can't down device: no such device) [11:59:33] ERROR: Could not send the key; Is the car awake and sufficiently close to the bluetooth adapter?

[iainbullock]

Not possible sorry, it must be hci0. You will have to change your hardware configuration somehow

[TheRealSimon42]

Also, will ESPHome BT-Proxy be used? 😅

[iainbullock]

No.
The bluetooth hardware must be physically attached as tesla-control wants to control it at the hardware level.

If you need a 'remote device' solution have a look at our other project https://github.com/tesla-local-control/tesla_ble_mqtt_docker which allows use of say a Raspberry Pi remotely located away from your HA system

[chokethenet]

Hi,
I've been struggling with this issue for many days with the integrated bluetooth chip in the pc and several home assistant recomended usb sticks and the issue is as follows:
With this addon stopped the bluetooth receiver (integrated or usb ones) is on hci0 always, for days/weeks/months, once this addon is enabled it causes the bluetooth receiver to have an error (in a couple minutes or several hours) and it's re-loaded in hci1 (or hci2 or the first available if you have more than 1 bluetooth receiver configured).
Once that reload in hci1 occurs the addon is no longer capable of sending commands as it expects the device where it found it on start. Only a restart of the machine works, as it reloads the receiver in hci0.
In my case its HAOS on an intel minipc.

To summarize, this addon causes the bluetooth receiver to crash and it reloads on a different hci# with causes the addon to not be able to send more commands (all my other bluetooth integrations/devices work in seconds after the hci change, they adapt to the available one).

[iainbullock]

As per my comment on tesla-local-control/tesla_ble_mqtt_core#142

@chokethenet I think best to wait for the next update when I believe the robustness will improve considerably. In the meantime if you are sending commands with your automations when the car is away, you could improve robustness by not doing so

I'll let you know when I have something for you to test.