-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional functionality present? #89
Comments
You can get the SOC and unlock the charge cable using the HA Tesla fleet plugin |
Except I don't use HA :) If using the BLE device for controlling charging etc. anyways, it would be really cool to be able to get all required data, and control charging cable lock, through this same device. |
I think it has been added to the BLE API: teslamotors/vehicle-command#330 Maybe it can be updated? |
Thanks for sharing this! This would be awesome once it's merged! We can do it locally through BLE! |
@yoziru Can you offer some insight into what it would take to merge this update, and expose the functionality as esphome sensors? (And any idea about the cable unlock command?) |
Having the ability to read the new data would be awesome. Tesla is now monetarizing the fleet api, and having basic stuff like SOC for charge automation via their cloud service makes this all pretty complex as additional programs like Teslamate are needed. If this project gave reading ability to the exposed data, it would make automatic charging so much easier. |
It is unclear for me if there is some way to get access to additional vehicle data, like for example current battery SoC?
Also unclear what it would take to unlock the charging cable through esphome-tesla-ble?
I would love to have a stab at these two things, but I have no idea where to start?
The text was updated successfully, but these errors were encountered: