Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tesla fleet API error 429 Too Many Requests #14226

Closed
Raudi1 opened this issue Jun 7, 2024 · 78 comments
Closed

Tesla fleet API error 429 Too Many Requests #14226

Raudi1 opened this issue Jun 7, 2024 · 78 comments
Labels
devices Specific device support prio Priority

Comments

@Raudi1
Copy link

Raudi1 commented Jun 7, 2024

Describe the bug

Plötzlich geht bei mir die Tesla Anbindung nicht mehr. Kommt immer 429 Too Many Requests egal ob EVCC SOC abfragt, oder Ladegeschwindigkeit sendet. Hat bisher ohne jegliche Änderung meinerseits problemlos funktioniert. Über die Tesla APP und auch Home Assistant läuft alles ohne Probleme.

Steps to reproduce

Tesla anstecken/als Fahrzeug auswählen

Configuration details

# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: warn
levels:
  wario: trace
  db: trace

# unique installation id
plant: xxx

interval: 15s # control cycle interval

# sponsors can set telemetry: true to enable anonymous data aggregation
# see https://github.com/evcc-io/evcc/discussions/4554
telemetry: true

sponsortoken: xxx

meters:
  - type: template
    template: shelly-pro-3em
    usage: grid
    host: 192.168.1.131
    name: Strom

  - name: Balkonsolar
    type: template
    template: hoymiles-opendtu
    usage: pv
    host: 192.168.1.126

chargers:
  - type: template
    template: twc3
    host: 192.168.1.35
    name: twc

  - name: gemini
    type: template
    template: go-e-v3
    host: 192.168.1.149

  - name: handtuchwaermer
    type: template
    template: shelly
    host: 192.168.1.125
    standbypower: 15 # Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional)
    integrateddevice: true
    icon: heater
    heating: true

vehicles:
  - name: wario
    type: template
    template: tesla
    title: Wario
    accessToken: xxx
    refreshToken: xxx
    vin: xxx
    capacity: 60
    mincurrent: 1
    maxcurrent: 16
    control: true

  - name: Teslamate
    type: template
    template: teslamate
    title: Wario-Teslamate
    id: 1
    capacity: 60

loadpoints:
  - title: TWC3
    charger: twc
    vehicle: wario
    mode: pv
    priority: 2

  - title: Go-e
    charger: gemini
    vehicle: wario
    mode: pv
    priority: 1

  - title: Handtuchwaermer
    charger: handtuchwaermer
    priority: 0
    guardduration: 1m

site:
  title: Heideweg 20
  meters:
    grid: Strom
    pv: Balkonsolar
tariffs:
  grid:
    type: tibber
    token: xxx
  co2:
    type: grünstromindex
    zip: xxx

mqtt:
  broker: localhost:1883
  topic: evcc # root topic for publishing, set empty to disable publishing
  user: MQTT
  password: xxx

Log details

[db    ] TRACE 2024/06/07 12:34:36 UPDATE `sessions` SET `created`="2024-06-07 12:09:20.11",`finished`="0000-00-00 00:00:00",`loadpoint`="TWC3",`identifier`="",`vehicle`="Wario",`odometer`=NULL,`meter_start_kwh`=NULL,`meter_end_kwh`=NULL,`charged_kwh`=0,`charge_duration`=NULL,`solar_percentage`=NULL,`price`=NULL,`price_per_kwh`=NULL,`co2_per_kwh`=NULL WHERE `id` = 412 1 <nil>
[lp-1  ] ERROR 2024/06/07 12:34:50 vehicle odometer: 429 Too Many Requests
[lp-1  ] ERROR 2024/06/07 12:34:50 vehicle soc: 429 Too Many Requests
[lp-1  ] ERROR 2024/06/07 12:34:50 charger get max current: 429 Too Many Requests
[lp-1  ] ERROR 2024/06/07 12:34:50 vehicle soc: 429 Too Many Requests
[lp-1  ] ERROR 2024/06/07 12:34:50 charger get max current: 429 Too Many Requests

What type of operating system are you running?

HomeAssistant Add-on

Version

0.126.6

@Dirk77777
Copy link

Gleiches Problem (bei mir Docker mit 0.126.6). Gefühlt wechselt sich dieser Fehler mit #14229 ab.

@Raudi1
Copy link
Author

Raudi1 commented Jun 7, 2024

