Repository navigation
Cannot reconnect BLE after car is back at home #122
Description
After the car left, the BLE loses connection. So far so good.
But when it returns, it seems that the first connection fails and then it keep getting a Command Disallowed.
After I restart the docker container, it connects to the car right away
Running in Docker on a RPI3+, DietPi using a TP-Link UB500 Adapter as BT dongle.
Car: MY RWD 2024
Car software: 2025.20.3
Might be related to #117
`2025/06/24 15:15:37 INFO Executing command Command=vehicle_data Body=map[endpoints:[charge_state]]
2025/06/24 15:15:37 INFO Successfully executed Command=vehicle_data Body=map[endpoints:[charge_state]]
2025/06/24 16:51:02 INFO Connecting to Vehicle ...
2025/06/24 16:51:12 ERRO Cannot connect to vehicle Error="Vehicle is not in range: ble: failed to scan for XXX: hci: no response to command, hci connection failed"
2025/06/24 16:51:13 INFO Connecting to Vehicle ...
2025/06/24 16:51:13 WARN failed to connect to vehicle (A): ble: failed to scan for XXX: Command Disallowed
2025/06/24 16:51:16 WARN failed to connect to vehicle (A): ble: failed to scan for XXX: received scan response xxx with no associated Advertising Data packet
2025/06/24 16:51:22 ERRO Stop retrying after 3 attempts Error="failed to connect to vehicle (A): ble: failed to scan for XXX: received scan response xxx with no associated Advertising Data packet"
2025/06/24 16:51:22 ERRO Cannot connect to vehicle Error="failed to connect to vehicle (A): ble: failed to scan for XXX: received scan response xxx with no associated Advertising Data packet"
2025/06/24 16:51:32 INFO Connecting to Vehicle ...
2025/06/24 16:51:32 WARN failed to connect to vehicle (A): ble: failed to scan for XXX: received scan response xxx with no associated Advertising Data packet
2025/06/24 16:51:35 WARN failed to connect to vehicle (A): ble: failed to scan for XXX: Command Disallowed
2025/06/24 16:51:41 ERRO Stop retrying after 3 attempts Error="failed to connect to vehicle (A): ble: failed to scan for XXX: Command Disallowed"
2025/06/24 16:51:41 ERRO Cannot connect to vehicle Error="failed to connect to vehicle (A): ble: failed to scan for XXX: Command Disallowed"
.
. After a restart of the docker container
.2025/06/24 16:57:59 INFO TeslaBleHttpProxy 2.1.2 is loading ...
2025/06/24 16:57:59 INFO Env: httpListenAddress=:8080
2025/06/24 16:57:59 INFO Env: cacheMaxAge=5
2025/06/24 16:57:59 INFO Env: scanTimeout=2
2025/06/24 16:57:59 INFO BleControl initialized
2025/06/24 16:57:59 INFO TeslaBleHttpProxy is running!
2025/06/24 16:58:02 INFO Connecting to Vehicle ...
2025/06/24 16:58:03 INFO Connection to vehicle established
2025/06/24 16:58:03 INFO Executing command Command=vehicle_data Body=map[endpoints:[charge_state]]
2025/06/24 16:58:04 INFO Successfully executed Command=vehicle_data Body=map[endpoints:[charge_state]]`
Activity
kerbje commentedon Jun 26, 2025
Same situation without the car leaving place. Cloudy day, so wasn't charging for quite some time. At one point it got the command to start charging again and the same thing happend. A restart of the container fixed it.
wimaha commentedon Jan 6, 2026
Any new findings?
ggolec commentedon Jun 7, 2026
I get the same. it can be reproduced also when do not insert charging plug on first time correctly. If car throws "Check charger plug again" then got similar errors and car is not detected as tesla but like guest car.
I tried on tplink UB500 and some noname dongles.
So far worked for me on builtin BT on raspbery pi 2 model B but I had to replace it.
Is there any difference in BT handling between those?
wimaha commentedon Oct 19, 2026
Closing as a duplicate of #155: "Command Disallowed" / "hci: no response" after some time is the go-ble adapter hang tracked there. 2.5.0 makes sure only one Bluetooth connection runs at a time (#174), which may help. Please try 2.5.0 and report in #155 if it still happens.