Status: fehlgeschlagen prüfen cannot create vehicle type 'template': cannot create vehicle type 'tesla': 401 Unauthorized

[cpertel]

Describe the bug

Hi,
I use evcc-Plugin in HomeAssistant (209.1)
My Tesla once worked without issues.
Then something discontinued so I decided to remove the car and the story began.
Whenever I try to add my Tesla, I get the following issue:

"Status: fehlgeschlagen
prüfen
cannot create vehicle type 'template': cannot create vehicle type 'tesla': 401 Unauthorized"

I use the experimental GUI.
It might be that the "original" entry for my car came from the yaml.
All input entered.
Tried integrated GUI as well as the one listening on port 7070.
I exported the database, downloaded it and it could be opened with the correct client.
I saw no entry called "tesla"

My approach would be:

• dump database to yaml
• "correct" the yaml
• transform it back to a database

Steps to reproduce

1.go to the experimental GUI
2.add a car
3.select tesla
4. enter client-ID and the two tokens
5. click on "prüfen" / ?test?
...

Configuration details

HomeAssistant on x86-PC, current versions of HomeAssistant, evcc, ...
first config was in yaml
then I started using the GUI

evcc checkconfig
[main  ] INFO 2025/10/08 11:59:40 config file not found, database-only mode
config valid

Log details

starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2025/10/08 03:07:12 evcc 0.209.1
[main  ] INFO 2025/10/08 03:07:12 using config file: /config/evcc.yaml
[db    ] INFO 2025/10/08 03:07:12 using sqlite database: /data/evcc.db
[mqtt  ] INFO 2025/10/08 03:07:12 connecting evcc-xxx at tcp://xxx.xx.x.x:1883
[main  ] INFO 2025/10/08 03:07:12 UI listening at :7070
[site  ] INFO 2025/10/08 03:07:14 site config:
[site  ] INFO 2025/10/08 03:07:14   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2025/10/08 03:07:14     grid:      power ✓ energy ✓ currents ✗
[site  ] INFO 2025/10/08 03:07:14     pv 1:      power ✓ energy ✓ currents ✗
[site  ] INFO 2025/10/08 03:07:14     pv 2:      power ✓ energy ✓ currents ✗
[site  ] INFO 2025/10/08 03:07:14     battery 1: power ✓ energy ✓ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2025/10/08 03:07:14   tariffs:
[site  ] INFO 2025/10/08 03:07:14     grid:      pricestatic
[site  ] INFO 2025/10/08 03:07:14     feed-in:   pricestatic
[site  ] INFO 2025/10/08 03:07:14     co2:       ✓
[site  ] INFO 2025/10/08 03:07:14     solar:     ✓
[lp-1  ] INFO 2025/10/08 03:07:14 loadpoint 1:
[lp-1  ] INFO 2025/10/08 03:07:14   mode:        pv
[lp-1  ] INFO 2025/10/08 03:07:14   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1  ] INFO 2025/10/08 03:07:14   meters:      charge ✓
[lp-1  ] INFO 2025/10/08 03:07:14     charge:    power ✓ energy ✓ currents ✓
[lp-1  ] INFO 2025/10/08 03:07:14 car disconnected
[main  ] ERROR 2025/10/08 09:07:19 version check failed: Get "https://api.github.com/repos/evcc-io/evcc/releases/latest": dial tcp: lookup api.github.com: i/o timeout (installed: 0.209.1)

What type of operating system or environment does evcc run on?

HomeAssistant Add-on

External automation

• I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.

Nightly build

• I have verified that the issue is reproducible with the latest nightly build

Version

No response

[naltatis]

Then something discontinued so I decided to remove the car and the story began.

Can you explain what you mean by this?

The 401 Unauthorized indicates that your access/refresh tokens are not valid (any more). Please generate fresh ones and use them for creating the vehicle in evcc.

[cpertel]

Hi,

thanks for your support.

Didn't even know that this shows a "Tesla"-message thought of an evcc-error

I freshly generated the Tokens (using the windows "TeslaAuth"
No changes made to Teslamate

I mean that I saw no data about my car in evcc ... so I dropped the "car-object"

[naltatis]

Did it work?

[cpertel]

Evcc worked really great/amazing

In teslamate I See my cars data
On Tesla Development all looks okay as well
And I don't remember a change from my side

[andig]

There was no change on evcc side either