James Gragg

@Bre77 Possible it worked on the old Fleet API data. Not currently populating these fields into vehicle_data but may be added in the future.

@Bre77 This is now supported on firmware 2025.2.6+ (Pro account needed)

@jlpouffier This takes awhile to roll out globally. If you're still missing media data, please email [email protected] with your VIN. Thanks!

@patrickdemers6 Just saw a similar issue and snagged the VIN and timestamps. Check ticket SUPPORT-148.

> I suspect this entity will need to be removed since Tesla doesn't provide this via the Fleet Telemetry. > > Right [@stx](https://github.com/stx)? Hopefully this is coming via Tesla. And...

Yeah, looking at the times when data is sent by Fleet Telemetry (along with the car timestamps of those data points), and looking at when Fleet Telemetry reports Connected/Disconnected, there...

SoftwareUpdateScheduledStartTime has the same issue. I think reporting a Unix UTC timestamp (regardless of how it's achieved) is the most friendly and sane thing to do. But considering this is...

Actually, I don't think timezone interpretation fixes this. Example with SoftwareUpdateScheduledStartTime: Fleet API: 1739692800553 - Sunday, February 16, 2025 8:00:00.553 AM GMT - **Correct** Fleet Telemetry: 1739700120 - Sunday, February...

Example for ScheduledChargingStartTime... Fleet API: 1739650500 - Saturday, February 15, 2025 8:15:00 PM GMT - **Correct** Fleet Telemetry: 1739682900 - Sunday, February 16, 2025 5:15:00 AM GMT - **Wrong**

@patrickdemers6 In addition to the timezone mismatch, it seems like there's an additional 2-minute offset happening: Scheduled time: Friday, February 21, 2025 11:55 AM PT Fleet API scheduled_time_ms: 1740167701092 (Friday,...