search

wimaha / TeslaBleHttpProxy

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.
Apache License 2.0
31 stars 7 forks source link

Can’t open dashboard #42

Closed Arturfrain closed 3 months ago

Arturfrain commented 3 months ago

Hi, I try to install the BLE proxy on a PI Zero W. I succeeded install with the image followed by dev. After docker compose up -d It says [+] running 1/0 Container Tesla-ble-http-proxy Started.

now as in the documentation said I want to browse to http://“my-pizero-ip”:8080/dashboard But no connection can be established. I have no clue what I do wrong. Maybe is it a problem with the pi zero w? Do I need a other Raspberry Pi model? Maybe Pi Zero W is not working due to 32bit ? SSH works over WLAN. Only when using a web browser and trying to connect to that dashboard no connection possible.

Any help is appreciated

wimaha commented 3 months ago

Can you please restart the container and copy the logs (docker logs --since 12h tesla-ble-http-proxy). Thank you!

Arturfrain commented 3 months ago

Thank you, I am away from home until Wednesday. I will do that then and post.

Arturfrain commented 3 months ago

Hallo, ich habe nun auf einem PI4 unter 64bit intstalliert. Ich komme auf das dashboard, die keys sind erzeugt worden und im Verzeichnis abgelegt. Das Log File zeigt mir abe4r Fehler und ich sehe keine logs der gesendeten Befehle. Ist das vielleicht doch noch ein Fehler ?
Meine "docker logs --since 12h tesla-ble-http-proxy" zeigt Fehler an, die Befehle funktionieren aber anscheinend in evcc (verwendet evcc vielleicht wegen fehlndem proxy die fleet api).

bleproxy@bladepizero:~/TeslaBleHttpProxy $ docker logs --since 12h tesla-ble-http-proxy 2024/08/16 15:31:09 INFO TeslaBleHttpProxy 1.2.2 is loading ... 2024/08/16 15:31:09 ERRO failed to load private key. err="open key/private.pem: no such file or directory" 2024/08/16 15:31:09 WARN BleControl could not be initialized! error from daemon in stream: Error grabbing logs: invalid character '\x00' looking for beginning of value

Das habe ich nun gelöst indem ich den docker container mit "docker compose down" und dann wieder "docker compose -up" neugestartet habe.

Jetzt habe ich auch vernünftiges Log:

bleproxy@bladepizero:~/TeslaBleHttpProxy $ docker logs --since 12h tesla-ble-http-proxy 2024/08/16 20:02:09 INFO TeslaBleHttpProxy 1.2.2 is loading ... 2024/08/16 20:02:09 INFO BleControl initialized 2024/08/16 20:02:09 INFO TeslaBleHttpProxy is running! 2024/08/16 20:02:47 INFO received command=charge_start body=map[] 2024/08/16 20:02:47 INFO connecting to Vehicle ... 2024/08/16 20:02:52 INFO connection established 2024/08/16 20:02:52 INFO sending command=charge_start body=map[] 2024/08/16 20:02:53 INFO successfully executed command=charge_start body=map[] 2024/08/16 20:03:07 can't accept: listner timed out 2024/08/16 20:03:20 INFO received command=charge_stop body=map[] 2024/08/16 20:03:20 INFO sending command=charge_stop body=map[] 2024/08/16 20:03:22 INFO connecting to Vehicle ... 2024/08/16 20:03:25 INFO connection established 2024/08/16 20:03:25 INFO sending command=charge_stop body=map[] 2024/08/16 20:03:26 INFO successfully executed command=charge_stop body=map[]

Ich habe evcc mit dem Sponsortoken und dem Tesla Template laufen. Danke für das tolle Programm !!!