Ist möglich, dass Tesla was an der API umgestellt hat. Evtl. limitieren sie jetzt die Commands pro Tag und Fahrzeug.
https://developer.tesla.com/docs/tesla-fleet-api#membership-levels

@Dirk77777
Copy link

Also wenn das stimmt, nur 50 Commands pro Tag und Fahrzeug, dann ist es vorbei mit dem PV-Überschussladen.

@Raudi1
Copy link
Author

Raudi1 commented Jun 7, 2024

Ja, sieht wohl leider so aus. Größere Pakete könnten natürlich helfen, aber die gibt es ja noch nichtmal.
Allerdings ginge es evtl. über BLE. https://github.com/teslamotors/vehicle-command
Wäre eh besser als über eine Cloud Lösung gehen zu müssen.

@premultiply
Copy link
Member

Oder einfach lokal wie vorgesehen über die Wallbox? 🤷🏻‍♂️

@row2hot
Copy link

row2hot commented Jun 7, 2024

Gleiches Problem hier, ich hab auch die Meldung: 429 Too Many Requests

@Raudi1
Copy link
Author

Raudi1 commented Jun 7, 2024

Oder einfach lokal wie vorgesehen über die Wallbox? 🤷🏻‍♂️

Die gehen leider nur bis 6A runter. Meine PV hat aber nur 1,75kWp. Damit habe ich aber trotzdem im letzten Monat 90% nur durch PV geladen.

@andig
Copy link
Member

andig commented Jun 7, 2024

@Raudi1 OT: wie machst du das?

@Raudi1
Copy link
Author

Raudi1 commented Jun 7, 2024

@Raudi1 OT: wie machst du das?

Bei gutem Wetter hauptsächlich das Fahrrad genommen und fast immer wenn Sonne war ab 1A 1-phasig über EVCC geladen. Waren im letzten Monat ca. 100kWh laut EVCC.

Am elegantesten wäre es denke ich den Tesla BLE Support in ESPHome oder so zu integrieren und das dann über EVCC zu steuern.
Es gibt auch schon Versuche in die Richtung: esphome/feature-requests#2630

@andig
Copy link
Member

andig commented Jun 7, 2024

und fast immer wenn Sonne war ab 1A 1-phasig über EVCC geladen.

@Raudi1 nochmal OT: schon klar- aber wie? charger: twc3 mit minCurrent: 1?

@andig
Copy link
Member

andig commented Jun 7, 2024

Bei evcc, insbesondere auch serverseitig bzgl. Tesla Service hat sich nichts geändert, es gab auch keinen Neustart. Im Logfile kann ich erkennen, dass es viele Fahrzeuge gibt wo das problemlos zu laufen scheint obwohl wir tw. mehrere Requests pro Sekunde (für unterschiedliche Fahrzeuge) in Richtung Tesla schicken.

See teslamotors/vehicle-command#255

@Raudi1
Copy link
Author

Raudi1 commented Jun 7, 2024

und fast immer wenn Sonne war ab 1A 1-phasig über EVCC geladen.

@Raudi1 nochmal OT: schon klar- aber wie? charger: twc3 mit minCurrent: 1?

Genau. Kann auch gerne noch mehr Daten von EVCC und Teslamate teilen, falls Interesse besteht.

Bei evcc, insbesondere auch serverseitig bzgl. Tesla Service hat sich nichts geändert, es gab auch keinen Neustart. Im Logfile kann ich erkennen, dass es viele Fahrzeuge gibt wo das problemlos zu laufen scheint obwohl wir tw. mehrere Requests pro Sekunde (für unterschiedliche Fahrzeuge) in Richtung Tesla schicken.

See teslamotors/vehicle-command#255

Ich habe heute Nacht bei meinem Tesla ein Update auf 2024.14.9 gemacht. Ggfs. hängt es damit zusammen. Oder es wird einfach nur sukzessiv umgestellt.
Jedenfalls reicht das aktuelle Limit des einzigen verfügbaren Membership Levels von Tesla nicht. Habe nachdem EVCC nicht mehr steuern konnte dann von Hand in Home Assistant gesteuert. Das ging nach einer Weile dann auch nicht mehr...
Ich denke mittelfristig wird es nur über BLE vernünftig gehen. Lokal ist mir eh lieber als Cloud. Diese Umstellung ist mal wieder ein gutes Beispiel warum.

@Raudi1
Copy link
Author

Raudi1 commented Jun 8, 2024

Heute geht es wieder. Die Frage ist nur für wie lange bevor das Limit wieder erreicht wird.

