Tesla Fleet configuration issues

Configuration
1

Trying to setup the Tesla Fleet integration and having some issues on the Tesla Developer site. Few days ago I followed the instructions from Tesla Fleet - Home Assistant but messed up the key generation so Telsa wouldn’t accept it. I had got through the part of hosting the key on Fleet Key for Home Assistant and then creating the Application in Tesla Developer site successfully.

I’ve now created the correct key type and am trying to either update the existing application to point to the new fleetkey.cc hosted public key but it’s complaining that:
“Domain is not valid. Please ensure it is registered with a certificate authority, does not include “Tesla”, and is not being used with a reverse proxy setup”

The instructions for the integration talk about choosing between “Just for me” or “For my business” which I thought were the options I saw initially. On the Tesla Developer site I’m now seeing “Authorisation Code and Machine-to-Machine” or “Machine-to-Machine only (Recommended for Enterprise Only)” options instead.

I’m wondering if this is a change on the Tesla Developer site that has broken the existing process or if there’s something else wrong with what I’m doing? TIA

4 Likes
2

I have the exact same issue, hopefully someone has a solution

3

Yep, same issue here

4

Messaged FleetKey / Teslemetry; this is a known issue that they’ve raised with Tesla and are awaiting a response / fix.

5

Also having the same issue. At first I thought maybe DNS hadn’t fully propagated the domain name, but finding this thread seems to suggest that isn’t the issue.

6

this is still an issue it seems

7

Hi guys, Tried today and got the same issue. Have anyone solved the problem?

8

Hello everyone,

just to keep this topic hot, I have the same issue today.

9

Developer has told me that he’s not has any success with Tesla support. Guess we all continue to wait or choose one of the other options.

10

So after a bit of digging, and found this and made it work.
I would argue that it is even better because I host my key this way :slight_smile:

of course it requires that you have some way of accessing your server from outside, but I use nabucase and worked just fine :slight_smile:

11

hey there.

Thanks for the link.

I tried to setup this up but i get an “failed setup error”. i confirmed that my public key is being served correctly.
I’m guessing I probably messed up on the subsequent steps. How did you configure the API on Tesla’s developer website? On Allowed origin(s) i put just my Nabu Casa URL without any additional path since it was giving an error. Is that the correct approach?

Thanks

12

image
image849×740 26.8 KB

this is how it looks on tesla dev site.

Also, I redid the whole shenaningans here, all steps!

And in the step “Register your application as a Fleet API partner”
since I am (and my car is) in EU, I changed this link to the EU one.
This is not written in the steps, I just found it in some git or some other site comment
NA one:
https://fleet-api.prd.na.vn.cloud.tesla.com
EU one:
https://fleet-api.prd.eu.vn.cloud.tesla.com

13

Thanks for the additional information.
i figured out that i missed the “Register your application as a Fleet API partner” step.
I read through the documentation and honestly i’m not familiar with curl commands. Is there a tutorial on how to do it? is it as simple as just copy pasting the code into a terminal window?

14

i dont know anythign about them, i used some gpt help

i did all through powershell, gpt had to transform the curl commands to fit with PS syntax, and then i just took a step by step approach with it. asked gpt to descxribe what the next step is, what it does, what result i shoudl expect etc. and then we wnet command by command.