Jump to content

Katya (ABRP)

  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Katya (ABRP)

  1. Hi @PDXBob, @stocktroy, @CBenson,

    This is actually not a bug but a feature 😛 

    The settings option is called 'adjust speed' and can be toggled off / on in: Settings (detailed) > Speed

    Lowers consumption by lowering speed, thus lowers the number of stops.

    When the option is turned on, the legs of the route with reduced speed will be orange and you'll see the details on speed limit in the list of stops. 

    However yes, the detour in example 2 doesn't make sense. Likely the planner tries too hard to optimize the SoC for faster charging thus drives further to consume more. Not exactly desirable, we'll have a closer look at this.

    Update: we discovered the bug causing this and we've had the issue that resulted in the detour fixed.


  2. Hi @sengler,

    Sorry we didn't get back to you sooner! 

    I checked the logs and everything looks correct now. Normally it should only be in the 'registering' process for a couple minutes at most but it could vary depending on the connection to Tesla's servers. 


  3. Hi @Harald Friedrichs,

    Just to clarify, we don't support registering an ABRP account using your Tesla credentials. However you may create a connection between your Tesla and the ABRP account to be able to use live data and also send plans to your car.

    To link your car you'll need to have a 'saved vehicle'. You can create one in: Settings (detailed), instead of clicking 'select car model' click 'add my car'. You'll be presented the linking options after this.

    However if you've already created a saved vehicle, you can do the following;

    1. Go into: Settings (detailed ) > Car model
    2. Click the cogwheel to the right of your saved cars name
    3. If you're using a device with a smaller screen you may have to scroll down a little to see the linking options
    4. Select 'Link MyTesla' and login with your Tesla credentials, alternatively provide a token

    Having your car linked does provide a better experience and more accurate planning, but I'm curious if the connection issues aren't caused by something else. If you're still having issues could you describe how these problems were presented?


  4. Hi @NewTeslaDriver,

    If you want to add a specific charger as a waypoint it can be done in two ways:

    A) Click the charger on the map > Click "Add waypoint"

    B) First make sure you have the appropriate fast charger types selected in settings to be able to search and view the charger.
    Add a new waypoint > type in the name of the charger and the network name, example: "Sisteron Tesla" > Then click the suggestion in the drop-down that has a charger icon (it is recognised as a charging point).


  5. Hi @Ike Westbrook,

    It looks like we tried to plan a route without having any charging options available to us, but it's hard to tell exactly what happened without looking at the actual plan. If you encounter the problem again, or find any other oddity, please provide the link to the plan. You can either click share > share ABRP link or simply copy it from the browser 🙂 


  6. Hi @Comanche,

    1. Type your home address (in any of the address fields)
    ( It can be helpful to select a matching option from the drop-down to directly give the planner an exact location (with coordinates) as it in some situations can happen that the planner does not directly find the address.)
    2. Click the cogwheel to the right of the input address
    3. Click Set as > Home

    This will overwrite the previously saved address.


  7. Hi @Toma,

    I'm aware we replied to you on twitter but if anyone else has the same question;

    No, the useable battery capacity should be less than that number. Currently we're guesstimating based on experience but as we receive charging data we'll be able to analyse this and if needed make corrections. 

    Should you feel that our predictions are off somehow, do tell us and we'll look into what we need to change 🙂 


    • Like 1
  8. Hi @Zarax@AlistairB,

    Sorry for the confusion! Currently you would have to also enter either a time duration to charge for or a % to charge up to in order to have this change applied. If both power and time/% are input there should be no issue with the change. We do want to support the use case you're describing and it's on the list for future development.


  9. Hi @Gleb,

    I'm aware we resolved this on email but should anyone else be looking for the answer;

    The reason is we only fetch information for the following countries; Denmark, Finland, Norway, Sweden. Uppladdning.nu focuses mainly on the nordic countries and those are the best covered and most frequently updated, hence this restriction. So a charger in for instance Ukraine added in uppladdning.nu will not be added in ABRP.

    Instead, depending on what type of charger it is, these can be used:

    - openchargemap.org
    - goingelectric.de (only in German language)
    - supercharge.info (only for Tesla superchargers)


  10. Hi @Nicktesla87,

    We refresh chargers once every 24 hours, currently 5AM CEST to be specific. Hence the time it'll take for a charger to be added into ABRP ater having been added in OCM may be up to 24 hours depending on time of additon.

    I think the charger you added is this one: https://abetterrouteplanner.com/?charger_id=11062034

    Since it is a slower charger you'll need to let 'Type 2' be viewed in settings for 'Slow chargers'. We are going to add a region setting for slow chargers in Oceania but currently selecting 'Europe' will let you view 'Type 2'.


  11. Hi @Mark Verberkt,

    Could you perhaps provide a picture / screenshot of how the route is being covered? 🙂 

    Currently not, but it is something we could look into. Though, it is worth to mention that Apple are very restrictive with what we can and cannot do.



  12. Hi @Marc816

    I looked at your linked vehicle and it seems we haven't been able to fetch data from EVNotify since about 10 days ago [2021-01-23 17:14:09] so there must be an issue with the connection which in turn causes the position not to be updated. Have you tried to reconnect it?


  • Create New...