@thanasis I can’t tell you that, I live in a flat area ahhaa

@zt_zzzzz thanks for the feedback. Why it happened: The indoor-riding move’s FIT declared sport = generic, and intervals.icu files a generic, no-distance move as strength training. It came out generic because: A watch move’s activity_name is empty, so the sport rides only in the activity-id byte. My earlier byte→sport map was copied from mobile’s GpxParser.SPORT_TYPE_MAP — which turns out to be an older, off-by-one, incomplete table (it says 19=Alpine when Suunto’s real id is 20, and it has no indoor cycling at all). So id 17 (Indoor cycling) fell through to generic → strength. Also fixed for strava. Pushed a v2.3.8 release with that, should be on github within some minutes. Hope you haven’t lost data. For info I don’t have anymore an ambit 2 to test. So I rely on users feedback.

@GiPFELKiND Download from apk mirror, then use ADB (you need to uninstall the higher version first). For now I have disabled automatic update as there seems its a new bug in the new version.

Yes, Never have to worry about plastic aging and breaking again.

I updated to 6.13.8 yesterday. And now it succesfully pairs. But somehow it get stuck in some sync loop and never actually sync the activities? Edit: Once again downgraded to 6.7.12 version and everything works…

@Ze-Stuart thanks for the input. Due to your suggestion it has been a long 2 week low sleep work to built an ambit app with claude ahahh Lot’s of reverse engineering. Not easy. I am missing just some points that if someone can help (I believe from Suunto would be easier, @pavel.samokha @dimitrios-kanellopoulos @isazi ) How does the firmware decide a rule is a browsable WORKOUT (listed in the WORKOUT menu) vs a normal pinned display app? Is it purely that the rule is wired to the PID_RUNNER_GPS_TEMPLATE_GUIDANCE display template, or is there another marker (a rule flag, a CustomModes tag, an EXERCISE_MODES_RULE field beyond the 6 bytes [RuleIdx][UseRule][LogRule] we see, an Apps-entry field, …)? What bytecode/data does the guidance graph consume to draw a segment (segment count, per-segment duration/distance/lap end, upper/lower target, target metric)? i.e. what is the .Binary a Category:"guidance" rule compiled to — its structure, or the App-Zone/VM primitives it uses that a generic app does not? Is the guidance .Binary a different bytecode dialect than a normal App-Zone app, or the same VM with specific built-ins/opcodes for segments/targets? (If the latter, the live community compiler might be able to emit it with the right source.) Full claude recap here. These features that were lost in the movescount transition, and I am trying to get them back to the community.

@zhangschmidt while looking for some material in order to get back some old movescount features like training plan I stumbled uppon what maybe was your site. You had a lot of material, which unfortunately is not up anymore, if you still have some of them ,specially in what would concern movescount training plans I would be keen to have it to see if I can reproduce something.

For the curious, while reverse engineering some features on the ambit, it is the POIs from the ambit that don’t contain altitude. Not linked to suunto app.

@margusl hello the link is not working! OK sorry the question is 6 Year old ;-(

@FredJ I see your point. And this is related to the fact that TSS is based primarily in duration and aerobic/cardio stress nor in muscular stress.

@Sebastiaan-van-leeuwen I have exactly the same problem with Ambit2 sync. This started yesterday and I’ve also re-installed Suuntolink without success. BR, tikru68

@Kutmore Same thing, support said the barometer was faulty, out of the blue I’ll try your method, thanks!! Edit: did not work, tried on another computer that never add suunto software as well, no dice. My watch is bricked, shame

Hi all, I have my Ambit 3 peak for about 6 years. first time the pressure sensor failed after using it for 4 years, then after a yearI sent it to refurbish because it is a good watch, its the best to keep devices that are working nice. But again one year after refurbishing it is failing again. I wish to disconnect the pressure measurement feature, because now the watch thinks its in verry high altutude and it doms the display and it is really annoying.