Home Assistant Add-On

[stumbaumr]

Would you be willing to add configuration files to make this docker container available as a Home Assistant add-on?
https://developers.home-assistant.io/docs/add-ons/

Some people run evcc.io as a Home Assistant Add-on - it would be conveniant to just be able to run TeslaBleHttpProxy as an Add-On as well.

[Trunks1982]

Das würde mir auch gefallen!!👌

[Lenart12]

I created a similar repo TeslaBle2Mqtt-addon that starts this proxy together with TeslaBle2Mqtt. Someone could make an addon fairly easily just for this proxy by removing the "2Mqtt" part and its related configuration.

[Trunks1982]

Ich habe es gerade mal installiert aber bekomme mit meinem vorhandenen usb blenden keine Verbindung zum Auto.BLE ist aber in ha drin.

2025/01/29 17:09:55 INFO Publishing topic=tb2m/tb2m/uptime/state access path=uptime state=90 old_state=0
2025/01/29 17:09:58 ERRO Failed to publish state error="failed to get body controller state: command failed: vehicle not in range: ble: failed to scan for XP...............: context deadline exceeded"
2025/01/29 17:09:58 INFO received command=connection_status
2025/01/29 17:11:25 INFO Publishing topic=tb2m/tb2m/uptime/state access path=uptime state=180 old_state=90
2025/01/29 17:11:28 ERRO Failed to publish state error="failed to get connection status: command failed: ble: failed to scan for XP7YGCES9RB368880: skt: can't read hci socket: broken pipe"
2025/01/29 17:11:28 INFO received command=connection_status

[Lenart12]

Does TeslaBleHttpProxy work on your hardware without the addon, running it directly? This might be problem because you are using usb dongle.

[Trunks1982]

Also ich nutze im proxmox eigens eine vm nur für reine http ble und da funktioniert es mit einem usb dongle.Ich habe zwei stk.Einmal für ha vm selber und ble http vm auch.Wollte das halt nur in Ha nutzen.

[Lenart12]

Sorry, I have no idea how this works in proxmox. Im running HA Supervised with Rpi 3B+ and bluetooth that comes with it.

[Trunks1982]

Ist nicht schlimm das du das nicht weisst.Sicher ist das der usb komplett in der VM durchgereicht wird. Im Linux Vm läuft ja der proxy auch.Frage kann man nicht angeben in der programmierung auf was dr proxy alles zugreifen soll?
Also zb nicht nur hci?

[Lenart12]

If it runs in the VM i think the problem is related to docker/homeassistant. Maybe it is not forwarding USB devices correctly. Can you try installing this addon locally and set usb: true in TeslaBle2Mqtt/config.yaml then build and try it.

[Trunks1982]

Wie meinste lokal zu installieren?
In HA OS wüsste ich nicht das ich nen compose installieren kann.

[Lenart12]

Can you check for updates and install this testing addon:

I added usb: true to see if devices get passed on correctly to docker now

[Trunks1982]

sehe nur das im log: 2025/01/29 18:50:24 INFO received command=connection_status
2025/01/29 18:50:44 INFO ECDSA private key generated and saved
2025/01/29 18:50:44 INFO ECDSA public key generated and saved
2025/01/29 18:50:44 INFO BleControl initialized
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[18:51:09] INFO: Starting TeslaBle2Mqtt
2025/01/29 18:51:10 INFO Starting TeslaBle2Mqtt
2025/01/29 18:51:10 INFO TeslaBleHttpProxy undefined is loading ...
2025/01/29 18:51:10 INFO BleControl initialized

ERRO can't connect to vehicle error="failed to scan for vehicle: ble: failed to scan for XP7YGCES9RB368880: skt: can't read hci socket: broken pipe"

[Lenart12]

Can you build my fork https://github.com/Lenart12/TeslaBleHttpProxy/ in your Linux VM and check if that works? Maybe one of my new commits breaks the proxy on your vm.

[Trunks1982]

Can you build my fork https://github.com/Lenart12/TeslaBleHttpProxy/ in your Linux VM and check if that works? Maybe one of my new commits breaks the proxy on your vm.

Ich hab jetzt ihr repo neu gebildet in meiner normalen vm.Da funktioniert auch das senden des keys zum Auto und das verbinden.

2025/01/29 19:10:40 INFO TeslaBleHttpProxy 2.0.3 is loading ...
2025/01/29 19:10:40 DEBU LogLevel set to debug
2025/01/29 19:10:40 INFO TeslaBleHttpProxy httpListenAddress=:8080
2025/01/29 19:10:40 DEBU privateKeyFile loaded
2025/01/29 19:10:40 INFO BleControl initialized
2025/01/29 19:10:40 INFO TeslaBleHttpProxy is running!
2025/01/29 19:11:22 INFO ECDSA private key generated and saved
2025/01/29 19:11:22 INFO ECDSA public key generated and saved
2025/01/29 19:11:22 DEBU privateKeyFile loaded
2025/01/29 19:11:22 INFO BleControl initialized
2025/01/29 19:11:59 DEBU connecting to vehicle (A)...
2025/01/29 19:12:09 DEBU create vehicle object ...
2025/01/29 19:12:09 DEBU connecting to vehicle (B)...
2025/01/29 19:12:09 INFO Key-Request connection established
2025/01/29 19:12:09 INFO sending command=add-key-request body=map[]
2025/01/29 19:12:09 INFO Sent add-key request to XPxxxxxxxxxx. Confirm by tapping NFC card on center console.
2025/01/29 19:12:09 INFO successfully executed command=add-key-request body=map[]
2025/01/29 19:12:09 DEBU disconnect vehicle (A)
2025/01/29 19:12:09 DEBU close connection (A)
2025/01/29 19:12:20 can't accept: listner timed out

[Trunks1982]

Jetzt ist die frage ob der dongle schon in ha verwendet werden darf?
Er wird nämlich in der geräte liste angezeigt und verwendet.