In Australia (may be other places also?) a Tesla destination charging time scheduled along the route is not included in the total trip time calculations. For example, if there fast charger stops for 39 minutes total, and a Tesla destination charger at a hotel etc for 1 hour, that hour is not included in the total trip estimate so it will still say 2 charging stops, but total trip charging time will only say 39 minutes instead of 1 hour and 39 minutes. In the attached example, the Marlo Hotel charging stop of 1 hour is not included in the calculations.
App 4.1, iOS 15.1 however this was also happening before either of those updates.
This bug happens regardless of route, destination etc.
When calculating a route, the suggested route is as expected, however the total travel time including charge times is not including the 3rd stop at a Tesla destination charger.
Trip shows 3 charging stops and a 34 minute charge time total, however this only includes the first two stops (3 min and 31 min) and does not include the third 51 minute charge stop.
Therefore the total trip time is off by nearly an hour and can’t be relied upon if the trip is time sensitive for arrival time etc.
Running the app on iPhone 13 pro, latest iOS version and most recent app version
4.1.6 (however this issue was also on previous app versions)
Route link: abetterrouteplanner.com/?plan_uuid=ada51d3c-8984-43f5-8cdf-d3b7f9ed174e
Apologies for logging this as a bug a second time. I did not see an update to my original ‘bug’ report on the same issue, as the email notification went to my junk mail.
I understand now that destination charge times are not included by design, so please disregard the above report.
Hey Harlan, destination chargers are excluded from the plan by choice. The reson being that when you come to a destination charger you would in general do something else, you are not there with the main purpose of charging and thus it should not be added to the plan total. You will notice that the time when you will arrive to the next step of the plan is updated though so it will not create a problem that you arrive later than you thought or similar.
Hope this was an answer to you question!