Tesla Fleet Telemetry

&gt;At Tesla we believe that security and privacy are core tenets of any modern technology. Customers should be able to decide what data they share with third parties, how they share it, and when it can be shared. We&#x27;ve developed a decentralized framework: &quot;Fleet Telemetry&quot; that allows customers to create a secure and direct bridge from their Tesla devices to any provider they authorize.<p>Complete non-sequitur.<p>“We care about your privacy”<p>“Here’s a way to share private information with others”<p>Also, un-stated “there ain’t nothing you can do about sharing your private data with us”<p>Cool that they give you a way to access some of your data at all though, I guess

Every time Tesla refers to the cars they sold to customers as their ‘fleet’, I get the feeling they don’t really recognise they are no longer the owner of those vehicles.<p>Fleet as defined in Oxford Dictionary: “A number of vehicles or aircraft working together, or under the same ownership.”<p>(edit: use actual Oxford definition)

This is cool, I&#x27;ve been thinking about building an application that polls the reverse engineered Tesla API, but an officially supported solution sounds much better. Is there any documentation about how users authorize applications?<p>Seems like this allows vehicles to connect directly to your own server instead of having a Tesla server act as intermediary. Will it be free to use then? I guess Tesla is still footing the bill for cellular bandwidth used, so it probably won&#x27;t be free.

&gt; Fleet Telemetry is a server reference implementation. The service handles device connectivity, receives, and stores transmitted data. Once configured, devices establish a websocket connection to push configurable telemetry records. Fleet Telemetry provides clients with ack, error, or rate limit responses.<p>I assume this means that Tesla devices can be configured to speak the client end of this protocol, and that fleet operators might enable it. If so, that’s kind of neat.<p>Of course, it would be nice if <i>Tesla</i> telemetry non-fleet vehicles worked the same way and could be turned off.

congratulations your motor vehicle is now dependent on kubernetes<p>pov you are headed for a collision and something is wrong. you issue a describe command ...<p><pre><code> Type Reason Age ---- ------ ---- Normal Sync 100s (x3 over 100s) </code></pre> Is that an expected status for this component? The distance narrows ...

I may be missing something but how do you get your specific client_config deployed to your car? The quickstart says, &quot;Share with Tesla&quot; - do you like send them an email asking nicely?

&gt; Tesla strongly encourages providers to only collect data they need, limited to frequency that they need.<p>If only...

I wonder if they started building this API to comply with the newer Massachusetts right to repair law, then just made it public when the feds told automakers to ignore the Massachusetts law.

Seems like the idea here is to provide a public API for third party integrations, which currently use a private API.

Based on the message spec[0], it doesn&#x27;t look like this can be used to track Full Self Driving disengagements which is a shame. However, for its intended purpose which is presumably to help 3rd parties (eg Hertz) manage fleets it seems like a boon.<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;teslamotors&#x2F;fleet-telemetry&#x2F;blob&#x2F;main&#x2F;protos&#x2F;vehicle_data.proto">https:&#x2F;&#x2F;github.com&#x2F;teslamotors&#x2F;fleet-telemetry&#x2F;blob&#x2F;main&#x2F;pro...</a>

That’s great and all, but I’d settle for my Model 3 Autopilot staying in its lane and not trying to slam me into the median.

I&#x27;m a kubernetes noob, in <a href="https:&#x2F;&#x2F;github.com&#x2F;teslamotors&#x2F;helm-charts&#x2F;blob&#x2F;main&#x2F;charts&#x2F;fleet-telemetry&#x2F;README.md">https:&#x2F;&#x2F;github.com&#x2F;teslamotors&#x2F;helm-charts&#x2F;blob&#x2F;main&#x2F;charts&#x2F;...</a><p>why do they do `helm repo add teslamotors <a href="https:&#x2F;&#x2F;teslamotors.github.io&#x2F;helm-charts&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;teslamotors.github.io&#x2F;helm-charts&#x2F;</a>` instead of<p>`helm repo add teslamotors <a href="https:&#x2F;&#x2F;github.com&#x2F;teslamotors&#x2F;helm-charts&#x2F;">https:&#x2F;&#x2F;github.com&#x2F;teslamotors&#x2F;helm-charts&#x2F;</a>` ?<p>isn&#x27;t the first one a webpage rather than a repo?

Wow this is a surprising roll-out. The k8s recommended deployment seems a bit overkill, perhaps thrown over the fence, but it shouldn&#x27;t be hard to knock out a much more manageable docker compose configuration instead.

Is there an accompanying architecture diagram that goes with this?<p>I&#x27;m not sure which bits and pieces are included without poking through the code

&quot;What Tesla really means by Fleet Telemetry&quot;<p><a href="https:&#x2F;&#x2F;www.reuters.com&#x2F;technology&#x2F;tesla-workers-shared-sensitive-images-recorded-by-customer-cars-2023-04-06&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;www.reuters.com&#x2F;technology&#x2F;tesla-workers-shared-sens...</a>