Model S REST API

[SeBsZ]

Just a heads up, most of the media controls are the same media_toggle_playback, those need to be changed to media_next_track, media_previous_track, media_next_favorite and media_previous_favorite.

 

[SG57]

Just a heads up, most of the media controls are the same media_toggle_playback, those need to be changed to media_next_track, media_previous_track, media_next_favorite and media_previous_favorite.

Doh, thanks. Copy paste blindness.

 

[SeBsZ]

Doh, thanks. Copy paste blindness.

Heh, but still wrong, I think. favorite, not fav right? Oh, and previous, not prev.

 

[SG57]

Heh, but still wrong, I think. favorite, not fav right? Oh, and previous, not prev.

Actually no the API endpoints are abbreviated like that, here's a snippet from the official app's endpoints container.

Spoiler

  "MEDIA_TOGGLE_PLAYBACK": {
    "TYPE": "POST",
    "URI": "api/1/vehicles/{vehicle_id}/command/media_toggle_playback",
    "AUTH": true
  },
  "MEDIA_NEXT_TRACK": {
    "TYPE": "POST",
    "URI": "api/1/vehicles/{vehicle_id}/command/media_next_track",
    "AUTH": true
  },
  "MEDIA_PREVIOUS_TRACK": {
    "TYPE": "POST",
    "URI": "api/1/vehicles/{vehicle_id}/command/media_prev_track",
    "AUTH": true
  },
  "MEDIA_NEXT_FAVORITE": {
    "TYPE": "POST",
    "URI": "api/1/vehicles/{vehicle_id}/command/media_next_fav",
    "AUTH": true
  },
  "MEDIA_PREVIOUS_FAVORITE": {
    "TYPE": "POST",
    "URI": "api/1/vehicles/{vehicle_id}/command/media_prev_fav",
    "AUTH": true
  },
  "MEDIA_VOLUME_UP": {
    "TYPE": "POST",
    "URI": "api/1/vehicles/{vehicle_id}/command/media_volume_up",
    "AUTH": true
  },
  "MEDIA_VOLUME_DOWN": {
    "TYPE": "POST",
    "URI": "api/1/vehicles/{vehicle_id}/command/media_volume_down",
    "AUTH": true
  },

 

[SeBsZ]

Oh yeah sorry, I was looking at the capitalized titles.

 

[ACDriveMotor]

Has anyone else noticed that the format of scheduled_charging_start_time changed with the latest FW? Previously it was a numeric value and now a string. Pretty easy to detect and correct across FW versions but otherwise an annoyingly arbitrary change.

 

[SG57]

@ACDriveMotor , yes I received reports of that last week, latest firmwares now use a string format for the scheduled time (yyyy-MM-dd'T'HH:mm:ss) instead of a timestamp.

Interesting to note is this breaks the official app as it expects a timestamp with no support for a time string.

 

[ACDriveMotor]

@SG57 Yes, I coded it so it detects and works either way. I don't want to have to update again in case they change it back.

 

[dpskipper]

Not the first time the firmware department don't bother leaning across their desk and speaking to the app department

 

[dailo]

That explains why the app doesn't show the scheduled charging time anymore

 

[SG57]

So Elon's tweet confirms new Summon features coming to AP v2+ hardware vehicles in about 6 weeks from now. Looking forward to them, however I don't have a AP v2 vehicle, I just missed that boat in 2016 by 6 weeks :'(

I guess this means one of you lucky ducks will need to do the dirty work on actually testing anything discovered from the official app's source

 

[SG57]

Can anyone with a Model 3 confirm they are able to track their vehicle's live location while driving in the official Tesla app? Or if perhaps if there's a setting in the car that disables streaming? Try turning Summon off and try again, and the energy saver / always connected settings.

I'm seeing the official app set the initial position (from the drive state), but after sniffing traffic I'm seeing it fail to connect to the streaming endpoint with a "vehicle_disconnected" error. This is the exact same issue I've been seeing with Model 3s the past month in my own app I posted about earlier, trying to confirm this is a Tesla server-side error or not so anyone able to help would be great.

 

[bsproul]

Can anyone with a Model 3 confirm they are able to track their vehicle's live location while driving in the official Tesla app? Or if perhaps if there's a setting in the car that disables streaming? Try turning Summon off and try again, and the energy saver / always connected settings.

I'm seeing the official app set the initial position (from the drive state), but after sniffing traffic I'm seeing it fail to connect to the streaming endpoint with a "vehicle_disconnected" error. This is the exact same issue I've been seeing with Model 3s the past month in my own app I posted about earlier, trying to confirm this is a Tesla server-side error or not so anyone able to help would be great.

It tracks my car in the official app, but I'm guessing it polls the drive_state endpoint as it seems to update every ~5s.

 

[ACDriveMotor]

Anyone have the speed_limit REST endpoint? I couldn't find it with search.

 

[apacheguy]

Anyone figured out the streaming API on the M3?

 

[ACDriveMotor]

Anyone have the speed_limit REST endpoint? I couldn't find it with search.

Nevermind, found it here in this thread. Not sure why forum search failed me. Bing/Google found it.

 

[SG57]

Anyone figured out the streaming API on the M3?

I've been debugging Model 3 streaming API for weeks now to no avail. After exhaustively snooping the official Tesla app and @bsproul 's account of ~5 second location updates (indicating drive state updates not streaming updates), I can only conclude streaming API is broken for Model 3s.

I'm seeing the exact same "vehicle_disconnected" results when using the official Tesla app as we see when connecting ourselves. Some times I have observed a "Vehicle is offline" value instead of the "vehicle_disconnected", but I've never received a success case on my own attempts or through using the official app only for Model 3.

I encourage all Model 3 owners to try out the official Tesla app and test if the Location screen is working as intended, meaning you get real-time updates including speed. Better yet if you're technically-minded try connecting to the streaming API yourself and witness successful data updates or failure due to "vehicle_disconnected".

 

[insaneoctane]

Does the API support changing the charging start time? I can't find it, but it seems like a pretty fundamental need. If the answer is "no", then are all the apps that support changing the start time just manually starting the charge at the new time from the app/server end? Sounds crazy to me!

 

[dpskipper]

Does the API support changing the charging start time? I can't find it, but it seems like a pretty fundamental need. If the answer is "no", then are all the apps that support changing the start time just manually starting the charge at the new time from the app/server end? Sounds crazy to me!

That's how I do it...
It's the only workaround I've found.

 

[nasatech]

Does the actuate_trunk work on Model S / Model X? Always get invalid_value when trying.