@Markus-Hornof cheers mate! Thank you very much

The manual provides an example of using an Enum, so that cannot by itself be the problem. What kind of error are you getting. Do not know if it is relevant here. But I had to init settings in code like below. I initially thought the data file was sufficient to do this but it seems not. // Load app settings settings = localStorage.getObject("appSettings"); // Create default settings if none found if (settings == null) { settings = { targetPaceWarm: 2.326, targetPaceInterval: 2.857, targetPaceRecovery: 2.083, targetPaceCool: 2.083, durationWarm: 10, durationInterval: 12, durationRecovery: 5, durationCool: 20, repeatCount: 2 } }

@matram pm me with your GitHub name, I’ll add you to my S+ skill repo. I’ve already done the digging.

Black grid issue is back on my vertical v1. strange because the watch did not receive any update this year…

@cosme.costa said: Rearding the OFF ROUTE alerts when you are on track, check what I said. Is the route created with SA or imported? I think I’ve seen it both ways - both when it is created in SA and when it is imported. This has never happened before but started happening regularly after the last update. What the new implementation doesn’t take into the account that the map may not be accurate enough, so it may think you are off route because the trail on the map is slightly off from the real trail.

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

@pavel.samokha First of all, thank you very much I’m sure you know who to refer the issue to and I know it will be addressed

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