If they do flash the V2/R2 then the R2 could be a great purchase when the R3 is released.

@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.

@Nandodiver I have the tank POD, i believe the transmitter only works with the older computers like Vyper and the D Range of dive watches. I bought the POD in the beginning of this year and i’m not aware that there is a new version available.

@bruno.tanqueray Is the tide for my GPS position or for a reference port? Your phone sends your coordinates, but the forecast comes back for the nearest reference point in the tide dataset, and it’s that point’s coordinates and name that are pushed to the watch. If the reference point is within 50 km of you the widget may still label it with your own town, so the name you see isn’t proof the curve is for your beach. What triggers a refresh? Nothing on the phone: there’s no tide screen in the app and no background schedule. The watch asks for data when it needs it, and the phone answers only if it’s connected and nearby, so the practical trigger is “watch connected to phone”, not “open the widget”. Is there a cache or a daily limit? There’s a cache, but I don’t know about a limit: each fetch pulls about a week of data, and the app serves it until roughly two days of it are left, or until you move more than about 10 km. That’s probably why it fetches once and then appears to do nothing for a couple of days. What’s the correct sequence? Pair the watch, keep the app installed and allowed to use location all the time (not just “while using the app”), keep the watch connected, then open the tide widget on the watch. If you there’s no tide data after that, the two things worth ruling out first are background location permission and a location that has no usable tide data (eg something inland, like Lake Tahoe). NB: I don’t work for Suunto; these are my own observations. Someone who works for Suunto can tell me I’m wrong, or delete my post if it over-shares.

@raven agree with you! ZS is not great for the training you are doing.

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/

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

Race 1 and Race S was perfectly fine about price. For me only OHR was poor (at least Race 1 which I used). I mostly used chest strap awnyway, but sometimes didnt use or just left it home, and it was completly *****. Race 2 solved this problem when I compared watch OHR vs. Strap. Also at launch date Race UI was so laggy (at moment Race 2 release it was speed). Didnt bothered me so much, but for new user or someone born after 2000, it could be ancient technology if we talking about speed of using it and kinda bad first impression. Anyway I think Race and Race S was one of biggest step for Suunto, especially very popular Race S from what I’ve seen. Race 2 OHR was much better, also faster in using, and in maps., but price went up. Iam very interested what Race 3 will bring. By rumors Race 3 got no longer sapphire glass (must have for me) and AI coach subscription (which I completly dont care). If it will be main changes I’ll stick with Race 2 few more years, and who knows, maybe I’ll give a try Coros or Garmin.

@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.

@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.

Thought I’d add an update as I’ve just received a new sensor & belt from Suunto support who tested the old one & agreed that it was faulty. Also worth mentioning, whilst it was away at support I had to use the watch based optical sensor as I don’t have a back up & it performed surprisingly well

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

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

@Squirrel don’t know. This is iOS beta 3.13

Possible solution to the restart problem. I let the previous version of the system be installed and waited for it to finish. Then I let the watch update to the latest version of the system, again I waited for the whole process to finish, which takes a long time. No restart yet. Before that I interrupted the update process by holding the restart button because it seemed to me that the update was taking a long time.

I’ve had my V2 since mid October and so far not a single crash. I always run 3 S+ non-third party apps. No other issues either.

@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.