Bluetooth Low Energy and TWCManager

[ChutneyMary]

I've been reading the attached article and wondered if this has been considered for TWCManager -

https://shankar-k.medium.com/tesla-developer-api-guide-ble-key-pair-auth-and-vehicle-commands-part-3-485e4a357e7d

TLDR - The new official Tesla API has provision for Bluetooth LE commands including Stop/Start charging and set charging rate. AFAIK, the Raspberry Pi Zero W supports Bluetooth and typically resides in the Tesla Wall Charger within Bluetooth range.

It seems a logical extension to forgo all the API authentication, potential tiered subscription costs etc. and do direct control of charging via Bluetooth?

[MikeBishop]

That's a very exciting prospect -- thanks for finding that! I believe you still need the API registration in order to register the key on the car to use BLE commands, but this might help us stay in the lowest (and hopefully free) usage tier if we're never actually hitting the cloud API.

[ChutneyMary]

I hope Tesla has provisioned a non-cloud-based method for interaction with their vehicles. It would be remiss of them not to support people in remote localities out of internet range.

Here's hoping...I still can't get the Fleet API working!

[ChutneyMary]

Here are some resources I've found while trying to understand Bluetooth programming -

http://blog.kevindoran.co/bluetooth-programming-with-python-3/

https://people.csail.mit.edu/albert/bluez-intro/c212.html

[ChutneyMary]

Further resources are linked for anyone (@MikeBishop ?) thinking of progressing the Bluetooth API -

onokje/node-red-contrib-tesla#67 (comment)

The developer states that he has made "a tiny HTTP API to make BLE request to my Tesla". I haven't experimented with the code yet, but he goes on further to explain that no internet access is needed to interact with the vehicle over BLE.