someone on the forum built this tool, but I haven’t tried it yet.https://github.com/GitjoPowershell/suunto-tbt-web

@Euan73 Never had that behavior after 6 months of intense use. In the first weeks I had a couple of restarts but those never appeared again after the latest 2 updates. I would try a hard reset to see if it solves the issue. Last months the watch has been super stable, both on trails and road running and I’ve been racing a lot averaging around 7-10h of weekly training.

@DonTomGot I am no JS expert myself. But some tips. The watch runs Duktape JS engine, which is only ES5.1 compliant. The simulator runs QuickJS I think. So code that will work OK in the simulator may silently fail on the watch. There is a pinned thread on the difference between simulator and watch, you can check there for advice on some of the typical stumbling blocks. For instance the missing semicolon on the return statement will work in the simulator but likely fail on the watch. I would also use “View system events” in the “Suunto watch view”. A lot of the failures are silent or not easy to decode, but you may find something. You can also insert your own systemEvent statement to “print” to the event log and get a traceback that way.

@Rasser Hello, I use the drill mode personnaly. I count the number of turns and when I put in pause, I add the distance. Like that I know each distance between each pause.

@9peekrf0 Raw data from watch are going to app, you can update in the app and see other metrics. But it can’t invent data, if the used mode was without GPS for example, then, no GPS. Etc… And update in app won’t be synced to watch.

Have you tried to connect the Eon Core to a computer ?

@Masnyband You need to have navigation turned on for LOOP to work… another option is to use my S+ aLOOP which doesn’t require that and is more accurate at detecting your position, preventing false positives.

@perfekt_tall who is “we”?

@peegee you need “Veneto”

@Mister-PYC a widget for Fasting is my ambition here.

@peegee If you loaded a route, the % displayed on guidance screen is the average slope on remaining distance of the climb. If you are using climb app, the % is the “current” slope (based on last seconds or X meters - don’t know the exact calculation method used - maybe already mentionned on the forum).

I have the same issue. I sent watch data to Suntoo. I want to ask, does factory reset remove my own intervals?

not a priority, but it would be nice

I’ve also added a new branch in the ESP32 repo: https://github.com/SellA/BoschEBikeESP32/tree/feature/multi-mode Besides the standard bridge mode, it now supports exposing standard BLE sensor profiles as well: Power + Cadence Speed + Cadence Power only These modes don’t provide the full Bosch telemetry, but they work without the companion SuuntoPlus app and integrate natively with Suunto’s internal metrics and training features. For example, power data is correctly used for Suunto power zones, training load calculations, and related analytics. I also updated the integrated WiFi access point UI, where all bridge settings can now be configured directly from the browser: [image: 1779313377850-241b5f60-a758-476f-9131-c1158af2009e-image.png] There is now also a simulation mode that allows testing the connection with Suunto watches and bike computers without needing to connect to the actual eBike. Useful for validating the setup or experimenting with different configurations without having the bike nearby.

@TyreseJ4 two comments: battery life is not an online hype, but one of the key specs of a sport watch. my S9B Ambassador is slow and the battery not in anyway living up to the one in Vertical 2 I would sell it, if it was not the Ambassador version and thus some kind of collectable…

Does the Ocean really have all the features of the Nautic S? One thing I wasn’t sure is if Ocean supports Trimix - which Nautic S seems to do. And maybe Nautic S is lighter, but this could also just be the strap Edit: I forgot - also the Nautic S has no Trimix

@yassine-besbes If I remember correctly, the sensor indeed needs to be deleted from the watch and paired again. This came with the change in sensor management. Now I see that you have already tried to re-pair it. Have you deleted it before this? And then have you enabled the sensor in the exercise settings under “Sensor Data”?

@olaf-gottschalk has gone silent , update us if the work around helped you?

Same here for 3 divers in my club. The Suunto App just gives an error. I tried re-pairing, reinstalling, clearing caches, data, etc.