Tesla: Require personal developer account

[andig]

With #17501 we're relying on users to supply their own Tesla Client ID. They can use https://www.myteslamate.com/tesla-api-application-registration/ which provides this free of charge. As a benefit, they get 10$ free requests per month for personal use.

To complete this transition by end of January, we should remove the Tesla Client ID from the build process and hint users accordingly.

This prepares for evcc Tesla client only providing command proxy.

• implications on power wall?
• switch command proxy to myteslamate.com's 12€/yr service (only required for Tesla Wall Connector)

[rklueber]

On the nighly build my tesla connects fine.

I run a own build docker, bc of some changes für my PV system which are not yet in the nightly. I am not able to get tesla connected in my self build. I found out the hard way that you can not use the comfy way of access/refresh token generator from evcc.

I registered a 3rd party app at tesla developer account. I have clientId and clientSecret. But how can I connect now. I am missing to create access and resfresh token.

I tried ENV variables TESLA_CLIENT_ID and TESLA_CLIENT_SECRET with no success.

[naltatis]

@rklueber See the explanation in #17501 (comment). Our plan is to deprecate tesla.evcc.io and let Tesla owners generate the credentials via the free tier of myteslamate.com.

We'll publish a more in depth explanation of the upcoming changes soon.