Fixed. “modificationTime”: was wrong in the manifest.json.

@stereodreieck86 Hi there! I try to answer you by points: 1- My implementation use only official LDI. Proprietary control need an android or IOS phone paired to the ebike to read the data. There is a security going on on the first pairing that need to be done and there is no reverse engineering available on that. Other uses data from the can bus but it need physical access to the bus. 2- No for both at the current state 3- LDI is the easiest one to go with. Older protocol is all reverse engineered but has additional data and hardware requirements 4- I have only one gen4 and one gen5 personally tested and they work nicely 5- I can’t test but probably the only field not available is the light sensor (working on my Kiox400C). Probably not available if there isn’t a display (i suppose, not confirmed). As a bonus i can say that i’ve tested all the non documented data field on the LDI protocol and no data is transmitted. All that is documented is all that we have.

@rémiP Thanks. This seems problematic. Is there any reason for this behavior @suuntopartnerteam?

@rémiP Thanks for this - but it seems the problem was somewhere else… “shift” does indeed work - but I now instead use it in an another way/method. It seems I was recreating an array without any need to do so - leading to memory issues. Hopefully now fixed.

The app is great. Would it be possible to add an infinite loop feature? For example, I set it to 15 seconds and the watch keeps looping every 15 seconds without having to manually restart it using a button.

Must correct myself a bit … MacOS 27 drops support for Intel, i.e. the OS cannot be run on Intel CPUs. It also removes the Rosetta component that provides Intel emulation on top of Apple Silicon during the installation of the new OS. BUT there is a one-year grace period, where you can manually install Rosetta. To my understanding it no longer automatically installs as it did before when needed. You have to do the installation yourself from the command line. But it does work! So now I have the Suunto Plus environment running on two machines, double the productivity And Suunto has one more year to upgrade the simulator!

I suddenly worked, after a few times uninstall/install the same app build. Seems like there is a problem with stale versions…

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

@matram We’re still eagerly awaiting the custom watch face functionality!

@Łukasz-Szmigiel No I do not think so, there is only a single output in the manifest and three inputs. It seemed more load related as staggering canvas refreshes removed the problem. Worth nothing, on at least one occasion the canvas went black first then as a consequence of the load resulting in handling of that exception (we think) we got the pool full.

@Steven-Hambleton These are the font sizes available. There is plenty of options for larger size … f-d-xxxl: data field font, 85px for medium, 155px for large display f-d-xxl: data field font, 65px for medium, 118px for large display f-d-xl: data field font, 57px for medium, 103px for large display f-d-l: data field font, 50px for medium, 91px for large display f-d-m: data field font, 42px for medium, 78px for large display f-d-s: data field font, 35px for medium, 65px for large display f-d-xs: data field font, 25px for medium, 46px for large display However there is not much room for fine tuning at the lower end. I tried rendering text on a canvas and displaying that. It works but takes a bit more effort to program.

Another data point. I am working on app where I have included 12 minutes of actual HR data in main.js in a Uint8 array. This works nicely on the simulator but it fails on the watch. The app can be loaded but not activated, “too many apps”. If I comment out the test data and reloads the app on the watch, the app can be activated without error. It cannot be a memory constraint issue. I have separately verified that I can create arrays with up to 4000 elements and heap memory may be around 28k on the Race S. Some issue with parsing the declaration?

@matram ok right. I was confused. Workouts != activities. I can try to implement a workout upload but I see that ideally you need api access to suunto. for that I suppose you should mail them unfortunately.