Step-by-step instructions for setting up Tesla Fleet API with DuckDNS, Nginx proxy and Tesla HTTP Proxy. Minimal prerequisites.

[jason-curtis]

I finally got my own setup working, so I figured I should share the steps that helped me get the Fleet API up and running on my setup. They're pretty rough step-by-step instructions, but they're more comprehensive than other instructions I've seen. I figured they might help some folks here (such as folks on the #976 thread).

Feel free to comment & suggest edits: [Google docs link] EDIT: see below; there's a Wiki page that I've contributed to rather than maintaining my own doc.

Also! Note that there's a brand-new Tesla Fleet integration that might replace the Tesla Custom Integration soon. For more, see discussion #1036 .

[alandtse]

Thanks for sharing. The Wiki is probably the best location for something like this. Dropping a link may work or just having the content there too so it's not tied to your google account.

[jason-curtis]

Oooh, that wiki is everything that I was looking for during this process, and it's more complete than my doc! Would you be open to linking to the wiki from more places like the repo README and DOCS.md?

[alandtse]

PRs are always welcome.

[jason-curtis]

cool cool. submitted #1049 .

[Wintherman]

Hi, I have a Model-Y which I could read values from before Tesla stopped the easy reading. I could check the Batterylevel and start other activities when it reach the charge_limit etc.
But know I need to get the Tesla_HTTP_Proxy up and running and I am using your very good step-by-step instruction.
But I get stuck when the Tesla_HTTP_proxy start up and says "Failed to start add-on
Port '443' is already in use by something else on the host." and I assume it is due to the NGINX run on port 443 since that is for HTTPS.
How can I solve this?
If I try with port 8099 on the Tesla-HTTP_Proxy it starts but the logs does not look nice and after a restart of NGINX there is no https://[mydomain].duckdns.org/.well-known/appspecific/com.tesla.3p.public-key.pem to be found.

I am not sure if this is a bug so I post it here under this discussion.

One more thing, anyone now where in the HA file structure I can find ".well-known/appspecific/com.tesla.3p.public-key.pem"?
//Håkan

[Wintherman]

My problem solved by follow the step-by step very careful.
Then at Enrolling the key to the car only works if configuring the NGIX with a dummy domain first and then restart NGINX after after starting the Tesla HTTP Proxy and the start over the again with Tesla credential and restat the NGIX again. Mayby not exactly like this but it works after some restarts...