Ramon Posted May 2, 2019 Share Posted May 2, 2019 Description: I primarily drive on the Tesla navigation due to its better visualization. Since a few versions ago Tesla supports sending locations to the vehicle for navigation. It would be awesome if ABRP could automatically or suggest to manually push the next destination of the trip to the car. Currently I need to manually search the next destination while I'm on route. Which is especially annoying if the trip route changed due to traffic or just because you forgot to take the exit This is the API doco https://tesla-api.timdorr.com/vehicle/commands/navigation Use Case: I would use this *all the time* as I'm doing this manually at the moment. Link to comment Share on other sites More sharing options...
Bo-ABRP Posted May 2, 2019 Share Posted May 2, 2019 Cool! I just implemented a first version and added a button to the ABRP Share menu if you are logged in with MyTesla. Works, but we need to figure out how to send the lat/lon coordinates instead of an address, and preferably make the Tesla Navigation understand that we mean a specific supercharger. Any input on that is welcome! Right now we send the string "<lat>,<lon> (<name>)" as address, but it seems like the Tesla ignores the lat/lon. Let us know what you think. Link to comment Share on other sites More sharing options...
rochoje Posted May 6, 2019 Share Posted May 6, 2019 Does this send the whole trip to tesla navigation or just the next point? Link to comment Share on other sites More sharing options...
Jojo Posted May 7, 2019 Share Posted May 7, 2019 Hello I think, it's only the next point, because the API can only read one point at a time. I also recognized that Tesla ignores coordinates also if these are send from Google Maps. It can only handle complete adresses, that can be found one to one within the Tesla (Google?) database. Because of this, in many cases the transfer from Google Maps to Tesla does not work at all. Thanks Link to comment Share on other sites More sharing options...
dobbersp Posted December 17, 2019 Share Posted December 17, 2019 On 5/2/2019 at 7:06 AM, Bo (ABRP) said: Cool! I just implemented a first version and added a button to the ABRP Share menu if you are logged in with MyTesla. Works, but we need to figure out how to send the lat/lon coordinates instead of an address, and preferably make the Tesla Navigation understand that we mean a specific supercharger. Any input on that is welcome! Right now we send the string "<lat>,<lon> (<name>)" as address, but it seems like the Tesla ignores the lat/lon. Let us know what you think. Ran across this while searching for a way to cancel the existing trip when sending a new one. Currently, if you have an existing trip and send nav info to the car, it requires the user manually accept the new destination. You can send raw lat/long using the share api call. In case you were still looking for it: type = share_dest_content_coords and for properties, add a lat and long instead of android.intent.extra.TEXT Search for "sharerequest" here for details: https://github.com/jonahwh/tesla-api-client/blob/master/swagger.yml#L1117 Link to comment Share on other sites More sharing options...
israndy Posted June 29, 2021 Share Posted June 29, 2021 This seems like an important feature, I am surprised it's still not implemented Link to comment Share on other sites More sharing options...
Katya-ABRP Posted June 30, 2021 Share Posted June 30, 2021 Hi @israndy, The 'Send to Tesla' feature is implemented and available for users who've got a linked Tesla (through the tesla/mytesla linking option). However, due to the fact that Tesla do not handle waypoints we're still restricted to only sending one location at a time. At the moment you may share the plan (next waypoint) to your Tesla nav and once you've reached the destination, you may share it again to continue to the next waypoint. But, we'd of course like to do better than this. If you've got any suggestions they're more than welcome. /Katya Link to comment Share on other sites More sharing options...
