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

@aiv4r is [image: 0UA9ixY] not a sign? Has been there since I dunno when. There are, from my understanding, already SuuntoPlus apps running natively on the Run, don’t ask me which as I’m not sure.

I want to raise one thing while the fix is still being scoped, though. The mail talks about the unexpected Mandatory Gas Time alarm specifically, and I think the alarm is only the noisy half of this. I went back and ran the same check over all seven dives I have on the Nautic. Three of them show the estimator dropping out during the descent and coming back with a nonsense number: 69 l/min on 7 May, 40.6 on 21 May, 100 on 28 June. Only the last one produced an alarm, and the only reason is that the resulting gas time happened to land below the threshold that time. The other two failed in exactly the same way and I never noticed. Also after digging in the logs a bit more I found out the alarm is a proper event in the log: 127.6s {"DiveEvents": {"Alarm": {"Active": true, "Type": "Gas Time"}}} 137.7s {"DiveEvents": {"Alarm": {"Active": false, "Type": "Gas Time"}}} At 127.6 s both Ventilation and GasTime are null, not zero. The 100 l/min turns up 2.3 seconds afterwards. So the alarm doesn’t fire because the estimate went bad, it fires because there is no estimate at all, and the bad number is what comes back after. On my 16 July dive the estimator barely produced anything at all: of 371 samples, 355 had a valid tank pressure but only 17 had a Ventilation value, all reading 0.0 with GasTime: 0. In practice that meant no gas consumption or gas time on my display for that dive, with the POD transmitting normally throughout. No alarm on that one, incidentally, even with GasTime at zero at nearly 12 m. So there is definitely something wrong happening in the Nautic. Let’s hope they will release an update soon.

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

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

@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

I don’t see this too much on trails but 100% on roads. I think they over corrected a bit with this last update. I constantly get “off route” notifications simply being on the other side of the street running in the correct direction.

Today my Race 2 restarted during a walk, the first time this has happened in four months of daily use. When it restarted, my phone notifications, which I always keep disabled, were activated on the watch. Could this be a problem with the latest version? I’ll let you know if it happens again. I do have several Suunto Plus apps installed, but they were all disabled during the activity.

@Nelson-Diogo That’s why I didn’t keep my Suunto Run

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

@BrunoH Thanks for your feedback. so the bug is on my watch. Biking is not in the list a think? have a nice day vinc

@KSGravelJunkie Wahoo can’t choose between ANT+ and BT, whereas Karoo can, so it doesn’t have a problem with this … but I’m not sure if there isn’t also an identification error on Suunto’s part

@elbee Thanks!

@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 one more question Regarding cadence sensor. Should I remove it or just set in right way? I can see that I can set wheel size and turn on or off something like sinc speed and cadence (but it cannot sync speed because it’s only on cadence mode) I removed sensor and at least distance is correct

@wakarimasen their tss is though synced back to your watch. Suunto app calculates that fyi.

@brechtvb Not, it’s not just you. I bit the bullet and bought a combi sensor about 18 months ago. For 25-30 EUR, this was a small price to pay to remedy my frustration In the real world it makes little difference: a full watch battery gets me 232 hours of riding with the pod, or 103 hours of riding with GPS in “OK” mode.

I checked runs from Spring in this year. In April, with apparently the same setup, the R-R data recorded by the 9 Peak Pro looked normal. The recent recording contains repeated missing or corrupted R-R intervals and implausible HRV values. So it doesn’t look like a Firmware thing cause the major BT updates happend in Sept 25 and in January 26 April [image: 1785265928172-8e88a92f-036e-4a19-baf4-bdf31fd1923b-image.jpeg] Juli [image: 1785265951381-8f441eff-fefb-434d-ade5-fafcc40a355e-image.jpeg]