Problem with wunderlinq integration
Hello Guido, since update 3.52 the app works very well with the handlebar wheel (1250 gsa 2020 and mini iPad 4) thank you. But there is a problem since the new version that was not there before, when I have finished a route, I cannot always see the driving time in relation to the start and the first stop or all the others stop (chronology). It's quite disturbing to obtain an exact timing of the route. One day it works, the other not.
Can you please look at this?
Thanks
Mike
Hello Guido, I put a screenshot where the timeline appears. Today it works but it’s random!
Good day.
Mike 
Hi Mike,
When you select a route for navigation, and "Guidance to route" is set to "Start" like in the screenshot, the Scenic will add a section to the route (from the nearest road to your current position, to the route start point). When I said "route" in my post above, I meant the route you saved, including that added section.
In the above screenshot, my current location is very close to the actual road, and guidance will start almost immediately. However, when you are not so close to the road, Scenic will start navigation yet. In stead, it will say "Go to route" (like screenshot below). As long as it says "go to route" your timeline will be empty, as Scenic does not know where you will join the route yet.
Now, as new coordinates come in (typically every second), it is possible that one of those coordinates is close enough to the route to start the navigation. In the current version this is 25 meters. So, if you get closer than 25 meters to the route, the "Go to route" will go away, and guidance instructions will start, and your timeline will also contain values. Before that time (as long as "Go to route" is there) it will not. It's possible that when you first start navigation, the GPS accuracy is not so good, and maybe the reported coordinate is further away than 25 meters. However the longer the GPS is on, the more precise the coordinates will get, and perhaps after a while, one of those coordinates comes within the 25 meter threshold, and the route guidance will start.
For the next version I will increase the threshold to 35 meters. I believe that will make a difference in your case.
Regarding your WunderLINQ problem. Indeed I believe this is not a Scenic issue. In fact, Scenic continuously checks for the precense of the WunderLINQ. If you turn off your WunderLINQ Scenic will give you a message "Remote Controller Disconnected". If you turn it on again, Scenic will give you a message "Remote Controller Connected". You can do this as many times as you want. In your case, it sounds like the WunderLINQ is turning off (or disconnected from power) and is not turning on again automatically. What happens with the WunderLINQ app? When the connection with the WunderLINQ cuts out, does the WunderLINQ app still show it as connected? Or also as disconnected?
Best regards,
Guido
Hi @mike,
I already answered you over email, but I'll also answer here so that it can help other people.
So, when you start a route while you are not close to a road (for example if you are inside or on private property with unmapped roads), it will say "Go to route", until you get within 25 meters (35 meters from Scenic v3.55) of the road.
As long as it says "Go to route" at the bottom, you will not get time and distance to destination and stops. This is because you are not on the route yet, so Scenic does not know when and where you will join the route, so it can not calculate the time and distance to destination:
Only when you are ON the route, you will see time and distance to destination and stops:
