komoot ConnectIQ app = no turn-by-turn navigation

(in both cases watch set to "Follow Course" as I want to follow the course I've pre-made)

Routes sync'd from Strava (starring the route in Strava, automatically syncs with Connect, then to the watch) = turn-by-turn navigation prompts, works fairly well. Not perfect (likely down to the underlying map data) and is also a pain that starring a route sends it to ALL my Garmin devices - despite me never wanting a run on an Edge unit or ride on my fenix etc.. but does the job.

Routes sync'd from komoot using the ConnectIQ on-device app is a much tidier way of doing it (ie. just pull down the routes I want to the device I want).. only problem is no turn-by-turn navigation - just shows the course on the map (accurately) and you follow the line without any prompts.

I seem to remember from the past, back in early Strava days, this was a product of the route not having been processed through Connect first - same thing here?

This is not the case with the Edge unit (1030), using the komoot on-device ConnectIQ app to pull down routes has them routing with turn-by-turn just fine.

I also know there is the option to link up komoot and Connect so as newly planned routes are automatically sync'd across, and suspect this might make the turn-by-turn work (?), however this makes the mess problem even worse than Strava as EVERY route I plan on komoot will sync to EVERY Garmin device I own!

Anyone had better luck/experience?

  • So I messed up my test - despite creating a fresh dummy komoot account in a private browsing window.. when I connected it to GC it has connected my main account.. you can guess what happened!

    = came to the same conclusion as you, all routes (past/future) sync'd to GC then to device no matter what.

    What I've also found, in terms of duplicates, is that the route itself seems to be kept in sync between komoot and GC (name of route, contents etc), however the device sync queue gets messed up..

    When you create a route in komoot, when you click save but BEFORE you've confirmed the name of your route (default suggestion is "From A to B"), this syncs to GC and adds "From A to B" to your sync queue (of every device). You then name it as you choose ("My great route") and hit ok, this sync's across to GC with the new name (and in most case overwrites/renames the "From A to B") however it then adds "My great route" to your sync queue (for every device) in addition to the already there "From A to B". This means when you sync each device it will report a failure, because "From A to B" doesn't exist anymore.

    Again, seems more a GC issue rather than komoot.

  • Agree. I think I was so quick in renaming that I just got  multiples named!

    I've set a new post and emailed support. I'm pretty sure this is changed behaviour as I used Komoot a lot last year, and PAR, and I'm pretty sure this didn't happen/

  • Not the answer that you expect but it's the same thing here.

    If you have f6  in route mode it doesn't have turn prompts. If you have F6 in map mode it will process the route and you will give you primpts. However in map mode it will take a lot of time to process the route (komoot export a lot of points) and it could give you a different route. The komoot map is not the same has the F6.

    In the edge it will process the route, in my explore it could take up to a minute to process. And this will give you primpts.

    When you import komoot by using connect app, the app will process rhee track and put the prompts. 

  • Thanks, I'm keen to use "follow course" as I want to follow the route I've (sometimes!) carefully planned, as opposed to an interpretation of it. I see this as less of an issue for cycling - no matter what platform is used there's a fair chance the roads on the underlying maps will mostly be the same, therefore the route will be the same - yet for trail running and hiking the trails are much less defined and inconsistent across platforms, hence the preference to follow a course as opposed having it potentially re-mapped.

  • Thanks, I'm keen to use "follow course" as I want to follow the route I've (sometimes!) carefully planned, as opposed to an interpretation of it. I see this as less of an issue for road cycling - no matter what platform is used there's a fair chance the roads on the underlying maps will mostly be the same (give or take some metadata anomalies), therefore the route will be the same - yet for trail running and hiking the trails are much less defined and inconsistent across platforms, hence the preference to follow a course as opposed having it potentially re-mapped.

    I'd also presume for complex long courses, say an ultra, there would be battery hit too doing the nav. calculations on-device (?).