[teslajsonpy.connection] 403: {"error":"account disabled: EXCEEDED_LIMIT"}

[madsdyd]

Hi there

So, I think I might have issued too many commands to my Teslas yesterday, and today, I can't use my custom integration.

The error in the UI of HA, when I tried to restart the integration is something like (my installation is Danish, so not sure about the english version): "Configuration failed. Check the log files".

I got lines like these in the extended log:

2025-04-27 10:46:38.988 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in 6:15:57 2025-04-27 10:46:38.988 DEBUG (MainThread) [teslajsonpy.connection] get: https://c03d64a7-tesla-http-proxy/api/1/products {} 2025-04-27 10:46:39.053 DEBUG (MainThread) [teslajsonpy.connection] 403: {"error":"account disabled: EXCEEDED_LIMIT"} 2025-04-27 10:46:39.054 ERROR (MainThread) [custom_components.tesla_custom] Unable to communicate with Tesla API: UNKNOWN_ERROR_403

I have two questions:

• Will these error go away "automatically", ie, will I get a new window of commands "tomorrow"?
• Would there be any way to propagate this information to the UI, to the benefit of clueless users like myself

Oh, and the reason I get too many commands is due to solar charging: For the last couple of years it has worked flawlessly by sending commands to the car - but even after reducing to max one command every 10 minutes, it seems I am able to break it. So sad :-(.

[skipishere]

You will need to check your Tesla Developer account, I'd assume that you've used up the free $10 monthly allowance so until that refreshes (or you add payment details/change the limit) you won't get any more information from the API

[skipishere]

Thanks to the way they've done it, it's more complicated than it should be. If you have a Tesla Powerwall you can get the car and battery setup to charge using the app (it's pretty poor though from my attempt to use it) otherwise some people use the local BLE which doesn't have limits or cost (it's on my list of things to try myself at some point)

[madsdyd]

Thanks a lot, this makes it a lot easier to understand. Apparently, it is "data" that I use all my money on, not commands.

Commands: 409 calls / 4.1% of bill
Data: 4583 calls / 92.1% of the bill
Wakeups: 19 / 3.8% of the bill

Do you (or others) have any idea what the data is, and if I can reduce it? I am running Teslamate as well, but that is on the old API, AFAIK (I have not changed anything related to the fleet api on teslamate, and it is not integrated into HA).

(I have added payment details, but would be great to have to pay for the data, as I am not really sure I am using it for anything?)

[madsdyd]

Sorry for mid-air collissions on the messages: Yes, BLE is also on my list (would love to hear about your experiences, if you get around to it), but the list is currently way to long :-(.

I don't have the powerwalls (I am in europe): I am using the Huawei Integration to control the cars through this Tesla Custom integration.

And thanks a lot for the hint. I added a card, and it now works flawlessly. Would like to reduce the data though, as I am not really sure I use it. But maybe that is me that just does not understand the way the integration works.

[skipishere]

I'm was still using the old API up until the point I could no longer issue commands anymore but I still get read-only data, mostly because I like being able to get the location information while driving (which I know would eat up the $10 allowance fairly quickly). In terms of what is using the data for you, possibly worth checking if the location while driving is your big user?

[madsdyd]

Ah, yes, if the Tesla Custom integration polls while driving I could see that going up. I don't use that in the HA system, AFAIR. And I am almost certain I still get it from the TeslaMate setup using the old api, so I could publish that using MQTT to HA. I think.

Thanks a lot, I will look into that. For now, I will use the monthly payment as a motivation to get the BLE stuff going.