@FraBoCH
Copy link
Contributor

FraBoCH commented Jun 8, 2024

Same issue on my side, also since updating my Model Y to 2024.14.9. Yesterday evening, no way to control anything, 429 errors at any request. This morning it was working again. To mitigate the issue for the time being, I’ve increased the refresh interval in yaml config to 60 instead of 30.

@ugoetzen
Copy link

ugoetzen commented Jun 8, 2024

I think there is an issue with the Tesla API. Yesterday I got the 429 errors and nothing worked at all.
Today after evcc was working as aspected for a while, I now got these errors and the charging power cannot adjusted anymore. Reading the API seems to still working.
[lp-1 ] WARN 2024/06/08 13:37:09 charger logic error: current mismatch (got 6A, expected 16A)
[lp-1 ] DEBUG 2024/06/08 13:37:09 pv charge current: 0A = 6A + -8.79A (6065W @ 3p)
[lp-1 ] DEBUG 2024/06/08 13:37:09 projected site power 6065W >= 0W disable threshold
[lp-1 ] DEBUG 2024/06/08 13:37:09 pv disable timer start: 3m0s
[lp-1 ] DEBUG 2024/06/08 13:37:09 pv disable in 3m0s
[lp-1 ] ERROR 2024/06/08 13:37:19 max charge current 3A: Post "https://tesla.evcc.io/api/1/vehicles/XP7YGCEL7NB00XXXX/command/set_charging_amps": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Wallbox: Tesla Wallbox 3 with Tesla MY + M3

@FraBoCH
Copy link
Contributor

FraBoCH commented Jun 8, 2024

I observe something similar: I’m getting timeouts from EVCC proxy: "https://tesla.evcc.io/api/1/vehicles/XXXXXXX/command/set_charging_amps\": net/http: request canceled (Client.Timeout exceeded while awaiting headers).
I have no issue changing the amp & starting/stopping charge from the Tesla mobile app.
I’m also on a tesla wallbox 3 with a Tesla Y.

@Shuflel
Copy link

Shuflel commented Jun 8, 2024

I observe something similar: I’m getting timeouts from EVCC proxy: "[https://tesla.evcc.io/api/1/vehicles/XXXXXXX/command/set_charging_amps](https://tesla.evcc.io/api/1/vehicles/XXXXXXX/command/set_charging_amps%5C)": net/http: request canceled (Client.Timeout exceeded while awaiting headers). I have no issue changing the amp & starting/stopping charge from the Tesla mobile app. I’m also on a tesla wallbox 3 with a Tesla Y.

Having the exact same problem with our Model 3.

@andig
Copy link
Member

andig commented Jun 8, 2024

@ALL could you please stop posting "me too"?

@Raudi1
Copy link
Author

Raudi1 commented Jun 8, 2024

Ich habe jetzt mal die Bluetooth Option getestet. Funktioniert super!
Installationsschritte:
Auf dem Raspberry PI Zero W raspberry OS lite installiert und SSH+WLAN konfiguriert.

sudo apt update && sudo apt install -y wget git build-essential
wget https://go.dev/dl/go1.20.14.linux-armv6l.tar.gz
tar -xvf go1.20.14.linux-armv6l.tar.gz
mkdir -p ~/.local/share && mv go ~/.local/share
echo 'export GOPATH=$HOME/.local/share/go' >> ~/.bashrc
echo 'export PATH=$HOME/.local/share/go/bin:$PATH' >> ~/.bashrc
git clone https://github.com/teslamotors/vehicle-command.git
cd vehicle-command
go get ./...
go build ./...
go install ./...
openssl ecparam -genkey -name prime256v1 -noout > private.pem
openssl ec -in private.pem -pubout > public.pem
sudo setcap 'cap_net_admin=eip' "$(which tesla-control)"
tesla-control -vin YOUR_VIN -ble add-key-request public.pem owner cloud_key

Dann muss man einfach die Keycard auf die Konsole halten und bestätigen. Achtung: Es taucht vorher im Tesla keine Meldung auf!
Im Anschluss kann man Kommandos wie über die cloud API schicken. Beispiel:
tesla-control -ble -vin YOUR_VIN -key-file private.pem charging-start

Jetzt wäre nur meine Frage, wie man das am besten in EVCC einbindet? MQTT, REST...? Am besten wäre es natürlich das ganze in den bestehenden Tesla Code einzubinden und redundant zu gestalten. Dann könnte man wenn vorhanden und erreichbar über BLE gehen, und sonst über die Cloud.

