2024.8 Tesla Fleet Integration (still) only one way

Configuration
102

I hope nobody minds, if so please remove, but I am maintaining a fork of Yoziru’s BLE Tesla project that provides an alternative approach. I started looking for an alternative to apps using Tesla’s pay for API and realised BLE was the likely best approach. I can’t use BLE from the RPi on which I run HA so needed something on a separate device, likely ESPHome based, and Yoziru’s project was what I found and tried. However, that seems to have stalled so I started a fork from which I’ve done some development that provides sensors and controls in HA. You can find it here: GitHub - PedroKTFC/esphome-tesla-ble: Interact with Tesla vehicles over BLE using ESPHome and Home Assistant.

It’s another tool in our armoury.

1 Like
103

Is there a simple way to update a device running yorizus project to yours?

104

Just update your yaml to point to my project. The readme is all but up to date and the example yaml in the repository explains the basic yaml.

105

bit of a novice when it comes to esp32 gear. Can this be done through home assistant ESPHOME device builder Addon? or i need to compile some other way?

106

I always use the ESPHome device builder myself. The readme and example.yaml should point you in the right direction. It’s pretty straightforward.

1 Like
107

I have spent hours trying many ways to implement Tesla Vehicle tracking
since my newest Tesla failed under the old " Tesla Custom Integration" implementation.

Tesla Fleet will not take any domain names that are registered and do work in browser.

Teslamate integrations would require 60+ entries in configuration.yaml file for each vehicle.

NONE of the options are acceptable for normal Home Automation users and more than 50% of the home assistant users.

No discovery when using Teslamate integration as it puts entries under teslamate.

There must be a better way.