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

@Steven-Hambleton I would guess that the typical HW development time is 2 years. Then you would have different teams working on different products. I think this is what we see with Garmin and Suunto. If Apple releases new HW every year, they are likely still taking 2+ years for each watch, just running multiple model years in parallel. Suunto seems to follow the normal Agile development approach for software with 2-week sprints and quarterly releases. In my personal view that approach will emphasise regular releases of customer-visible features and give low priority to quality improvements and architectural changes. It does not have to be like that, but it is a common pattern.

See also the facebook Suunto Nautic group. More people are impacted.

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

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

@MikeC30 this is well possible.

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/

@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

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

@Manta for the Suunto plus app you have to compile and transfer this: https://github.com/SellA/BoschEBikeSuunto In my opinion however this is not convenient since you have to do it from the pc and, everytime you sync with the Suunto App on the phone, it will be erased. That’s a “stupid” limitation on the Suunto plus app that are not official distributed trough the mainline channel. I find myself perfectly happy with the ESP32 firmware flashed and set to POWER+CADENCE mode where i get the Cadence in RPM and Power in WATT. This is done trough standard communication like all other sensors and can be used without a custom plus app in the watch. And moreover, the power and cadence data will be used for Suunto internal algorithm, they are also correctly mapped to Strava if you have it. I’ve connected my board directly to the motor for getting power (using a DC-DC converter to step down the voltage from 12V to 3,3V) and it turns on directly with the ebike. Low power port (LPP) is used in my bike for the magnet sensor of the back wheel so i’ve connected it to the High power port (HPP). If you need further info just drop me a mail theray2189@gmail.com . I’ll try to help you to set things up if needed.

@SamppaP none as well. But i care more more about the guides tbh.

@sky-runner It’s worth adding that this error occurs when using paths, trails, etc. Off‑trail, it’s a complete disaster – because the Suunto App doesn’t handle elevation at all in those cases.