@andig
Copy link
Member

andig commented Jun 8, 2024

Wie du willst, aber dafür bitte neue Diskussion. Template welcome.

@Raudi1
Copy link
Author

Raudi1 commented Jun 8, 2024

Wie du willst, aber dafür bitte neue Diskussion. Template welcome.

#14252

Wenn sich ein Entwickler dafür finden könnte, wäre das eine super Sache. Ich helfe auch so gut es geht, aber ich kann leider keinen sauberen Code schreiben.

@Stacykid

This comment was marked as duplicate.

@yipikaye

This comment was marked as duplicate.

@phoet
Copy link

phoet commented Jun 9, 2024

teslamate-org/teslamate#3928 (comment)

The official API mentions a limit of 1 call every 5 minutes: that's actually 300 calls per day on vehicle_data then gets a 429 response with a retry-after header of 86400 seconds.

Man müsste das intervall also auf 300 Sekunden stellen. Wäre ja nicht so schlimm, wenn man unterschiedliche update intervalle konfigurieren könnte.

@haroldboom

This comment was marked as off-topic.

@infinus
Copy link
Contributor

infinus commented Jun 9, 2024

teslamate-org/teslamate#3928 (comment)

The official API mentions a limit of 1 call every 5 minutes: that's actually 300 calls per day on vehicle_data then gets a 429 response with a retry-after header of 86400 seconds.

Man müsste das intervall also auf 300 Sekunden stellen. Wäre ja nicht so schlimm, wenn man unterschiedliche update intervalle konfigurieren könnte.

https://docs.evcc.io/en/docs/reference/configuration/interval
So for now set interval: 300s to comply with current API limitations until fix is found.

@tapwork
Copy link

tapwork commented Jul 3, 2024

I am the developer of SolarDashboard (an iOS and macOS app), and I've been following this thread since Tesla introduced these strict rate limits. SolarDashboard directly integrates the fleet API to enable solar surplus charging, but as we all know, that is no longer usable for those use cases.

I am currently experimenting with the BLE implementation of the Command SDK, but there is no way receiving any charge states via BLE, making it useless for our purposes. However, what about using the Fleet Telemetry (https://github.com/teslamotors/fleet-telemetry) to retrieve the states and utilizing BLE for the commands? Has anyone considered this approach?

P.S. Would be surprised if you guys get an answer from the fleet api team (email).

@andig
Copy link
Member

andig commented Jul 3, 2024

Not considered since we don't need it. We're getting the state via TWC, i.e. evcc requires a "charger".

Btw: beautiful dashboard!

@tapwork
Copy link

tapwork commented Jul 3, 2024

thanks ;-)

Right. Wallgen is also an option. understand you always get the charge state from the charger. makes sense

@Raudi1
Copy link
Author

Raudi1 commented Jul 6, 2024

With #14616 there's a working solution and unless Tesla changes something, EVCC works again for me.

@Raudi1 Raudi1 closed this as completed Jul 6, 2024
@andig
Copy link
Member

andig commented Jul 6, 2024

Excellent, thank you all for your patience!

@spubanz
Copy link

spubanz commented Jul 9, 2024

Hi,
first off, thanks for the solution with the BLE command proxy - works like a charme for our Model 3!
However, since our other car - a legacy Model X does not support the BLE key, I'm pretty much still facing the API call limit issue with that one.
Are there still efforts to get in touch with Tesla about other plans that allow more API calls? That would help all the legacy Modle S & X drivers.
Thanks again!

@andig
Copy link
Member

andig commented Jul 10, 2024

Yes, but Tesla doesn‘t answer at this time…

@User47873S
Copy link

Ich schlage vor Tesla mit der Anfrage zu überfluten das die APIs wieder freischalten. Das muss teurer und aufwendiger sein die Kunden Beschwerden zu bearbeiten als die Serverkosten oder warum es gedrosselt wurde. Am besten mit Papier Briefen damit kein bot es erledigen kann.

@spubanz
Copy link

spubanz commented Jul 12, 2024

Hi again,
in the mean time I found a workarround that runs on HomeAssistant and the old API, thus it works without BLE for legacy Teslas.
I'm using the Tesla Custom Integration (https://github.com/alandtse/tesla) in combination with the REST API and simply set up a custom vehicle in evcc.

vehicles:
  - name: modelX
    type: custom
    title: Hotblack Desiato
    capacity: 100
    icon: car
    chargeenable: # start/stop charging
        source: http
        uri: "http://MY_HA_IP:8123/api/services/switch/{{if .chargeenable}}turn_on{{else}}turn_off{{end}}"
        method: POST
        headers:
            - authorization: Bearer MY_HA_ACCESS_TOKEN
            - content-type: application/json
        body: '{"entity_id": "switch.MY_CAR_charger"}'
        jq: .state
    maxcurrent: # set charger max current (A)
        source: http
        uri: http://MY_HA_IP:8123/api/services/number/set_value
        method: POST
        headers:
            - authorization: Bearer MY_HA_ACCESS_TOKEN
            - content-type: application/json
        body: '{"entity_id": "number.MY_CAR_charging_amps", "value": "{{.maxcurrent}}"}'
        jq: .state | tonumber
    wakeup: # vehicle wake up command
        source: http
        uri: http://MY_HA_IP:8123/api/services/button/press
        method: POST
        headers:
            - authorization: Bearer MY_HA_ACCESS_TOKEN
            - content-type: application/json
        body: '{"entity_id": "button.MY_CAR_wake_up"}'
        jq: .state
    status: # get vehicle connection status
        source: combined
        plugged: # plugged in?
            source: http
            uri: http://MY_HA_IP:8123/api/states/binary_sensor.MY_CAR_charger
            method: GET
            headers:
                - authorization: Bearer MY_HA_ACCESS_TOKEN
                - content-type: application/json
            jq: .state
        charging: # charging?
            source: http
            uri: http://MY_HA_IP:8123/api/states/binary_sensor.MY_CAR_charging
            method: GET
            headers:
                - authorization: Bearer MY_HA_ACCESS_TOKEN
                - content-type: application/json
            jq: .state
    soc: # battery soc (%)
        source: http
        uri: http://MY_HA_IP:8123/api/states/sensor.MY_CAR_battery
        method: GET
        headers:
            - authorization: Bearer MY_HA_ACCESS_TOKEN
            - content-type: application/json
        jq: .state | tonumber
    range: # electric range (km)
        source: http
        uri: http://MY_HA_IP:8123/api/states/sensor.MY_CAR_range
        method: GET
        headers:
            - authorization: Bearer MY_HA_ACCESS_TOKEN
            - content-type: application/json
        jq: .state | tonumber
    limitsoc: # charge limit set by car (%)
        source: http
        uri: http://MY_HA_IP:8123/api/states/number.MY_CAR_charge_limit
        method: GET
        headers:
            - authorization: Bearer MY_HA_ACCESS_TOKEN
            - content-type: application/json
        jq: .state | tonumber
    odometer: # milage (km)
        source: http
        uri: http://MY_HA_IP:8123/api/states/sensor.MY_CAR_odometer
        method: GET
        headers:
            - authorization: Bearer MY_HA_ACCESS_TOKEN
            - content-type: application/json
        jq: .state | tonumber

The important pice is that you use the custom integration whithout the fleet API.

Maybe that helps someone out there.

Cheers!

@andig
Copy link
Member

andig commented Jul 12, 2024

The important pice is that you use the custom integration whithout the fleet API.

That seems pretty impossible?

@spubanz
Copy link

spubanz commented Jul 12, 2024

The important pice is that you use the custom integration whithout the fleet API.

That seems pretty impossible?

Well, when you install the plug in in home assistant it shows you a checkmark box "use fleet API" that you can leave unchecked. If you do so you can enter a refresh token on the next page that you can generate as described in the installation instructions.

With that it works for me. Frankly I'm not able to tell what really goes on in the background since I'm not that deep in the topic.

@Maddimax
Copy link

@spubanz Did you try a longer charging session with that yet? Last time I tried without Fleet Api I also ran into the rate limit.

@spubanz
Copy link

spubanz commented Jul 12, 2024

@Maddimax, it ran yesterday the whole afternoon (approx. 5+ hours) and still works today - with the standard template it usually lasted for 30 minutes max.

Never the less, I tried it with the Model 3 a bit ago and it seems that wrinting values does not work with that one. So it looks like I'll stick with the BLE solution for the M3 and with the custom vehicle implementation for the pre 2021 MX...

@haroldboom
Copy link

haroldboom commented Jul 15, 2024

Hi all, some more rublings on Facebook with regards to OCPP on the TWC3, anyone should be able to view (I dont have a FB account and can).
https://www.facebook.com/groups/teslaownersaustralia/permalink/792579336197477/?m_entstream_source=group&_rdr

Link to document: https://www.energymining.sa.gov.au/__data/assets/pdf_file/0005/1051358/27062024-EVSE-Registered-Equipment-Compliance-List.pdf

I am also going to contact the SA government and ask how Tesla is on there when it doesn't currently support OCPP and see if I can get more info.

@User47873S
Copy link

Is there a solution coming soon for people without programming skills, or should one just buy a different wallbox? I have EVCC running in Home Assistant. I can still manage to forward a Bluetooth stick to HA. But I can't get the TeslaBle Proxy running as a container; I've been working on it for three days. Not to mention what needs to be configured afterward. That's why I'm asking if it will ever be officially integrated into EVCC or if there is another solution. I don't think I'm alone in not having any programming skills. And definitely not in combination with Tesla and TWC.

@Raudi1
Copy link
Author

Raudi1 commented Jul 19, 2024

You don't need programming skills to set up the proxy. I'd say anybody who can get EVCC running and configured should be able to get the proxy running on a dedicated raspberry pi with Bluetooth built in like the zero 2. Another potential future option would be ESP home.

@Stacykid
Copy link

Well, it would be nice to have proper instructions on what needs to be done and how.

There are different scenarios, raspberry, Nas etc. I don't know what works. Is my Raps sufficient for this, do I need a new one or a 2nd one?

@Raudi1
Copy link
Author

Raudi1 commented Jul 19, 2024

You need one near your car. If it's only running EVCC, it should be fine. With other stuff your mileage may vary.
Here's detailed instructions https://github.com/wimaha/TeslaBleHttpProxy/blob/main/docs/installation.md
On the EVCC side you only have to add the IP of your pi to the config.

@User47873S
Copy link

"I have a NUC, Proxmox, VM Home Assistant, and Docker. ESPHome is running in HA. If I understand correctly, it only works with ARM architecture."

@alexonbandit
Copy link

alexonbandit commented Jul 19, 2024

So what I would do, is get yourself a Raspberry Pi Zero 2 W (the W is important to have WiFi and Bluetooth onboard). Install an OS on it and than install the above mentioned BLE proxy by following the instruction on the GitHub repo.
Place it near the car (you need to have WiFi in the garage).
Afterwards evcc or HA (can be placed wherever u want) can send http commands to the proxy which than forwards the command via BLE to the car. Works really well! I also have almost zero experience in programming and it took me app. half a day to get it all working

@laenglea
Copy link

Hi, everyone!
I just read the most amazing thing about the TeflaBleHttpProxy and the commandProxy. It's such an easy solution! All you have to do is add it to the evcc.yaml file.

I paired both Teslas to the proxy and am happy to report that I can control them through the proxy with no problem at all! All I have to do is use this simple command:
curl -X POST "http://IP:PORT/api/1/vehicles/VIN/command/charge_start"
I also added the commandProxy: addition to both cars and started playing around with Fast Charge/OFF to make sure everything is working as it should. So far, so good!

After starting evcc, the first car receiving the command is working great! However, the second car is raising the API error '429 Too Many Requests'. I tried several times and noticed that it really only depends on which one was controlled first. Is there someone else with this behavior?

@andig should i create another issue for this?

Thanks
Alex

@andig
Copy link
Member

andig commented Jul 20, 2024

Needs trace log file for tesla, please open new issue.

@Dragonkit

This comment was marked as off-topic.

@Eandy84

This comment was marked as off-topic.

@pssturges
Copy link

OCPP apparently confirmed to be coming to TWC3

https://www.solarquotes.com.au/blog/tesla-ev-charger-sa/

@BM183
Copy link

BM183 commented Oct 21, 2024

Hi all, I'm interested in getting this working with an ESP32/ bluetooth proxy.
I've seen these projects exist:
https://github.com/yoziru/esphome-tesla-ble
or https://github.com/robin-thoni/tesla-ble-esphome
Is that possible to combine something like this with EVCC and its tesla commandproxy? Thanks!

@andig
Copy link
Member

andig commented Oct 21, 2024

Du kannst jeden Proxy nehmen der das Tesla API nachbildet. Getestet ist https://github.com/wimaha/TeslaBleHttpProxy, ob die anderen das auch tun musst Du selbst heraus finden.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devices Specific device support prio Priority
Projects
None yet
Development

No branches or pull requests