Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't init hci: no devices available #125

Open
ViperRNMC opened this issue Dec 16, 2024 · 3 comments
Open

can't init hci: no devices available #125

ViperRNMC opened this issue Dec 16, 2024 · 3 comments

Comments

@ViperRNMC
Copy link

ViperRNMC commented Dec 16, 2024

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
Copy link
Collaborator

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

@TheRealSimon42
Copy link

Also, will ESPHome BT-Proxy be used? 😅

@iainbullock
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants