Brett Adams

The data is sent as protobuf, so you need to decode the raw data using the protobuf definitions in this repo.

You need to learn how to handle protobufs, and implement it in your server using the proto files from this repo. Here is a result I got from a google...

The announcement was about MCU2 vehicles. MCU1 is still discounted and still doesn't support Fleet Telemetry. Your service will need to keep supporting both.

The quote at https://developer.tesla.com/docs/fleet-api/announcements#2025-06-26-discounted-vehicle-data-pricing-update is: > The Model S and Model X vehicles which now support Fleet Streaming have previously received discounted pricing for calls to the vehicle data endpoint....

I suspect I know exactly what's wrong here. Ill get a PR raised to fix it. As an FYI you shouldn't need to call wakeup in automations, unless you're doing...

> would it be possible to make the sensors return the previous value after core restart (i.e. when Tesla Fleet integration is loaded) even if the car is sleeping? Its...

@JEMcats run `pytest ./tests/components/tesla_fleet --snapshot-update` in your dev environment to update the test snapshots and commit the `binary_sensory.ambr` file it will update.

You can use this as your documentation: https://github.com/home-assistant/home-assistant.io/pull/34911

@JEMcats sorry I made a bad assumption that your translations would be up to date. Delete the *.ambr files you generated, run `script/setup` then re-run the `pytest` command, this should...

So @JEMcats thanks for making me aware that this data even exists. After seeing this PR this morning I have gone and developed my own implementation independantly in the Teslemetry...