FSD Stats

[swiffer]

The Tesla Team has added additional fields to the fleet telemetry repo for basic reporting of FSD usage - not sure if something is added for Owners API as well but would be greeat to have it added / logged to the database.

For now it's HW4 on Holiday Update only

teslamotors/fleet-telemetry@031553a

[swiffer]

Anyone out here having fsd indicator within their app and can verify if it's accessible via the owners api now?

Would be great a great candidate for logging this to positions and get some drive stats for it as well.

https://www.notateslaapp.com/news/4402/tesla-app-now-shows-live-animation-when-using-fsd

[3rdStng]

Yes. On HW3 and recently received v14 lite.

[3rdStng]

Happy to, I just need to know how.
Seeing the FSD Stats in Teslamate/Grafana would be amazing!

[cwanja]

Happy to, I just need to know how.

Seeing the FSD Stats in Teslamate/Grafana would be amazing!

Just know it's only from the point we include it in the software and a users updates. It's not historical and back filled.

[3rdStng]

Understood. The car does have some back history, so they've been collecting for a little bit. My screen shows over 6,000 miles on FSD going back to April. Yet I've only been on v14 Lite for 4 days.

[3rdStng]

Hopefully I did this right, and redacted the right content.
Basically, I did a GET https : // owners-api . teslamotors .com/api/1/vechicles/[VIN]/vehicle_data -H Authorization: Bearer [Access token] and piped it to a json file. Although the json formatting may have been lost when I removed my IDs and VIN.

PLEASE delete this post if there is anything I missed in removing.

raw_vehicle_data.json

[JakobLichterfeld]

Ty.

Thanks for the dump — very useful.

Two things:

Redaction: the identifiers are properly zeroed, but a few fields are still personal: vehicle_state.vehicle_name, (visible in your screenshot as well)odometer, vehicle_config.utc_offset (reveals your rough region), the timestamp / tpms_last_seen_pressure_time_* values, and speed_limit_mode.current_limit_mph.

Correct stripped:
drive_state and media_info were stripped intentionally — the former normally carries latitude/longitude and, with navigation active, active_route_destination, and the latter can contain now_playing_*.

FSD: unfortunately I don't see anything here that gives us the active FSD status. driver_assist: "TeslaAP3" only tells us the hardware generation, not what's purchased. smart_summon_available is not what we are looking for.feature_bitmask is undocumented and firmware-dependent, and the old option_codes (APPF/APFB) haven't been meaningful for Model 3/Y in years.

Perhaps there is something in the stripped drive_state

Edit: wait, the dump is from standstill. So no FSD active. I will brainstorm in the coming days and hopefully come back with a test version which will enable you to safely log full during driving.

[3rdStng]

I did not strip out drive_state or media_info. Anything I redacted I literally just zeroed out. Maybe nav has to be running to show the Lat/Lon data? Nobody was in the car when I ran the GET command .

EDIT: My page hadn't refreshed to see your edit. I'll try to coordinate a FSD and run the command to dump more.

[3rdStng]

I grabbed a new vehicle dump while FSD was running. I don't see much in there that will help. Unless there are different APIs needed to get the data. Let me know if you need me to test anything.
raw_vehicle_data_fsd.json

[JakobLichterfeld]

What exactly do you mean by progress? We have proven that the data is inaccessible.

[3rdStng]

I think it's only been proven that "/api/1/vehicles/{id}/vehicle_data" doesn't contain the FSD info. It could be a fleet api too and not an owner's api. Anyway to intercept the traffic going to the phone app while FSD is on?

[brianmay]

The fleet API is fully documented. e.g.

https://developer.tesla.com/docs/fleet-api/endpoints/vehicle-commands
https://developer.tesla.com/docs/fleet-api/fleet-telemetry/available-data

I personally don't see anything on FSD, but admit I might have missed something.

[swiffer]

Fleet API has Self Driving Stats - think that's how https://www.fsddb.com/leaderboard#most-fsd-miles has been built (fairly limited - miles since last reset according to git commit history in fleet telemetry repo of tesla).

-> teslamotors/fleet-telemetry@031553a

It had only been confirmed that its not part of vehicle_data (but could be part of the streaming data set), right?

[JakobLichterfeld]

Any progress on this @JakobLichterfeld ?

This does not add any value to a discussion, Dana.

As said above:

about a different API: yes, that's where I'd look next. The app's live FSD animation is far more likely fed by a realtime channel than by polling vehicle_data. The streaming API's subscribe call takes a column list, so speculative names (autopilot_state, fsd_state, autopilot_style, …) can be probed cheaply — accepted, silently ignored, or subscription rejected are all informative outcomes.

It could be a fleet api too and not an owner's api.

As Brian said: no, Fleet API is an officially well documented API. So these values are not fully there.

(but could be part of the streaming data set), right?

Yes, see above.