Native home assistant integration

[Daniel-dev22]

I started porting this project and tesla-ble to a native home assistant integration so that we can leverage multiple Bluetooth proxies for redundancy rather than a single esp.

Is anyone interested in this project? Codex got me very far to the point the integration pairs with the car but now running into a connection issue after restarting ha it doesn't seem to resume connection.

I can open the integration repo to the public if anyone is interested in assisting.

[nagyrobi]

I prefer the contrary, leverage off Home Assistant from this, and use dedicated ESPs with local hardware control.

[top-gun]

I still don‘t understand the use-case, what do you mean by local hardware control?

[nagyrobi]

With Bluetooth proxy, as proposed in OP, I would loose the local entities accessible on the node itself.

[Daniel-dev22]

With Bluetooth proxy, as proposed in OP, I would loose the local entities accessible on the node itself.

What local entities? A Bluetooth proxy still uses the esp32s
https://esphome.io/components/bluetooth_proxy/

[nagyrobi]

The problem with Bluetooth proxy is that it just uses the ESP as virtual BT adapter over the network. A native integration will create the entities only directly in Home Assistant.

However, the best about what this project does here is that you have access to ESPHome's automations directly on the ESP32, and you can intreract with the car completely independently from Home Assistant. I use the same ESP32 to talk to the EVSE via UART and to the car via BT, and I don't need Home Assistant in between. If for any reason the network or Home Assistant has issues, they don't affect my setup.

I also interact with a few other ESPHome nodes with Packet Transport component (https://esphome.io/components/packet_transport/) so that even that data exchange is much faster and doesn't need Home Assistant in between.

Home Assistant is a very nice, useful and powerful tool, but keep in mind it's a single point of failure in the system. And with so many breaking changes lately, it's considerable to try to implement mission critical stuff not relying exclusively on it.

[Daniel-dev22]

I got it all working in home assistant connecting to the Tesla via Bluetooth proxies. Its a 1 to 1 on capabilities with this repo + I added psi sensors and may add additional control.

I'm continuing to test and refine behavior but it's definitely doable to talk to a Tesla using Bluetooth proxies. It was a lot of work to get the encryption/decryption right even leveraging both claude and codex but finally got it within 5 days of starting on this path. Pretty impressive timeline thanks to the major advancements in ai.

[jjjasont]

I'm not sure if I'm following your idea. Are you saying, you want all homeassistant to pair with Tesla and issue commands directly to tesla, as oppose to ESPs as a middleman?

My preference would be ESPs over to homeassistant because my Pi is placed in a location that is quite far away from the tesla and bluetooth signal would not be strong enough to communicate. The benefit of having ESP is that it can be placed close enough to the car while still in the wifi range.

[Daniel-dev22]

I'm not sure if I'm following your idea. Are you saying, you want all homeassistant to pair with Tesla and issue commands directly to tesla, as oppose to ESPs as a middleman?

My preference would be ESPs over to homeassistant because my Pi is placed in a location that is quite far away from the tesla and bluetooth signal would not be strong enough to communicate. The benefit of having ESP is that it can be placed close enough to the car while still in the wifi range.

I don't think you're understanding how Bluetooth proxies work. Each esphome device that has Bluetooth can become a Bluetooth proxy effectively forming a highly available network. Your pi doesn't need to have good Bluetooth connectivity at all. The same esp you use for this project could be set to be a proxy instead.

https://esphome.io/components/bluetooth_proxy/

[pvmil]

In another implementation, it is said it is not possible to use a Bluetooth proxy, because direct Bluetooth communication is required due to protocol complexity (I am not 100% sure it is also applicable for the PedroKTFC implementation, I can imagine it is: tesla-local-control/tesla-local-control-addon#118 (comment)
@Daniel-dev22 : you mentioned you were able to pair with the Tesla, can you also control it in your test? Did you test with multiple proxies?

[Daniel-dev22]

In another implementation, it is said it is not possible to use a Bluetooth proxy, because direct Bluetooth communication is required due to protocol complexity (I am not 100% sure it is also applicable for the PedroKTFC implementation, I can imagine it is: tesla-local-control/tesla-local-control-addon#118 (comment)
@Daniel-dev22 : you mentioned you were able to pair with the Tesla, can you also control it in your test? Did you test with multiple proxies?

I have multiple proxies, pairing was successful. Reading vcsec as well. Working on infotainment then control.

[Daniel-dev22]

In another implementation, it is said it is not possible to use a Bluetooth proxy, because direct Bluetooth communication is required due to protocol complexity (I am not 100% sure it is also applicable for the PedroKTFC implementation, I can imagine it is: tesla-local-control/tesla-local-control-addon#118 (comment)
@Daniel-dev22 : you mentioned you were able to pair with the Tesla, can you also control it in your test? Did you test with multiple proxies?

I have multiple proxies, pairing was successful. Reading vcsec as well. Working on infotainment then control.

I'm using yalexs_ble as the gold standard for working with proxies. It's determines which device is best and only one ever talks at a time to the lock.

[wfjsw]

Does this go any further? I was trying to do this as well but it is stuck on the pairing step

[Daniel-dev22]

I do have a working repo that can control multiple cars. It's a bit finicky on connections through esphome proxies but it does work. I just have to look at how to release it.

As it's completely Claude/codex coded and I don't know if I want to fully release it where people then expect me to fix stuff or add features lol. I got it where I wanted and it's good enough for me. I can potentially share the code with you perhaps. Still thinking about it.

[wfjsw]

I used that as well and Claude wrote me catastrophically failing code lol (see my public repo). I guess at some point I also have to manually fix stuff. Also not sure why it is not pairing currently; esphome-tesla-ble also does not pair. Dunno why.

I'd say just turn off Issues and release it as is. I do that even before AI is a thing

[Daniel-dev22]

I'll look at releasing it tonight.

I initially started with Claude and it liked to placeholder stuff codex took it all the way through and was much better at taking it's time through the encryption issues which is likely what's happening for you.

I used various references including this repo in my instructions file and it helped tremendously on the pairing process, protocol and home assistant ble patterns.

[wfjsw]

#238 #240
Could that be a reason :/