TeslaBleHttpProxy is a program written in Go that receives HTTP requests and forwards them via Bluetooth to a Tesla vehicle. The program can, for example, be easily used together with evcc.
I can't get it to work in with the latest docker image strangely. (1.2.5)
curl -X POST http://teslabridge:8080/api/1/vehicles/VIN/command/charge_port_door_open
{"response":{"result":false,"reason":"The command \"charge_port_door_open\" is not supported.","vin":"VIN","command":"charge_port_door_open"}}
and logs with successful wake_up
2024/10/17 14:49:20 INFO TeslaBleHttpProxy 1.2.5 is loading ...
2024/10/17 14:49:20 INFO BleControl initialized
2024/10/17 14:49:20 INFO TeslaBleHttpProxy is running!
2024/10/17 14:49:26 INFO received command=wake_up body=map[]
2024/10/17 14:49:26 INFO connecting to Vehicle ...
2024/10/17 14:49:41 WARN failed to perform handshake with vehicle (B): context deadline exceeded
2024/10/17 14:49:41 INFO retrying in 3 seconds
2024/10/17 14:49:46 can't accept: listner timed out
2024/10/17 14:49:46 INFO connection established
2024/10/17 14:49:48 INFO received command=wake_up body=map[]
2024/10/17 14:49:48 INFO sending command=wake_up body=map[]
2024/10/17 14:49:48 INFO successfully executed command=wake_up body=map[]
2024/10/17 14:49:59 INFO received command=charge_port_door_open body=map[]
2024/10/17 14:49:59 ERRO not supported command=charge_port_door_open
All other commands work too. Since it was deployed in 1.2.2 and looking at the code - it should work, right? I'm really confused honestly.
wimaha
commented
3 weeks ago
I can't get it to work in with the latest docker image strangely. (1.2.5)
and logs with successful wake_up
All other commands work too. Since it was deployed in 1.2.2 and looking at the code - it should work, right? I'm really confused honestly.
Originally posted by @Jabe in https://github.com/wimaha/TeslaBleHttpProxy/issues/41#issuecomment-2419495598