Tesla has stated that this error is caused by too many requests to their API/vehicle over a period of time. When I turn off TeslaFi logging the error ceases to occur. Within 24 hours of re-enabling the logging from TeslaFi the error starts to occur in a regular cadence. This did not used to be the case but maybe something has changed on Tesla's API that is causing TeslaFi to exacerbate this issue.
This was posted on the TeslaFi support forum multiple times last week and has been deleted by the mods. Very suspicious and I will be discontinuing my subscription until I here a proper response from support or some confirmation that this is not caused by Teslafi. The last time this was posted it was moved to the helpdesk and immediately closed with a blunt statement that TeslaFi is not responsible. If this is the case please post publicly so that others can be informed rather than hiding it away.
This was posted on the TeslaFi support forum multiple times last week and has been deleted by the mods. Very suspicious and I will be discontinuing my subscription until I here a proper response from support or some confirmation that this is not caused by Teslafi. The last time this was posted it was moved to the helpdesk and immediately closed with a blunt statement that TeslaFi is not responsible. If this is the case please post publicly so that others can be informed rather than hiding it away.