Closed EVGrokker closed 7 years ago
I tried a different approach after this bug emerged. I optimized the route to let EVTO establish the route, and it went north. I added a required stop at Bozeman, then optimized legs 2 and 3. When trying to optimize leg 1 (with a required stop in Elko) I get the Route Not Found error shown below.
I also started another support request from within the app, and it used the same trip ID, so I'm guessing that the trip has been updated to reflect the changes I made.
If I build the trip incrementally:
it works.
Did this ever get resolved? I assume you were trying to add a 4th segment to GJ? It worked ok for me.
EVGrokker mailto:notifications@github.com Friday, April 28, 2017 9:32 AM
v 1.2.0 (8)
Trip: Custer SD, [tz748o985djp09n86b06r]
Trip established with Manual mode.
Modeling a trip to Custer SD after reading about 4th Annual Sound of Silence Rally https://forums.tesla.com/forum/forums/4th-annual-sounds-silence-road-trip-black-hills-may-19th-20th-3 in Custer SD.
The trip ID as saved has an origin of Fremont, destination of Custer SD, with one required charging stop at Elko NV.
I'm trying to add a required charging stop at Grand Junction CO, but I get the following error:
direction svcs failed https://cloud.githubusercontent.com/assets/26678403/25537929/d0d3d2bc-2bfd-11e7-8b93-b6558c508089.PNG
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/aesculus/EVTO-App-Feedback/issues/339, or mute the thread https://github.com/notifications/unsubscribe-auth/AARS5LoG8AYBxsnsvaXaxliKbkyxSjzdks5r0hSvgaJpZM4NLtTB.
-- Chris Couper
The title said you could not add a supercharger. I thought it was the GJ SC but that worked OK for me too
If I follow the steps outlined in the first comment, this still fails as described. Ignore the saved version of the trip.
The dialog is displayed.
OK. I have duplicated this. Now to find out why.
Oddly if you use the sc search feature it works. This is because the routing uses the address. If you select the push pin Google first makes a special place ID for the location. That place ID fails. So it appears to be a Google problem and I will report it to them. Fixes of this type are uncertain. I still have one outstanding for the Beaver SC and it took 2 months before to get one resolved for another address.
Bug report submitted to Google.
v 1.2.0 (8)
Trip: Custer SD, [tz748o985djp09n86b06r]
Trip established with Manual mode.
Modeling a trip to Custer SD after reading about 4th Annual Sound of Silence Rally in Custer SD.
The trip ID as saved has an origin of Fremont, destination of Custer SD, with one required charging stop at Elko NV.
I'm trying to add a required charging stop at Grand Junction CO, but I get the following error: