Only able to read data not able to change (Command Signing?)

[26miller]

I am trying to get this working but somehow get stuck. I have installed this with ESPhome dashboard in homeassistent. Once installed and all proper values configured I was able to pair the bluetooth key with my car.
After completing this I can see sensors update with actual data. But as soon as I try to change charging amps or any operation this action times out.

I am able to change these charging amps with my ios Tesla app and I also tried the suggested reset of tesla.

Can anybody point me in the right direction to get this running.

[anthonykeane]

I also have this issue, I can change stuff with my Android app, but not the esphome, reading is fine

I am able to change these charging amps with my ios Tesla app and I also tried the suggested reset of tesla.

Can anybody point me in the right direction to get this running.

[mrd0n]

Did you try removing the key from the car and then repairing with the ESP device?

[26miller]

I tried removing the key and after pairing it with tesla again but got the same result. I will give it another when I am back home from work but have no big expectations of this.

Just tried it again. removing key and pairing it again goes without issues but as soon as I hit any operational button I see errors in the log and nothing happens.

When i open for instance charge flap with tesla I can see status change in ESP Tesla BLE device in homeassistant.

[26miller]

I am still not able to change charging amps while all other sensors are giving correct data. I found today a piece about command signing since my car is from late 2023 can it be that this is holding me back? Really would like to have control over my charging amps again.

Command signing
Certain vehicles, including all vehicles manufactured since late 2023, require vehicle commands to be encrypted end-to-end and signed with a private key. The Tesla Fleet integration is unable to perform this encryption at this time, so certain features may be disabled or throw an exception when used.

[DaRockTR]

Hello, did you solve the issue?

I just setup an ESP32. Paired it (little hit and miss though) and I can see at least the states of asleep, locked, charge flap but none of the controls are working. I also don't get it updated from the car when I change it in the IOS App.

I get the following in the log file for all non working controls: For example changing charging amps

[21:12:44][I][tesla_ble_vehicle:116]: [setChargingAmps] Preparing command..
[21:12:44][I][esp-idf:000]: E (3448398) tesla_ble: Session is not valid

[21:12:44][W][tesla_ble_vehicle:208]: [setChargingAmps] INFOTAINMENT auth expired, refreshing session..
[21:12:44][I][esp-idf:000][BTU_TASK]: W (3448521) BT_GATT: ATT - Ignore wrong response. Receives (13) Request(61) Ignored

[21:12:44][I][esp-idf:000][BTU_TASK]: W (3448525) BT_GATT: ATT - Ignore wrong response. Receives (01) Request(b4) Ignored

My car is an early 2019 model 3. Just updated to the latest software available.

[26miller]

No not yet, but I am confident that command signing is holding me back. I installed latest tesla fleet integration on homeassistant last week and with that I got the same issues. Can read data but no control. Still work in progress time to work on this is biggest issue...

[DaRockTR]

I have no idea what happened but it mysteriously started to partially work. I can now send control commands to the car. Set charge current, wake up and set charge limit for example. Also all the error messages are gone. All "green".

But it only works one way. If I change setting in the car or in the Tesla app, HA does not update.

Maybe that issue clears tomorrow? who knows :D