It would be really…REALLY…useful to have a tesla fleet telemetry server hosted within HomeAssistant to work in conjunction with the existing fleet-api integration. Currently, the fleet API data requests can add up quite quickly, resulting in exceeding the initial discount amount. Using the telemetry API would likely significantly reduce the cost while also improving update rates of the tesla-fleet integration.
Thanks.
Hi TheBob889,
How did you make it work? I tried to setup the API unsuccessful since Tesla made it payable. I would be fine to get limited update… but I wasn’t able to…
BR,
Siminhui
It was a bit of a schlep tbh. Though I know my setup is a little more complicated than it needs to be if all you want is fleet API to work.
There is pretty good documentation (Tesla Fleet - Home Assistant) now and you can use https://fleetkey.cc/ to host the public key which saves having to have your own domain.
Hope that helps.
I would second this as the fleet-telemetry server is available as a docker container. Having it in HA should help the entire story.
My understanding is that you can avoid many of the issues, primarily cost by having your own fleet-telemetry server, though there seems to be some indication of some functionality not in the server.
I already have a docker setup outside of HA so I’m going to go that route.
I have two Tesla cars, solar panels, and 2 powerwalls so I am motivated. 
did you manage to implement the telemetry server outside of HomeAssistant?