-
Notifications
You must be signed in to change notification settings - Fork 99
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
Failed to call service switch/turn_on. unknown error - Charger #1000
Comments
Not sure the Debug worked... information seems kinda useless for this issue... |
2024-06-14 09:58:45.062 DEBUG (MainThread) [custom_components.tesla_custom] Running controller.update() |
I'm having a similar error when trying to change the charging amps value. This issue appeared today as well, I haven't had any single problem so far... |
+1 here: can't update Amps and can't turn on/ off charging |
Can you perform any write actions (eg open boot, windows, charger door, etc)? |
It seems to work again now for me. Weird. Server down probably ? |
Still not working for me. No actions (setting amps or turning charging on/ off) and updates (eg started charging on the app and no update in Home Assistant) |
@vdiogo are you using the Fleet API? |
Don't know what the fleet API is sorry. I'm using this plugin combined with node-red in home assistant (with home assistant companion) |
Info about Fleet API if you're not using it and only get read data (and write actions fail) then you have to use the Fleet API |
Thanks buddy, will give it a try (was working until now, though) |
All commands not using Fleet API are now harder than ever to pass through... |
Hi there, I'm using Tesla Fleet API and after some time all action stop working. Can it be a throttling issue with the API?
|
@pmrosa did you check Tesla HTTP Proxy logs? I believe the 429 (too many requests, retry later) would show in there. You might need DEBUG level log. |
Just to add, had the same problem here, switching on charger, adjust maximum charge. [546329906048] Unexpected exception |
Really same symptoms as API rate limitations. My logs were exactly as yours... #959 |
I saw the logs and there was nothing relevant there but debug was off. I turned it ON now but the integration started working again since yesterday, what shows a little bit more that it should be rate limitation. It's bad because I have a solar surplus management in node red that can turn car charging on and off some times during the day :-( ... but not much (I manage that at node red) so the API should allow only a very limited rate :-( |
I also have charge on solar and I am seeing this although I had seen it before even without the car at home. |
Got it now on the logs with DEBUG on:
:-( |
5 charging commands only? Will this be the same when using the fleet API? |
This is USING the Fleet API. |
Same issue here. Did anyone try this with tessie or teslafi? AFAIK they use the fleet API as well but might have different limits? In general, using the Fleet API to change charging AMPs only should not fall under the 5 limits per day as it might be "Energy Settings Limits" and have 50k requests a day? |
File "/usr/local/lib/python3.12/site-packages/teslajsonpy/controller.py", line 1407, in __post_with_retries_except_unavailable |
Is there an existing issue for this?
I have read about the Fleet API and understand I may need to use it
Version of the Tesla component
3.23.0
Version of the Tesla car software
2024.20.1
Model
Model 3
Current Behavior
Attempting to start or stop charge using the "charger" toggle does not work.
"Failed to call service switch/turn_on. unknown error"
Tried restart HASS and reboot car.
First noticed today 14/6/2024
Expected Behavior
Car start or stop charging
Debug logs
Anything else?
car is Model 3 2019 with HW 2.5.
"Charger" toggle has worked for over a year with no issues.
Since last Tesla HASS Intergration update, the Climate Toggle takes at least 5 mins to change state in HASS, and rarely starts the AC in the vehicle, unless I open the Tesla official app.
The text was updated successfully, but these errors were encountered: