Jojo Posted July 28, 2019 Share Posted July 28, 2019 Description: login is currently not saved in the model 3 browser. After each browser opening, I have to type in the credentials again. it doesn't work in abrp and not on beta.abrp. Deleting bookmark and reload is also not working. Maybe it's a problem after Tesla update to 2019.24.4. Or did you change something? Tesla login works fine. I need abrp next three weeks working for Norway roadtrip! Thanks Link to comment Share on other sites More sharing options...
Jojo Posted July 30, 2019 Author Share Posted July 30, 2019 Something new? Can you reproduce the bug? It's very annoying, because when opening the browser the complete planning is calculated wrong, because settings not according account settings. Thanks Link to comment Share on other sites More sharing options...
Jojo Posted July 31, 2019 Author Share Posted July 31, 2019 Any news on this issue? The login is also not "stored" within Chrome Android browser. Whereas in Model 3 browser the input fields for the credentials are always empty after reload, in Chrome Android the credentials are stored within the browser, but you are not automatically logged in anymore. Something changed. Thanks Link to comment Share on other sites More sharing options...
Jason-ABRP Posted August 1, 2019 Share Posted August 1, 2019 Hmm, it seems to only do this when loading from a plan UUID. I will investigate. Link to comment Share on other sites More sharing options...
Jojo Posted August 6, 2019 Author Share Posted August 6, 2019 Hello Yes,I think, I know, what you mean. If I reload ABRP the first time, ABRP login is green right away. If I reload the browser during a running trip and want to look how my SOC compared to the planning, the login is gray. So the bug has something to do with a running trip. Thanks Link to comment Share on other sites More sharing options...
Jojo Posted August 8, 2019 Author Share Posted August 8, 2019 Hello Jason You did two updates of ABRP meanwhile. But ABRP is still not working in Model 3. Is it only me or does nobody else using ABRP in Model 3? To rephrase it: If I follow a plan on tour, each time I open the browser the plan calculates newly with a SOC of 90%. The browser does not start in the status of acquiring current live state of charge and showing it in the burn down chart. I have either to tap replan or even have to plan it new. It worked in the past. What's the problem? Is is the last Model 3 update? Thanks Link to comment Share on other sites More sharing options...
Jason-ABRP Posted August 9, 2019 Share Posted August 9, 2019 8 hours ago, Jojo said: Hello Jason You did two updates of ABRP meanwhile. But ABRP is still not working in Model 3. Is it only me or does nobody else using ABRP in Model 3? To rephrase it: If I follow a plan on tour, each time I open the browser the plan calculates newly with a SOC of 90%. The browser does not start in the status of acquiring current live state of charge and showing it in the burn down chart. I have either to tap replan or even have to plan it new. It worked in the past. What's the problem? Is is the last Model 3 update? Thanks My apologies, the last two weeks have been very crazy at my day job. I created an issue in our tracker, but haven't had time to address it yet. I'll see if @Bo (ABRP) or I can find time to take a look at it tomorrow. Link to comment Share on other sites More sharing options...
Jason-ABRP Posted August 9, 2019 Share Posted August 9, 2019 @Bo (ABRP) had a chance to look and fix this issue this morning: Link to comment Share on other sites More sharing options...
Jojo Posted August 9, 2019 Author Share Posted August 9, 2019 Hello About which problem do we talk? Mine is not solved. After each browser start in Model 3 the plan starts newly with 90% and not with the current state of charge. After replan or doing plan route it works, but this starts the planning with current position and current state of charge and so the burn down chart always begins new, which makes it pointless. Will upload a video of that issue. Thanks Bye Link to comment Share on other sites More sharing options...
Jason-ABRP Posted August 9, 2019 Share Posted August 9, 2019 There are several things going on here, first - we store the last plan in your local browser, that way when you reload the page, you've always got the last plan you did until you plan a new one. I don't think that's what's happening here, though. If you have a plan link bookmarked (Looks like: https://abetterrouteplanner.com/?plan_uuid=e5923eeb-9d6c-4f4c-b004-c08be1e8ca3b instead of https://abetterrouteplanner.com/) then you'll see exactly the behavior you're describing. On pageload, it'll immediately begin planning, but MyTesla takes a second to retrieve the first data point. The planning is faster, so it'll retrieve the plan before it can get your live data. If you change your bookmark to the main site, and load from a saved plan it should resolve your issue. Link to comment Share on other sites More sharing options...
Jojo Posted August 9, 2019 Author Share Posted August 9, 2019 Hello Thanks for your response. Now we can discuss. I use Abetter... and beta.abett... as bookmarks in Model 3. I already renewed these because of the issue, but it doesn't help. I never used an UUID link as bookmark. Currently (three weeks Norway roadtrip) I exclusively using saved plans. Everytime I reopen the Model 3 browser the right plan is loading correctly, no issue. But the burn down chart (right name? SoC chart) is always starting at 90%. It also shows the current SoC correctly and also at the right location/position within plan. But you than see planned SoC 88% and current SoC 63%. It only gets in line again after hitting replan (if it is presented) our hitting plan again. But than the plan starts with current position and the burn down chart is pointless. Video follows. Thanks Link to comment Share on other sites More sharing options...
Jojo Posted August 9, 2019 Author Share Posted August 9, 2019 See the behavior. Link to comment Share on other sites More sharing options...
Jojo Posted August 9, 2019 Author Share Posted August 9, 2019 (edited) Sorry, I wrote something wrong here. Edited August 9, 2019 by Jojo Link to comment Share on other sites More sharing options...
Bo-ABRP Posted August 9, 2019 Share Posted August 9, 2019 Ah, it seems like the issue is that the MyTesla API does not return the car SoC in time before the plan is executed. I'll try to solve it tomorrow. Link to comment Share on other sites More sharing options...
Jojo Posted August 10, 2019 Author Share Posted August 10, 2019 Hello Bo Thanks, but I'm not sure. You will know it better. But the current SoC is shown in the chart in green right from the reload if the page. But it is not taken into account by ABRP in that first moment. Let's see, what your fix will bring. Thanks Link to comment Share on other sites More sharing options...
Bo-ABRP Posted August 10, 2019 Share Posted August 10, 2019 I just released an attempted solution to this - the plan will now display "Waiting for position and/or car info" until it receives it, before doing the actual plan. Let me know if it works and if it breaks anything else! Link to comment Share on other sites More sharing options...
Raharney Posted August 10, 2019 Share Posted August 10, 2019 Thanks for all the good work. Link to comment Share on other sites More sharing options...
Jojo Posted August 10, 2019 Author Share Posted August 10, 2019 Hello Bo It nearly works, how it should. The SoC is now correct, burn down chart works and the route is not newly calculated from the latest "my position". Great job, thanks. But: the time schedule is wrong now. Each time I open the browser the plan begins with the current time, not with the time, when I started the plan. With the time it should be the same as with the position. First entry in the plan is the base with the location and time the plan was started at. Thanks Link to comment Share on other sites More sharing options...
Jojo Posted August 11, 2019 Author Share Posted August 11, 2019 Hello Bo, hello Jason Sorry to bother you again, but I'm really frustrated. Until around two weeks ago, ABRP planner works great in Model 3. Thanks for your effort and your commitment to this project. I know, it is not easy to do something like that besides a day job. Since two weeks ABRP doesn't work as it should, unfortunately exactly the two/three weeks, I'm on a roadtrip through norway, but this is my personal bad luck. There was the problem with too fast replanning after opening the Model 3 browser, before the live data was aquired. See posts before. Yesterday morning Bo fixed it and it works, but only yesterday. Today it doesn't work anymore. To be honest, I don't know if it's me or you changed the behavior by intention. Until two weeks ago all my plans always began with "my position". When I started they day trip in the morning, ABRP planner plans the route from the current position. After each browser reload, the start of the trip was still the initial starting point of the day with the initial "my position". The SoC burn down chart began with the initial SoC, the time schedule began with the starting time of the day trip. With the "recalculation", that is done when opening the browser, only the SoC was updated and the green line went along to the right side if the chart as the progress of the trip. I could see the same behavior yesterday after the fix of Bo, despite, that the beginning time in the time schedule for "my position" was always updated to the current time of reopening the browser. Today the behavior was different. With each reopening of the browser, the complete plan was recalculated and the current "my position" was set as the new starting point. Consequently the green line of the SoC chart was always on the left at the beginning. I could not compare the planning with the actual SoC, which makes the chart useless. I think we need three different trip/plan "refresh" strategies: 1. If the browser in Model 3 is reopened during a running plan. No new calculation, only update of SoC chart with live data. No update of initial "my position". No update of the current starting time. 2. Replan button appears: Without knowing the conditions for "Replan" exactly, I think it appears when I leave the path of the planning or the SoC deviates with a certain amount from planning. Recalculation of charging stops and time schedule. No new initial "my position". 3. Complete new calculation: Taking new current "my position" as starting point, new time schedule, new route. Strangely, I think, this it how it works until two weeks ago, but it does not right now. Thanks Link to comment Share on other sites More sharing options...
Bo-ABRP Posted August 12, 2019 Share Posted August 12, 2019 Allright, let's get this solved. If I understand you correctly, you have stored a bookmark for abrp including the ?plan_uuid=blablabla in the URL? And basically, you don't want that plan recalculated until you actually press "Plan", otherwise leave the old plan as it is? Link to comment Share on other sites More sharing options...
Bo-ABRP Posted August 12, 2019 Share Posted August 12, 2019 Released an update/fix now which will not recalculate the plan if it is the same as stored already. Let me know how you like it. Link to comment Share on other sites More sharing options...
Jojo Posted August 12, 2019 Author Share Posted August 12, 2019 No, no. As I wrote above, I never used uuid bookmark. The valid current plan is loaded according to the settings within my account on your server. That worked fine. I give you feedback, when I tried your fix. Thank you Link to comment Share on other sites More sharing options...
Jason-ABRP Posted August 12, 2019 Share Posted August 12, 2019 1 hour ago, Jojo said: No, no. As I wrote above, I never used uuid bookmark. The valid current plan is loaded according to the settings within my account on your server. That worked fine. I give you feedback, when I tried your fix. Thank you When we produce a plan, we set the URL in the browser to the returned plan's UUID, so when you re-open the browser in-car, the car reloads the page, which recomputes the plan. With @Bo (ABRP)'s update, it won't recompute the plan, and should pick up where you left off on the burndown chart. It may not have all of your historical driving data from the start of the trip, as that may get flushed when the browser refreshes the page. Link to comment Share on other sites More sharing options...
Jojo Posted August 12, 2019 Author Share Posted August 12, 2019 Good, good, I will try that. Thanks Link to comment Share on other sites More sharing options...
Jojo Posted August 14, 2019 Author Share Posted August 14, 2019 Hello Bo Yes, it's working better now. Not recalculating the route when just reloading the browser makes more sense. The burn down chart is getting updated, the first point stays the starting point. Well done. Did you change something on the time schedule? It still updates the time of the first point (starting point) to the opening time of the browser. The time of the route points should stay as we reached them, all route point of the future should be recalculated time wise. So you get an updated plan each time you open the browser. Is it clear, what I mean? Thanks Link to comment Share on other sites More sharing options...
