Tesla control issue

[changyang1230]

Hi, I have read through previous notes and followed instructions, unfortunately my tesla charging via TWC is still not working.

Steps done:

• Updated to v0.124.4
• Changed the YAML (see below).
• Access and refresh token is generated via tesla.evcc.io; virtual key is created and approved in tesla app.

vehicles:
- type: template
  template: tesla-command
  title: Model 3 LR  
  accessToken:  <token>
  refreshToken: <token>
  vin: <vin>
  capacity: 77.8  
  phases: 1  
  icon: car  
  mode: pv
  name: ev4
  control: true

Despite all the above, it doesn't work.

What is the reason? In then documentation it says that this is currently for sponsors only; however the blog doesn't seem to imply that this is sponsor-only feature. What else could I be doing wrong?

[litithio]

See https://docs.evcc.io/docs/devices/vehicles#tesla.
The Tesla templates have been unified. There is no "tesla-command" template anymore.

[changyang1230]

Thanks - I did try tesla template too and still no luck.

Also, is it true that this remains sponsor only?

[mucki12]

I think the documentary is quite clear on sponsoring:
https://docs.evcc.io/docs/devices/vehicles#tesla
#12174

[changyang1230]

Ok if that's the case it sounds like everything is correct and it doesn't work simply due to the fact that I'm not a sponsor.

I was a bit confused because the blog article and the issue discussions are not very clear about this being sponsor-only.

[pit65535]

Hi, I am sponsor and already created access- and refreshtoken via tesla.evcc.io, but when i try to setup the virtual key I cannot find where I sholud scan that QR-Code im my tesla app....
It looks so easy:

1. Download tesla app
2. sign in

• I use the tesla app since long time....... so i opened it and taped nearly everywhere, but I really don´t find where to:

3. Scan the QR Code

Please can somebody help me?

[litithio]

Just scan it with your phone camera.

[pit65535]

Ahhh... Thank you very much :-)

[Arturfrain]

I have a Tesla and a Tesla Wallconnector3. I have a evcc sponsorship. I use evcc as Addon in homeassistant. Newest version 0.124.4 I followed all setup steps, created new API token, refresh token, created Tesla Key for evcc. but it doesn’t work. With the old Tesla API it worked.

I receive the error message (tiny triangle shield on the top right corner): max charge current 16A: vehicle not capable of current control

I guess the vehicle control over the API does not work even with key and sponsorship token.
when i start “Schnell” it should immediately start charging with max current which it does not. Seems car control does not work.

Using Tibber for smart charging works without problems with the new Fleet API.

[Arturfrain]

@andig i use the homeassistant addon. So i need to wait for the next release version because nightly version does not work in HA addon. Will the fix be added in the next release ? In the meantime then i switch off the evcc addon.

[silencer2008]

@Arturfrain did you end up working around this or have you disabled the HA add on ? Having the same issue with waking up the car when asleep.

[Arturfrain]

In the meantime I use a Bluetooth Proxy which also is able to wake the car and no need for the Fleets API . Wiith the Fleet APi restriction it is not really possible to control. I use TeslaSolarCharger since some weeks and it works perfectly for me. Controls completely over BLE.

[silencer2008]

@Arturfrain interesting
I am using HA add on as well
Any idea how to implement bleproxy on HA ? Or did u use another method ?

[Arturfrain]

I use bleproxy on a raspberry pi in the near of the car together with TeslaSolarCharger (a program dedicated to Tesla only which can be found on GitHub) on the same pi. Not Homeassistant addon and not longer evcc.

[alexonbandit]

Hi, is the fix (related to the tesla-proxy) mentioned by @andig already included in 124.4? My interpretation from the release notes it should be, right?

I am still getting the following error message in the log
[lp-1 ] ERROR 2024/02/27 13:35:22 charger disable: 500 Internal Server Error

Virtual Key (for the use with my TWC3) was as far as I can tell successfully created in included in the config.

Excerpt from my config:
vehicles:

• name: my_car
  type: template
  template: tesla
  title: Tessi
  accessToken: eyJhbGciOiJ****
  refreshToken: EU_864****
  vin: LRW3**** # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (Optional)
  capacity: 82 # Akkukapazität in kWh (Optional)
  control: true # Notwendig für Tesla Wall Connector. Der Virtual Key für evcc muss eingerichtet sein.

error-log.txt
evcc_config.txt

Thank you very much for your help in advance!

[andig]

@alexonbandit unfortuantely your log is hard to read:

