-
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
Running Tesla Commands from Home Assistant does not work #901
Comments
Hi can you please add in the version of the integration you have installed in home assistant, latest isn't descriptive and given there have been a few releases in the last few days you could be on a few different potential versions. |
I have the same problem. I jsut installed this custom component and was hopign to change the Charging amps based on solar production but no commands works (honk,, etc.). I am running the latest version which is v3.20.3 (I just updated) but that problem was also on v3.20.2. Below are the logs:
|
I'm in the exact same case with solar optimization. Downgrading to 3.19.11 fixed the issue. I also noticed, twice, that if after a reboot I send a command while the car is awake then it runs fine, even if the cars goes to sleep after a while. |
I have tried that but still the car does not respond to commands. The asleep sensor is off so the car should be awake! It is a newer car (1 week old) in Europe but I don't see the error about requiring the new API. |
@flogitgeek can you send any command to your car and get a response? e.g. Unlock doors? If your car is that new there is a strong chance you can't use the unofficial API to send commands Edit read you other post, your issue is you have to use the new API to send commands so downgrading to an older version will not work for you |
Similar issue here.
|
Have any of you guys read the information about the latest releases and using the new fleet API for newer Tesla vehicles? The old APi can no longer control cars that Tesla migrated to the Fleet API. The new api requies the latest version and more extensive configuration. Please read the documentation. |
I was not getting the error listed in the documentation and wasn't sure if it impacted every regions as people could still use their integration from what I was reading on the home assistant forum. Maybe be best to update the documentation to clarify better? |
I thought about it, but the error seemed different, so I added my input. |
Actually, I was able to set the new solution up on my HA pi which is just a standard SD image setup. The challenge was more about getting all the domains into the right add on and performing steps in the right order despite the nested addons. |
My setup is HA in a docker behind a nginx proxy manager on another machine. |
Yes, Fleet Api requires a complex setup, i'm not sure if the effort will be worth the result... |
+1 on this issue. A few weeks back my car stopped responding to commands. All sensor data seems to work just fine. But pressing any button, toggle, dropdown, etc... nothing. Just get a similar error. Makes me sad, this is my favorite integration.
|
Have you read the README? It explains how to make this work with Tesla’s recent API change. Warning: it’s a complicated setup, not for the faint of heart. |
yes I have, an it requires the installation of two add-ons, which is not possible on my docker-based HA core setup |
Why it isn't? It seems I just did it on my stockpile of docker-composed containers. Just need one container and proxy if you don't have it already. |
Just type your name. |
ofc... then i make up completely the TAX ID also. |
Fully agree, it's my lack of capacity going beyond the basic readme. |
Same problem here. Also a brand new vehicle, one of the Highland edition Model3's, if that's a factor. |
This has been mentioned many times, including in this thread. New cars and in theory all cars at some point (bar some older ones) will need to use the Fleet API going forward. |
I've just updated the Tesla HTTP Proxy add-on to version 2.1.1 which removes the OAuth flow piece entirely. I hope this simplifies the setup for some people. Now the only "hard" part is figuring out how to host your public key. I recommend using Auth App For Tesla to generate the API token. |
That was actually best part of it, otherwise it would be enough to run original Tesla stuff. |
Thank you! Updated docs are also great - I understand where the complexity is now too (hosting the key). Is there anything obvious I'm missing here? (Before I spend a bunch of time trying to figure out how to make this work :) ). Does the Redirect URI need to be on the same domain? |
I'm going to take my question over to here, and stop spamming this issue: llamafilm/tesla-http-proxy-addon#3 |
For anyone getting a generic |
|
@BenoitDuffez you need to be using the fleet API like the error detail mentions |
@skipishere Maybe I am mistaken but I am just a user of the HA Tesla integration and I have no control over what API is used. I can't honk from HA because it seems the integration does not use the appropriate API. I'm not myself choosing either API and I have no control over this, but I could be wrong |
Please see https://github.com/alandtse/tesla#tesla-fleet-api-proxy for information about why and how to setup with regards to the API |
Indeed, thank you. Sorry about the noise, I thought I was helping :) |
Version of the custom_component
latest
Describe the bug
I'm trying to start and stop charge from home assistant but it does not work, logs below
Debug log
Warning! Logs in italian language!
The text was updated successfully, but these errors were encountered: