+3

API Request Frequency

rguptaca 3 years ago updated by odrotbohm 4 months ago 1

1st Thank you so much for implementing the API.

Some thoughts & requests.

  • Please document how long the lock out period is (code 1015)
  • Maybe allow "developer mode" for a limited time and number of times
  • Option to pay/temporarily pay for higher frequency and more API requests

I've been increasingly running into this problem recently. I'm building some charging automation, altering charge power based on the data I get from my PV system. It had polled that data every 30 seconds and potentially updates the charge power. Upon start, I might have to trigger three requests right after each other: current car state, start charging, set charge power.

Starting a while ago, I noticed that these requests immediately cause me to get a 429 Too Many Requests, although all subsequent requests are relatively modest (one every 30 seconds). I've also – unsuccessfully – tried turning down the polling frequency to 60 seconds, but it looks like the initial interaction pattern already breaks my use case, unless I artificially delay those requests.

I couldn't find any guideline about how many requests per time unit constitute “too many”. Also, it seems unspecified, how long the lock out period officially is.

Being able to set the charging amps with the start charging command would save me one request, too.