Teslamate: New "Pay As You Go" Pricing 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

[naltatis]

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

[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?

[andig]

I don‘t see why it shouldn’t be as long as MyTeslaMate can work as command proxy. That said: every other, non-crippled, wallbox will be better that the severely restricted and forced-to-cloud-usage, unfortunate TWC. It‘s just a crap solution to a problem that has been solved properly before.

[Berlusconi13]

I agree that TWC may not be the ideal solution.
What settings should I adjust to get it working again?
Currently, I can’t find any access token, refresh token, or proxy token on teslamate.com

[Dragonkit]

Ich habe seit gestern genau das gleiche Probleme mit beiden Teslas am TWC.

500 Internal Server Error` response: {"response":null,"error":"vehicle rejected request: your public key has not been paired with the vehicle","error_descrip (truncated...)

Habe sogar schon die Autos komplett neu verbunden in MyTeslaMate incl. Schlüssel aber keine Verbesserung.
Ich hoffe es gibt da eine einfache Lösung. Laden geht bei mir aber, nur die Änderungen über EVCC nicht.
Steht halt auf "Schnell" und wir aktuell nur durch das Auto und den TWC zeitlich gesteuert.

Ist es eigentlich mögich EVCC nur zur Steuerung der Hausbatterie und für die Ladelogs zu nutzen ohne die Autos zu steuern ? Das würde mir eigentlich schon ausreichen. Muss ich dann einfach die Autos löschen und als Gastfahrzeuge laufen lassen ? Würde halt schon gerne die Autos sehen aber Steuerung ansich brauche ich aktuell nicht zu nutzen.
PV Überschussladen nutze ich das von Tesla selbst was ja mit Powerwall, TWC und Tesla Fahrzeug super funktioniert.

[VickyP1987]

Ich habe nach der Umstellung alles gecleared, mist.
Leer lassen oder einfach was eingeben funktioniert leider auch nicht.
Da ist eine bestimmte Anforderungen an die Zeichenkette, die evcc bemängelt

Ich habe an der yaml nichts verändert, d.h. die Token sind noch drin, das "alte" refresh Token ist offensichtlich ungültig, siehe folgende Meldung im Log:"/api/1/vehicles/***/command/set_charging_amps": oauth2: "login_required" "The refresh_token is invalid. Generate a new refresh_token by forcing user to re-authenticate.\

[VickyP1987]

Tokens müssen neu generiert werden. Seitdem läuft bei mir wieder alles

[TheJDJ13]

Today I see this after about 90 minutes of charging time:

Garage: max charge current 9A: 429 Too Many Requests: Usage limit exceeded: You have reached your maximum of 100 credits per day.

[jbuchner]

Can the Tesla integration be modified so that the interval at which commands are sent via the proxy can be set independently of the general update interval? I would like to keep the general interval at 30 seconds but increase the "command interval" to, for example, 300 seconds to save proxy tokens.

[andig]

Can the Tesla integration be modified

You mean TWC3? Could probably try to send current control in specific intervals only. Those are not expensive commands though. What's really expensive are wakeups.

[jbuchner]

You mean TWC3?

Yes, as you can see from @TheJDJ13 's comment, the limit of 100 credits per day is reached after 90 minutes of charging (which, of course, can be increased in My Teslamate).

It would be great if evcc could be optimized to use commands more efficiently. This could be achieved either by allowing the interval to be adjusted or by only sending a new command when a significant change is necessary.

[andig]

It would be great if evcc could be optimized to use commands more efficiently.

See #19802 (comment).

This could be achieved either by allowing the interval to be adjusted

For time being you can already do this by adjusting the interval.

or by only sending a new command when a significant change is necessary.

This will make PV charging less efficient. Happy to take a PR for twc3.go. Given the TWC is crippled (and has been from the beginning which only brings us into this situation), it seems this is not something that the core team will be working on.

[Dragonkit]

Also der TWC3 mag verkrüppelt sein, aber in Verbindung mit Powerwall und Tesla Fahrzeug macht es das PV Überschussladen komplett ohne sonstige Tools. Ich hab es in EVCC auf "schnell" stehen und der Rest macht dann Tesla unter sich aus mit dem Überschussladen. Somit habe ich pro Tag und Auto bisher 1 bzw. 2 Credits verbrauch. Wenn ich dann wegen günstigem Strom mal schnell laden will mach ich der Tesla App kurz den Haken raus bei Überschussladen und gut ist.
Optimal ist das aber trotz allem leider nicht. Nutze EVCC quasi nur noch für das Laden von der Powerwall bei günstigem Strompreis und für die Übersicht der Ladedaten.
Aktuell stehe ich vor der grossen Frage ob ich von Tibber zum Tintenfisch wechsele um da halt feste Zeiten zum laden zu haben. Will aber erstmal abwarten wie sich das Modul 3 auf den Strompreis bei Tibber und Tinterfisch auswirkt.
Könnnte durchaus sein das damit das PV Überschuss laden der Vergangenheit angehört wenn man billiger Strom kaufen kann als es der vom Dach ist. Ich bekomme noch 14,06 Cent für den Verkauft und somit ist das schon nicht weit auseinander.

[andig]

Also der TWC3 mag verkrüppelt sein, aber in Verbindung mit Powerwall und Tesla Fahrzeug macht es das PV Überschussladen komplett ohne sonstige Tools.

Ich wollte auch nichts anderes behaupten. Das ist aber ein weiterer Grund, dafür keine weiteren Sonderlösungen zu finden.

Ich bekomme noch 14,06 Cent für den Verkauft und somit ist das schon nicht weit auseinander.

OT.: die sind natürlich zu versteuern ;)

[Dragonkit]

Bis 30 kwp muss man es nicht mehr bei der Steuer angeben und da es ohne Umsatzsteuer ist muss ich da auch nichts abziehen. Somit kann ich mit den 14,06 als direkten Vergleich rechnen. Also sobald ich unter 14 Cent einkaufen kann ist PV Überschuss teurer :-) Leider Schade es hier der Eigenverbrauch teurer ist als der Einkauf.

[TheJDJ13]

You mean TWC3?

Yes, as you can see from @TheJDJ13 's comment, the limit of 100 credits per day is reached after 90 minutes of charging (which, of course, can be increased in My Teslamate).

It would be great if evcc could be optimized to use commands more efficiently. This could be achieved either by allowing the interval to be adjusted or by only sending a new command when a significant change is necessary.

Today I reached the 100 credits message in about 30 minutes.

[naltatis]

Just updated our documentation and the explaining blogpost to reflect the recent changes at myteslamate.

https://docs.evcc.io/en/docs/devices/vehicles#tesla
https://docs.evcc.io/en/blog/2025/01/20/tesla-api-update

Migrating this issue to discussions.

[Berlusconi13]

Just updated our documentation and the explaining blogpost to reflect the recent changes at myteslamate.

https://docs.evcc.io/en/docs/devices/vehicles#tesla https://docs.evcc.io/en/blog/2025/01/20/tesla-api-update

Migrating this issue to discussions.

Hi,
I noticed a small error in the documentation. It says Tesla API users receive a monthly credit of 0, but it should be $10.

Thanks for your work!
https://docs.evcc.io/en/docs/devices/vehicles#tesla

[TheJDJ13]

Just now I have the 100 credits use message today- before I had enough excess to start changing.

Is there any reason why I should not switch back to BT?

[andig]

Not at all if BT works for you.

[Villabacha]

Hi, I am not able to create access and refresh tokens anymore. It worked around 4 weeks ago with the process described at that time but now I fail. When using the script available on myteslamate in powershell, I can enter Client ID and secret but then powershell stopps.
Following above discussion - is it anyway no longer advisible to use the fleet API as there are too many calls?
My system consists of Tesla Model X, Keba P30X, Victron with 15 Kwh battery and PV with SMA sunnyboy

[jlestel]

You can find the one line command to get new tokens here: https://app.myteslamate.com/tesla

You must check the redirect URI of your application and update it if needed.

[Villabacha]

That is what I tried - open powershell and copied the script in and pressed enter, then I am asked for Client ID and Client Secret and after entering both, powershell stopps :-(

[askp66]

I had the same problem running the script in Powershell on Windows. Instead, I ran the Linux script on the command line of my Raspberry. That worked for me.

[TheJDJ13]

I have not switched back to BT yet. I decided to let it go a little longer. Here is my first monthly charge:

Description:
Our Proxies for Tesla Fleet API, Commands & Telemetry
Mar 15 – Apr 15, 2025

Qty:
1,377

Unit price:
€1.00
per 500

Amount:
€3.00

Subtotal €3.00
Total €3.00
Amount due €3.00

Paypal charge converted to $3.57

It seems likely that I could reach the next 500 on any given month so figuring $3.50 - $5.00 / month or $42 - $60 / year.

I WANT to charge with solar and that is why I am here. However, with my provider and plan it might actually be slightly more expensive to charge on solar vs. charging over night. Paying more per month to be able to pay a little more per month starts to become undesirable.

[andig]

The other obvious alternative is to get a non-crippled charger.

[TheJDJ13]

Please suggest a better NACS EVSE available in the US. I don't know of any right now.

If were to buy something new, I'd probably go with Emporia.

[andig]

Not familar with the US, sorry. In Europe there‘s a plethora of great ev chargers.

probably go with Emporia.

As far as I‘ve been told they don‘t have a usable api…

[TheJDJ13]

Yeah there are no good options here.

If I switched to Emporia I would not be using evcc.io. I'd use their system.