Tesla Custom Integration & Fleet API

Third party integrations
1

Hi community,

I am looking for some help with installing the new Tesla Fleet API with Tesla Custom Integration as the old one is not supported on my car anymore.

So I understood I need to install a Tesla HTTP proxy, behind a dedicated subdomain, but the official documentation only explains how to do it with a couple add-ons: a Tesla HTTP Proxy add-on on top of a Nginx SSL proxy add-on.

But my setup is a core HA in docker containers which does not enable add-ons.
Also, my HA is behind a Nginx Proxy Manager running on a different machine.

So I have the feeling I must be able to set something up, but I just don’t know exactly how and cannot find the methodology.
Did someone do that before?
Can someone help?

Thanks!

1 Like
2

I’m in a similar boat to you.
I went through the setup and Tesla rejected my developer account.

I found this online, but havent tried it yet.

3

I’m running HA in docker and using nginx proxy manager as my reverse proxy (in its own container). I used this for the Tesla http proxy:

2 Likes
4

That might be the solution, but I got another one from Tesla first
image
Based on what I read it could be because my region (Belgium) isn’t supported yet.
:frowning:

5

Someone else had the same issue here: Unable to Onbeard? · Issue #67 · llamafilm/tesla-http-proxy-addon · GitHub
There might be more details on the error in the browser JS console.

6

Got confirmation of this one, using an address in the Netherlands did solve the onboarding issue :frowning:

7

Hi!
I am in a similar situation I guess. I have access to the sensors, but can’t send any command to the car, indicating I need to switch to the fleet API.
Now, I’m very new to this, and can’t really make sense of the steps to follow to get the fleet API…
Would you know any guide/video that would explain this bit by bit?
I have a HA green :slight_smile:

8

What’s your HA setup? Docker or HAOS?

9

Is it useful?

10

I could not register for the API, now I can, so it was extremly useful to me

11

How to operate

12

not sure I understand the question

13

How do you solve this problem， using Nginx SSL prxoxy duck dns？

14

OK…
So the “Address in the Netherlands” workaround is only about being able to register a valid tesla developer account to have a Fleet API.

For my setup I found the response in iainbullock/tesla-http-proxy-docker (github.com)

15

I found this well written blog article on how to setup the Fleet API for Home Assistant running on Docker: https://www.smartmotion.life/2024/04/23/tesla-custom-integration-with-home-assistant-on-docker/?v=6cc98ba2045f

4 Likes
16

Just found that I need to use the fleet API.
I’m running HA on an old laptop (Generic x86-64) and using Nabu-Casa for logging in externally.
I’ve installed the Tesla HTTP proxy thing, but thats as far as I got.
Please tell me the next steps aren’t as complicated as it looks!

17

Hello everyone,

I followed the entire registration procedure on the developer.tesla.com website, but when I got to the end of the OAuth 2.0 process, only the “Client ID” appeared, and there is no “Client Secret” anywhere. So, I don’t know what to enter in the configuration of the “Tesla HTTP Proxy” component…

Has this happened to you? Did I do something wrong? What can I do???
ttt

19

I also have the same problem! Did you find a solution?

20

You don’t need to choose the open-source software option.
Tesla support wrote to me:

Hey David,

Open source applications documentation will be released and updated soon! For now, you can create an application that is standard application for now until instructions are updated.

Sorry for inconvenience,

Jason
21

Is there any easier method on the horizon? I was quite happy with the Tesla Integration so far that just required to generate a token with my phone app.

Now all this exposing HA to the internet, SSL certificates, (reverse) proxy setup … WHY?

:pensive:

1 Like