The app has become rather big, but everything works solidly. Keep in mind that all of this is read-only, so you can’t adjust things from your watch to a communicating app. Currently only tested for my Race S (q display), it’ll probably work for the Vertical 1, and the 9PP, but I obviously haven’t tested that.
I was able to fit in two different layouts in in the app, switchable by holding the upper right button for about 2-3 seconds. Tried below with Trio in CGM simulator & pump simulator, and went bouldering for 2 hours and on a 40 min run while connected to my own Nightscout, all without issue. BG units are data stream aware, meaning it’ll show as either mmol/L or mg/dL. IOB, COB, Loop, BG, trend arrow, trend value are read from Nightscout/Trio data stream. Data age (lowest value) is data age from CGM, but an internal counter on the watch keeps track and greys out values older than 6 minutes, and gives an audible alert and buzz if older than 10 minutes.
The left is a “Sports” layout, the right is a “Daily” layout.
[image: 1792926347322-slide1.jpeg]
In the Sports layout, pace (upper left) is unit aware so automatically adjusts per sports profile chosen (tested with running, cycling, rowing). I’ve chosen HR and pace here as these are generally the major two I keep an eye on. All other info you can simply see by switching to you screen of choice.
The graph on Daily is the past 3 hours, data points are streamed as soon as watch connects to phone, with one point per 5 minutes (takes roughly 2 minutes for everything to load in). Dots in range (user adjustable, but a little quirky still) are white, otherwise red below range, orange above range. Values below 3.0 mmol/L are red triangles, value above 13.9 are orange triangles (upper range is adjustable but compresses the graph). Green band is Low to High, also adjustable. Switching to and back from the Daily screen may cause the graph to empty visually, but should be filled back in over a minute or so.
Alerts (vibration, plus a tone if your watch tones are on): going below or above your alert levels, a repeat alert if you stay low, falling or rising fast, and signal lost. In quiet sports (yoga, walking, meditation, etc.) I’ve set different levels because I tested this in a yoga class and the thing went off every 15 minutes because I was consistently just a little too high. The reason I’ve opted for two layouts, and two different alert “types”, is because without a true watch face implementation a “walking” exercise with the Daily layout is the best workaround I could think of for people to keep track of everything without having to check your phone.
Regarding settings and connection:
BLE bridge key: a 32-character key shown in a phone app. Secure connection and super lightweight. I’ve currently set this to be user generated in my bridge / Trio fork, and I entered this into the Suunto app with the VSCode extension.
Low below / High above: your target range: colours, graph band and time-in-range.
Stale (grey) after: minutes before an old reading turns grey
Alerts: alerts on or off
Alert below / Alert above: when the watch alerts (can differ from your range, e.g. alert at 5.0 during exercise)
Repeat low alert: repeat while you stay low, every x minutes (0 = off)
Quiet sports: alert below / above / falling fast below: the separate levels for quiet sports
Save glucose to workout: adds a glucose graph and avg/min/max/time-in-range to your workout in the Suunto app
Currently working out if I can send a warning if anything in a closed loop failed, but the app is extremely heavy for Suunto standards so I’ll likely only be able to send an “AID alert” warning.
