Purtroppo quest'informazione non è disponibile in italiano. Può essere consultata invece in English.

Connect your Coros account to Livelox

This guide describes how you connect an account from Coros's application Coros Training Hub with your Livelox account. By doing so, routes that you record with your Coros GPS watch will automatically be synchronized with Livelox when they are uploaded to Coros Training Hub.

How to do it

  • You record a route with your Coros GPS watch.
  • When the recording is finished, make sure that it synchronizes with your Coros mobile app. Read more how to do it at Coros.
  • Coros Training Hub sends your route to Livelox. It is ready after a few seconds.
  • Livelox does its best to connect the route to a class in a Livelox event (training or competition) based on the geography of the route and any uploaded start times or results. If the route is not automatically connected, you can edit the route under My events and connect it to the right class.

In order for it to work, you need:

  • A GPS watch from Coros.
  • A Livelox account.
  • A Coros account. If you don't have one you can create an account for free.

Setting up the synchronization

  1. Go to your account settings in Livelox.
  2. Under Connections to route-providing applications, click on the Coros link.
  3. Follow the instructions on the next page. You will be redirected to Coros Training Hub, where you have to approve that Livelox is connected to Coros. To do so click the Agree button. You might have to log in to your Coros account first.

Finished!

A few things to note:

  • The routes that you recorded before you connected Coros to Livelox are not synchronized to Livelox. Such routes need to be uploaded via a file in Coros Connect or Livelox.
  • Routes that are deleted or changed in Coros Connect after they have been transferred to Livelox won't automatically be updated in Livelox. You have to edit/delete them in Livelox as well. This is a feature that unfortunately is missing in Coros' API.
  • All routes will be transferred to Livelox, even the ones marked private in Coros Connect. Coros' API doesn't contain information about route privacy.