@David-Baldwin said in S+ parkrun: getting the “Maximum amount of SuuntoPlus apps enabled” error Try to hold upper button for 12 seconds to soft reset, then sync the watch with the app. See if you can enable it afterwards.

@2b2bff good question. For the first three points I have no idea where to look to be honest.

Like said, it can be done but quality will most likely be bad, meaning you will get either too many or too few turn instructions. The komoot route? No, it’s not bad and quite usable. Have you actually tried it? (There is no room in a gpx file for tbt alerts afaik. All other brands also use fit for this)

After the 2.50.28 update, I also have some battery drain issues. It’s not as bad as what you guys have, but the battery goes down twice as quickly as before.

@Antoine I had an idea to measure this, but haven’t gotten around to it yet. Honestly, measuring power consumption properly is not as simple as it looks. Battery percentage is a very subjective metric, especially just on-eye observation. To do it right, we would need to use a multimeter and run controlled A/B tests (baseline vs. tracking in background/UI) across different devices multiple times. That’s the only way to get real consumption milliamp numbers instead of just rough estimates. But 3% per hour looks great for continuous live tracking.

Oura !! Since 3.8.0 iOS beta app, ascent of ski resort is not counted in stats. Total distance is still counting lifts travels, and ascent is visible in detail, but not counted in app stats (but counted on watchface - vertical week one for instance). In ski mode modification, ascent is not visible. I need to now change to run for instance to set ascent to 0 (works without registering modifications) and then put it strait back to ski resort before registering

@SamuelP @voigas My watch is fine too, but hers isn’t. We trained together and I saw her watch, so it’s not something fake or something

@Jose-Luis-Merino-Parra wasn’t sure how I’d feel about the white ones from the website, but this looks great!

@cheetah694 AI analyse of a fit file (run) especially the record.cvs file from it : The Data Verdict (DFA a1) • Why Garmin is right: Raw data from your record.csv file shows your Aerobic Threshold (VT1) is at 148 bpm, exactly when the heart rate complexity index (DFA a1) hits 0.75. Garmin uses this value to end your Zone 2, matching your real-time physiology.  • Why Suunto is wrong: Suunto sets your threshold at 130 bpm. At this heart rate, your data shows a very high DFA a1 (>0.85), proving your body is still in a state of ease. Following Suunto would unnecessarily restrict your training. • Anaerobic Threshold (VT2): Your data also confirms you enter the critical (anaerobic) zone at 161 bpm (DFA a1 = 0.50), once again validating your Garmin Epix settings.

@herlas Thank you for these details, I counted my Assioma pedal equipment and it is unfortunate that the Run does not record the cadence. Have you used the training programming in walking class? Is there only this screen? I find the texts very small! [image: 1770463945743-suunto-run-lime-intervals-grande.jpeg]

@sky-runner it remembers an old experience with my Spartan Ultra. Searching a lot with the community why it would have strange baro / altitude behaviours, while after repairing it was so perfect. It happens unfortunately that HW is just the cause. (fridge test was the eye opener in my case). It is also why it is important that when issues are raised by some (not you specifically ), Community users should also answer “no issue in the same circumstances”, to orientate the analysis. Good luck with repair / warranty.

was going to make a post about a similar issue I have. brand new Garmin hrm 200. connects to my watch and the heart+belt icon shows before I start an activity (and on hr graph during activity) but it actually just uses the watch sensor and not the belt, even while maintaining connection the whole time - I take watch off and hr goes blank even when hr belt still on and connected. belt works with zwift 0 issues so I know it’s something up with the watch. I have a sonic too and haven’t had problems with it only other than trying to be connected to multiple devices and the audio from the watch would go choppy - but since no issues. I think ultimately the Bluetooth connectivity or something with the software on the watch is the culprit of both our issues.

New branch of software is a bad idea. Same problem as with firmware - less frequent updates due to complexity. I see no issues using Ocean both for diving and other activities and all logged in a single app. Besides, lots of features like maps, notifications are universal to activities so having two separate apps would be worse than frequently updated one.

@Steven-Hambleton oh yes

@Mff73 I just tested it with a new battery, no improvement on the Race S side. I tried connecting the heart rate monitor to the “Elite HRV” Android app, same result : the frequency is detected for a few seconds and then the app loses the signal with the heart rate monitor.