@2b2bff said: @dreamer_ said: Personally, I don’t see anything wrong with Suunto deciding to release watches every year if it helps the company improve its financial numbers. After all, Garmin has been doing this for a long time, and now Amazfit is doing it too. Perhaps the 2 year wait does not have any sense if you maintain the older devices. This is also common in other devices like smartphones. The key should also be to maintain support for older devices for a period of time. The faster pace you release new devices, the more devices you have to support… That is the problem about releasing devices in shorter intervals. Or perhaps the revenue is a lot more than the cost of maintaining an additional device. That is something that only Suunto will know…

@matus69 I don’t even touch my phone. It is in standby. Then I tap update in the widget, and the watch seems to fetch data via SA in the background.

@Squirrel correct, not a typo.

@Audaxjoe said: @André-Faria I work in car fleet management. We struggle to even get a car booked in for diagnostics in that time with Main Dealers. How would you feel if you contacted one of those dealers about a car and they would say, we fixed the issue. You would ask, when can I pick it up? And they would say, we have a release moment 4 times a year when all fixed cars can be picked up. Yours will be ready with the q4 release.

@muellersjens Did you check again your previous activity in the app? HR is computed in the backend and sometimes it doesn’t appear good initially (if appearing at all). After this, what is saying your watch logbook for zones duration for this activity? Correct or same discrepancy?

@Mikenizm I was comparing some of the four Mandatory Gas Time Alarms from my dives and found a dive where indeed things are a bit more complex and result in strange readings like the dive below. This dive intreged me as I was actually reading TANK PRESSURE: - - (0) during this dive at 33 meters. I can share the json if needed. [image: 1785558073201-screenshot_20260731_150907_suunto.jpg] Claude: There are two gaps in collecting data of this dive. The alarm fired 10 minutes in the dive at 33.27m. something structurally different then the other ones which were more in the 1 to 2 minutes alarm range at shallower depths. Dive context: deeper dive (max 34.36 m), and this time the first alarm hits at 9:30 into the dive. No elevated consumption beforehand — this wasn’t a noisy-estimate problem like the other files. Time Depth Ventilation GasTime 400–470s 21.6→28 m steady 0.0003–0.0004 steady 1280–1630s Then a real, extended data gap: Time Depth Pressure Ventilation GasTime 480.62–490.62s 28.7→29.6 m None 0 0 500.62–560.62s 30.6→33.0 m present, declining normally None None 570.13s 33.27 m present None None ← Alarm fires here 570.62–590.62s 33.3→33.9 m None 0 0 594.13s 34.1 m present 0.000188 37s ← alarm clears 600.62s 34.1 m present 0.000186 1729s What this shows: There were actually two separate dropouts stitched together: a short one at 480–490s, then a long ~70-second stretch (500–570s) where the pressure signal was fine but the computer simply wasn’t producing a ventilation/gas-time estimate at all (None, not 0) — then another ~20-second full pressure dropout right as the alarm was active. The alarm fired at the very moment the ventilation calculation had been dark for over a minute — likely the computer’s watchdog flagging “I can’t tell you your gas time” rather than a genuine low-air event. When data finally resumed at 594.13s, it briefly computed a startling 37 seconds of gas time — before jumping to a much healthier 1729s just 6 seconds later. That 37s figure is a transient artifact of restarting the estimate on stale/limited data, the same pattern as the first file’s dip, just far more dramatic because the gap was longer and happened at depth…

@dnctr I can also confirm it is the beta. I reinstalled what I thought was the July beta and it is now there. It is July Candidate 1, 3.13.0

@Kaiphi See https://support.komoot.com/hc/en-us/articles/10449347874074-Connect-Suunto-to-komoot

@prakalejas said: a day ago Somehow my watch always catches edge and brakes protective glass, so I made 3D printable protective case: I agree with another comment. The protective glass is far more fragile than the sapphire crystal used in the watch which is actually extremely scratch resistant. If you didn’t have the protective glass in the first place, I bet your watch would be fine. Personally I wouldn’t want to hide a beautiful Suunto watch behind this ugly looking case. But it is your choice.

@Peter-Pan-0 hey Before updating, you need to write the exact name of your firmware. When you got it, you can try the latest one and rollback if needed. Check forum https://forum.suunto.com/topic/6836/firmware-collection/110 The most stable for me was the 2.48.16, unfortunately, I never found the exact name so impossible to rollback . It was the best about bug and battery. Latest is quiet ok but definitely not a bug free. Especially, there is some famtom vibration sometimes

Unfortunately still an issue in 6.11.8

@bbx100 Thanks for sharing your insight, much appreciated. My race2 is only 10 months old, so I have another 14 to go before it is out of warranty. So far, everything is still working again as expected after doing about 10 ‘moves’ and daily use. Let’s see how it goes with the next firmware update and onwards. If this happens again, I’ll definitly report to Suunto support.