@dreamer_ said: Btw, It seems I can count 3 mayor betas in 2026 (splitted in 15 minor announced versions only this year). It is not the same release calendar/features as for the supported watches, but the bug fixes are there (even for Garmin). It is also more than nothing. Yeah, on paper it sounds good, but essentially each version had some serious issues for some people. Always the question of “Should I really upgrade beyond version …?” in the forums. I understand Suunto is focused in the new watches but it’s also a lot of time a watch like the Vertical is forgotten with the remaining bugs. And, when bugs, this can be a very bad image of the brand for the users that have the watch. Reminds me on Nokia and its N9, where they pushed a final update eliminating most of the bugs (over 1000 IIRC) before pulling the (support) plug. I also feel that is the right thing to do.

@Kowalski I don’t know. I’m not a Reddit admin, so I don’t know the tools they have at their disposal to detect stuff like this. It may have been that there was malware hidden in the file hosted in the Google Drive file, and the Core 2 leak was the bait to get you to open it? Just speculating.

Since Suunto still shows no meaningful response and reports of Nautic issues keep piling up, I have now reported the Nautic through the European product safety system as a potentially dangerous product. Given the false mandatory gas-time alarms and other incorrect dive data, I think an independent safety review is overdue. I’ll keep you updated. [image: 1786372833520-screenshot-2026-08-10-164007.png]

@Sascha-Domres makes sense, I get your point but it is more like I would buy Coros Apex 4 or similar and go to their community and start complaining that they do not support “tags” on activities and I am so dissapointed in all they do

@mickywickyftw I don’t see how ZS adds anything that you don’t get with HR anyway. For me it is just too inaccurate. I wanted to know how ZS actually performs and analyzed 150 runs and rides that I all did as Suunto recommends for ZS. While the mean reported thresholds over all workouts come very close to my actual thresholds, the standard deviation is at 9 bpms for the aerobic and at 7 bpm for the anaerobic threshold. So therefore on normal runs or rides, I get fluctuations of up to ±9 and ±6 bpm respectively and I never know when it is accurate or not. I had workouts where ZS told me that I am pushing way too hard but my HR was as usual and I was able to do the workout/race exactly as planned. I also had it the other way around. If I would have listened to ZS, I would have had a lot of destroyed workouts or races. From years of racing and training, I know that my HR never differs more than ±2 bpm at the anaerobic threshold and ±4 at the aerobic threshold if I am not completely destroyed or sick. So therefore HR and pace in combination with RPE is way more reliable. At least for me.

@MikeC30 @markg pretty sure this is a bug in the app.

@André-Faria It is hard to claim warranty for this. The watch restarts randomly. My seller says: the fault did not appear.

Wow, Dark Mode looks great! Now I can check my Runs in the Night without getting blind

ah here https://www.suunto.com/en-gr/sports/News-Articles-container-page/suunto-core-2-vs-core-1-whats-new-and-why-it-matters/

@Goatee Suunto reached out to me via email asking for more information (watch serial number, app version, etc.). I sent them the deets, so I’ll see where things go from there. Hopefully we can isolate the bug and get it fixed.

@isazi Yeah, let’s hope they implement it as soon as possible.

@elbee you are funny. Often the car manufacturer will not even give an indication of the needed update We have a couple where we are negotiating for a buy back as they can’t solve a software issue. Life isn’t that hard with Suunto. I do have a wahoo and also have the issue. But I didn’t buy the V2 expecting to be able to broadcast to the bike computer so when I can it will be a bonus.

@maszop can you give me some details about your disconnects with Vertical 2 and the new firmware? I will forward them to Suunto.

I need the link to the activities and the planned routes to report this, send them to me in private.

@Martin-Tuharský Hi Same issue here. 4 Days old Race 2 watch updated to the latest firmware on day one rebooted twice. Luckily only in time mode and not during my 100km race a day ago therefore there must be some kind of issue with this

Looks great in my Suunto 9 peak pro [image: 1786262740019-1000295463.jpg]

@Egika yep, I stiil have it in one of my drawers loved it so much!

@VoiGAS for the EON, thats correct as they hold both tables. You can switch over or set Buhlmann as default where locks do not occur. But this does not downplay the fact that the ceiling was not followed and decompression was not finalized. This will have impact on further calculations as Buhllman uses its nitrogen buildup for further calculations. So better not to have these sitiations and allways follow the indicators on the computer to the letter. Suunto does make the difference between voluntary or mandatory decompression stops. The RGBM lock only applies to the latter. The screen showed in the link indicates a mandatory situation which is explained by Suunto… you get a warning to go to the ceiling of 6,5 meter. You need to do that within 3 minutes and sit out the deco as long as indicated by the EON, in this case 75 minutes which is far from beeing recreational… If you fail - after warnings like the red ceiling indication and audible signal - to comply within 3 minutes, the computer locks for 48 hours. So you might say it indeed locks during the end of the dive.

@HonzaS same behavior I saw for my reboots. Immediately following or during a watch notified phone call