Suunto app Forum Suunto Community Forum
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    New Suuntolink to Replace Moveslink2

    Scheduled Pinned Locked Moved Ambit
    84 Posts 25 Posters 7.8k Views 25 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Dimitrios KanellopoulosD Offline
      Dimitrios Kanellopoulos Community Manager
      last edited by

      Thanks. I’ll ask and investigate this for you

      Community Manager / Admin @Suunto
      Creator of Quantified-Self.io
      youtube.com/c/dimitrioskanellopoulos
      https://instagram.com/dimitrioskanellopoulos
      https://www.strava.com/athletes/7586105

      lexterm77L 1 Reply Last reply Reply Quote 2
      • lexterm77L Offline
        lexterm77 Bronze Member @Dimitrios Kanellopoulos
        last edited by

        For A3P (pid001b) sample id 31 bike power (uint16) data type is same as on S series, there shouldn’t be a reason whatsoever for excluding it from transfer to SA, uint16 is datatype on S9B because thats how is transfered from powerpod(s).

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          margusl @lexterm77
          last edited by margusl

          @lexterm77 said in New Suuntolink to Replace Moveslink2:

          there shouldn’t be a reason whatsoever for excluding it from transfer to SA

          Oh but Suuntolink does not exclude power data, samples are sent to SA service, though summary values (min/max/avg) are indeed missing - https://forum.suunto.com/post/57611
          Apparently it doesn’t make much difference at SA service end nor in app itself.

          The way I see it, roles and responsibilities between Suuntolink and Suunto App are quite different when comparing data flows during syncing, at least for Ambits.

          Suuntolink uses different API endpoint for syncing activities, something specifically crafted only for Ambit line (or at least it seemes it’s currently used only for Ambit line). So Suuntolink is free to send out pretty much anything it can and crafting something SA-compatible out of it is the role for that Amibit-specific-API-endpoint. In a way it’s quite neat, in theory it adds possibility to add Ambit-specific pieces to Suuntolink sync layer without touching that part in mobile apps (less braking changes and test cases for SA, less affected users when something goes wrong). And handling most of that data processing/transforming at server side with a piece that only affects Ambit users has the same benefit, there’s less risk breaking things for majority of users. And generally such proxy layers are also helpful for keeping down the complexity of data models.

          But for end users it just means that if something is taken as granted for Spartans/S-line, it might take a looong time (infinity in the worst case) before it gets (re)implented for Ambits in SA.

          1 Reply Last reply Reply Quote 1
          • fethiyetourF Offline
            fethiyetour
            last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • First post
              Last post

            Suunto Terms | Privacy Policy