-
Notifications
You must be signed in to change notification settings - Fork 5
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
TeslaException - Suddenly stopped working this afternoon #22
Comments
Unplugging and MCU-reset fixed the issue for now... |
Failed again today… I also noticed that in the Tesla app, I can’t set the amps below 5. Maybe that’s what’s causing the issue. I also tested setting amps above 5 but I still can’t send anything to the car. |
Which version of custom Tesla integration are you using? Are you using the Tesla Fleet API Proxy? More info here: https://github.com/alandtse/tesla Any more clue about the exception message? Do you know which API call triggered the exception? |
I’m using the latest integration |
Just tried resetting my MCU but that didn't solve the issue. Checked the logs:
|
Is there a config to stay with the Owner API? Or is that the default? To stay with the Owner API, you might need to reauthenticate, or try revert to your previous version of Tesla integration. |
I never had to reconfigure when the fleet api was released. I’ll try to reauth and report back. |
Removed and readded integration. |
Weird, this morning. Without changing anything it started working again… |
I have setup the automation today, I also see a TeslaException with the following stacktrace:
This is for Tesla custom addon, without proxy, MY 2024. When I decrease the charging power manually it works but something (the script?) sets it back to full power. |
Maybe something wrong with the sensor that measures the excess solar? W instead of kW? Had this issue in the beginning as well. |
Thank you, converting W to kW in my grid sensor helped fixing the TeslaException. Automation now keeps running, triggers force update from time to time, so far it did not change charging power, even if 2kW are pulled from the grid. But that's a good point to start debugging from, thank you. |
Ok just wanted to give an update. I found out that TeslaException was expected since I needed to setup Tesla HTTP Proxy to be able to send commands to the vehicle at all. I missed that part in Tesla custom integration. My template sensor with "kW" instead of watts seems not to be needed, I think TeslaSolarCharger even requires watts to work correctly. |
Ok I re-tested the automation today and my observations boil down to a improvement idea. I think there is kinf of a rate limit around Tesla API and calling it too often leads to the TeslaException and the script being terminated (leaving everything in an undefined state). What I observed today:
So the automation tried to send at least 5 calls to the API in 21 seconds. Now I have two ideas how this could be improved:
Update: Ok with a limit of apparently 50 commands per day both approaches would not fix it completey. There is also an interesting discussion on Reddit: https://www.reddit.com/r/homeassistant/comments/1dixaub/tesla_fleet_api_request_limits_how_are_you_coping/ |
Except for some minor hiccups which can be fixed with other automations, this blueprint has been working perfect for about 8 months now! Thanks for that!
However today the script stopped working, when I restarted it quits after some time with an error (see image below)
![Schermafbeelding 2024-06-14 om 13 18 37](https://private-user-images.githubusercontent.com/42653485/339748381-42d2e852-c834-41a0-a421-dfae2121d667.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU5Mzg2OTgsIm5iZiI6MTcyNTkzODM5OCwicGF0aCI6Ii80MjY1MzQ4NS8zMzk3NDgzODEtNDJkMmU4NTItYzgzNC00MWEwLWE0MjEtZGZhZTIxMjFkNjY3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTEwVDAzMTk1OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWY1YTAxZDAxYzkzMmIxMTE3YTFiNzc0MDE0MjBjYTYzZDZiYjc0YTNjYTE0MmFiZDYzNjU5ODFjYmVjYWQ2ZmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.c0CsHOL643GJzUTnhmgyZyov-5iaTAqkyQpVc6fZLxE)
I fear it's on the Tesla-side of things but any idea's on how to fix this are always welcome!
I can pull data from the car without any issues but I can't send anything. Changing the amps manually is returning an unknown error.
Thanks!
The text was updated successfully, but these errors were encountered: