Teslamate Change in Subscription Pricing – New "Pay As You Go" Model

[Berlusconi13]

Describe the bug

Teslamate hat auf ein neues Zahlungsmodell umgestellt und nun taucht der folgende Fehler im Log auf. Die Ladesteuerung funktioniert nicht mehr:

ERROR 2025/03/15 12:27:09 max charge current 7A: Post "https://api.myteslamate.com/api/1/vehicles/XP7YGCEK0RB460704/command/set_charging_amps": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Steps to reproduce

Ladung starten mit Tesla and TWC3

Configuration details

Nicht relevant

Log details

Nicht relevant

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

Linux

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

0.200.9

[andig]

context deadline exceeded

Ist ein Timeout und hat mit Bezahlmodellen nichts zu tun. Bzgl. Bezahlmodell machen wir ein follow-up in den Discussions.

[naltatis]

@jlestel can the above error be related to your announced change at myteslamate.com?

[Berlusconi13]

context deadline exceeded

Ist ein Timeout und hat mit Bezahlmodellen nichts zu tun. Bzgl. Bezahlmodell machen wir ein follow-up in den Discussions.

@andig @naltatis
Es gibt keine access und refresh tokens mehr auf teslamate - anscheinend wurde hier was größeres umgestellt.
Es scheint eher, dass die tokens nicht mehr funktionieren. Daher wahrscheinlich auch das timeout

„To comply with Tesla's API policies, MyTeslaMate must now make API calls on behalf of its users using its own API credentials. As a result, we are adjusting our subscription model to a "Pay As You Go" system to better reflect actual usage.“

[andig]

Daher wahrscheinlich auch das timeout

Die URL kann man im Browser aufrufen, also kein timeout.

[Berlusconi13]

Daher wahrscheinlich auch das timeout

Die URL kann man im Browser aufrufen, also kein timeout.

Es geht doch explizit um den command proxy.
Die tokens sind verschwunden.
Seit dieser Umstellung funktioniert die Ladesteuerung beim Tesla mit TWC3 nicht mehr

Statt der tokens erscheint Folgendes auf myteslamate.com

Set the following env vars:
- TESLA_API_HOST=https://api.myteslamate.com
- TESLA_AUTH_HOST=https://api.myteslamate.com
- TESLA_AUTH_PATH=/api/oauth2/v3
- TOKEN=?token=*Mein API-Token*
# Important: need to lower polling interval to not increase your budget
- POLLING_ASLEEP_INTERVAL=180
- POLLING_CHARGING_INTERVAL=180
- POLLING_DRIVING_INTERVAL=120
- POLLING_ONLINE_INTERVAL=180
- POLLING_DEFAULT_INTERVAL=180
- POLLING_MINIMUM_INTERVAL=120

# You need to enable Streaming signals to use streaming on Teslamate
- TESLA_WSS_HOST=wss://streaming.myteslamate.com
- TESLA_WSS_TLS_ACCEPT_INVALID_CERTS=true
- TESLA_WSS_USE_VIN=true

[Berlusconi13]

Nun erscheint Folgendes.
Es ist alles gepaired.

max charge current 3A: 500 Internal Server Error: Server error: `POST https://tesla-vehicle-command.myteslamate.com/api/1/vehicles/***/command/set_charging_amps` resulted in a `500 Internal Server Error` response: {"response":null,"error":"vehicle rejected request: your public key has not been paired with the vehicle","error_descrip (truncated...) 

[jlestel]

Hi guys

Regarding the price update, Tesla urged me to do it before Monday. I considered that this new model allows us to maintain the same price as before if there is no excessive use of the commands:

• I changed the subscriber plan: they therefore have a prorated credit that will be used to pay for their consumption for the next few months.
  Obviously, I will refund this credit to those who wish to cancel.

• I highlighted the application creation page: https://app.myteslamate.com/tesla
  It has the advantage of not collecting any confidential information compared to the version that didn't comply with Tesla's conditions.

The process isn't ideal yet; it's a version 1! By displaying the Shell commands to guide users, it still seems understandable. I'm thinking of adding Shell and PowerShell files to facilitate the execution of these commands. I'm curious to hear your thoughts on this.

• The MyTeslamate API management page no longer refers to the customer's Tesla API, but rather to the Tesla API used by MyTeslamate: https://app.myteslamate.com/fleet

In conclusion, I'm going to further improve this process, which will allow Tesla to remain compliant and prevent all customers from being unable to use the service.

Moreover, if creating an application is complicated for some (and they want to send commands), it's entirely possible to use only the MyTeslamate API and not have to create an application.

I'm curious to know more about the number of vehicle_data, command, and wake-up messages sent daily.

Nevertheless, our current shared approach seems relevant to me since:

• the customer benefits from their $10 monthly credits with their Tesla API
• only commands are used (and that's the added value of my service).

[andig]

@jlestel I still don't fully grasp what exactly has changed. Does Tesla no longer allow using the customer's Client/Secret and instead requires you to use the MyTeslamate one now? If that's it, what did they base this on?

[jlestel]

Exactly, a partner should not make calls with client applications, but only with their own.

Tesla has clarified that the previous approach violated the following sections:

§ 5.6.23 – "Accessing, storing, using, or retaining Tesla account credentials (such as a username or password) for any Tesla account other than the Partner’s Tesla account."
→ MyTeslaMate previously collected user credentials to make API calls, which is explicitly prohibited.

§ 5.6.24 – "Accessing, storing, using, or retaining product data or user data obtained through the use of Tesla credentials other than the Partner’s Tesla account."
→ By using user credentials to retrieve and process their data, MyTeslaMate was in violation of this rule.

§ 5.6.16 – "Replaying stored user passwords or credentials for commands that require such credentials in the API call."
→ If stored credentials were used to execute API commands at a later time, this was also considered a violation.

So I should not be able to read the Client Secret or access/secret tokens from the client API application.

Finally, they rely on what is visible on the website... and especially in their databases. This was highlighted by their oversight of application creation and command hits.

[andig]

Oh dear. If I understand the implications correctly then this basically put MyTeslamate under the risk of the API consumers executing more requests than their subscription covers and assigns that risk to MyTeslamate as the owner of the client id? That is indeed very unfortunate. It also takes away the benefit of the 10$ free monthly api calls?

Note: reopened issue for visibility.

[jlestel]

It also takes away the benefit of the 10$ free monthly api calls?

This is only partially affected, as only commands are affected.
Currently, the $10 credit is used directly by EVCC for other calls.

Edit: Additionally, wake_up isn't a "command," works without the command proxy... and represents 20x the cost of a command.

So, sending wake_up messages with the customer's Tesla API is very useful for allowing the largest credits of the $10 offered to be used :)

[Berlusconi13]

If understood correctly, it is currently not possible to charge with evcc in combination with TeslaMate, when charging Tesla with TWC3, right?