Native home assistant integration #166
Replies: 4 comments 14 replies
-
|
I prefer the contrary, leverage off Home Assistant from this, and use dedicated ESPs with local hardware control. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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) |
Beta Was this translation helpful? Give feedback.
-
|
Does this go any further? I was trying to do this as well but it is stuck on the pairing step |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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.
Beta Was this translation helpful? Give feedback.
All reactions