{\rtf1\ansi\ansicpg1252\cocoartf2759
\cocoatextscaling0\cocoaplatform0{\fonttbl\f0\fmodern\fcharset0 Courier;}
{\colortbl;\red255\green255\blue255;\red218\green218\blue218;\red21\green21\blue21;}
{\*\expandedcolortbl;;\cssrgb\c88235\c88235\c88235;\cssrgb\c10980\c10980\c10980;}
\paperw11900\paperh16840\margl1440\margr1440\vieww29280\viewh15200\viewkind0
\deftab720
\pard\pardeftab720\partightenfactor0

\f0\fs28 \cf2 \cb3 \expnd0\expndtw0\kerning0
\outl0\strokewidth0 \strokec2 Using config file: /config/2024_02_evcc_modbus_tesla_proxy.yaml\
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/2024_02_evcc_modbus_tesla_proxy.yaml'\
[main  ] INFO 2024/02/27 13:08:20 evcc 0.124.4\
[main  ] INFO 2024/02/27 13:08:20 using config file: /config/2024_02_evcc_modbus_tesla_proxy.yaml\
[main  ] INFO 2024/02/27 13:08:20 starting ui and api at :7070\
[mqtt  ] INFO 2024/02/27 13:08:20 connecting evcc at tcp://localhost:1883\
[site  ] INFO 2024/02/27 13:08:22 site config:\
[site  ] INFO 2024/02/27 13:08:22   meters:      grid \uc0\u10003  pv \u10003  battery \u10003 \
[site  ] INFO 2024/02/27 13:08:22     grid:      power \uc0\u10003  energy \u10003  currents \u10003 \
[site  ] INFO 2024/02/27 13:08:22     pv 1:      power \uc0\u10003  energy \u10003  currents \u10007 \
[site  ] INFO 2024/02/27 13:08:22     battery 1: power \uc0\u10003  energy \u10003  currents \u10007  soc \u10003  capacity \u10007 \
[site  ] INFO 2024/02/27 13:08:22   vehicles:\
[site  ] INFO 2024/02/27 13:08:22     vehicle 1: range \uc0\u10003  finish \u10003  status \u10003  climate \u10007  wakeup \u10003 \
[lp-1  ] INFO 2024/02/27 13:08:22 loadpoint 1:\
[lp-1  ] INFO 2024/02/27 13:08:22   mode:        pv\
[lp-1  ] INFO 2024/02/27 13:08:22   charger:     power \uc0\u10003  energy \u10007  currents \u10003  phases \u10007  wakeup \u10007 \
[lp-1  ] INFO 2024/02/27 13:08:22   meters:      charge \uc0\u10003 \
[lp-1  ] INFO 2024/02/27 13:08:22     charge:    power \uc0\u10003  energy \u10007  currents \u10003 \
[lp-1  ] INFO 2024/02/27 13:08:22 car connected\
[lp-1  ] INFO 2024/02/27 13:08:22 start charging ->\
[lp-1  ] INFO 2024/02/27 13:08:22 vehicle updated: unknown -> Tessi\
[lp-1  ] ERROR 2024/02/27 13:08:24 charger disable: 500 Internal Server Error\
[lp-1  ] ERROR 2024/02/27 13:08:55 charger disable: 500 Internal Server Error\
[lp-1  ] ERROR 2024/02/27 13:09:23 charger disable: 500 Internal Server Error\
[lp-1  ] ERROR 2024/02/27 13:09:52 charger disable: 500 Internal Server Error\
[lp-1  ] ERROR 2024/02/27 13:10:22 charger disable: 500 Internal Server Error\
\
\
}

Please use plain text, not any encoding. You'll also need to set tesla: trace in the logging section to see what's going on behind the HTTP 500 error- that detail is missing.

[alexonbandit]

Hi @andig, first of all thanks for your help! Much appreciated!

As recommended I set tesla: trace in the logging section.

Since the following was caption was present in the log files, I revoked the evcc TESLA token pair and created new a new pair of tokens. I verified that in my TESLA account and all seemed ok. However that did not help.

{"response":null,"error":"vehicle rejected request: your public key has not been paired with the vehicle","error_description":""}

evcc_config_2.txt
Error_Log_2.txt

Note: I just removed the VIN, Tokens and some other credentials and replaced them with ****

[andig]

@alexonbandit error message means you'll need to install the evcc "virtual" key on the vehicle. You'll get to that step at the end of the token process on tesla.evcc.io.

[alexonbandit]

@andig I knew the problem was in front of the keyboard! Now all seems to work as expected.

[alexonbandit]

Again THX a lot!!

[andig]

You're welcome!

[andig]

Wer Probleme mit Tesla hat- HTTP 500 Fehler oder schlafendes Fahrzeug nicht aufgeweckt- bitte auf die evcc Nightly Version umsteigen. Wer HA nutzt muss sich leider bis zum nächsten Release gedulden.

[silencer2008]

Hi @andig is there a solution to waking up vehicle when using EVCC as a HA add-on? I assume the Nightly build is not yet available for HA yet ?

[andig]

@silencer2008 what wakeup are you missing specifically? Please start new discussion- this here has been resolved for 6 months and does not relate to wakeup.

[silencer2008]

@andig posted under #16545