-
Notifications
You must be signed in to change notification settings - Fork 7
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
Loss of Energy Controls - Error fetching Teslemetry Energy Site Info XXXXXX data: Multiple 5xx failures #151
Comments
Hey Mark do you have any evidence that other services work when Teslemetry doesnt? I am thinking I'll need to start running a test with Tessie, Teslemetry, and the Fleet API directly to see if there is a correlation. Here is the number of status 500 messages for energy sites over the last 7 days and the number of users it impacted. A small number of people constantly have issues, but there are also spikes. |
Ongoing issue. I mainly use teslemetry for my controls exclusively so haven't noticed the effects on any other platforms. Is there user ability to reduce or back off the numbers of requests being sent in my behalf?
|
Its probably no help, but you have more errors on the energy APIs than any other Teslemetry user. Today you have been 45% of all 5xx errors on the energy APIs. Every single one, was a response from Tesla saying My only two theories are: there is a connectivity issue to your Powerwall, or because you are frequenty changing your configuration, the powerwall itself is unable to respond to API requests at times. I will continue to monitor. |
Does it still show up in your Tesla app or products endpoint? There is a seperate issue where I need to do device cleanups. |
Looks like NetZero is seeing increased 5xx errors as well: |
Checklist
Describe the issue
As reported in Discord the Tesla site is returning 500 status errors, which results in the Energy controls going unavailable.
I'm wondering if a delay between calling for live_status & site_info may smooth things out a bit?
Reproduction steps
Config log attached.
config_entry-teslemetry-9148783ba548ef27e70b73108cd5fd97 (9).json
Debug logs
The text was updated successfully, but these errors were encountered: