Hi,
Device: Descent Mk3i 51mm, firmware 27.19
Connect IQ SDK: 9.1.0 (build) / 9.2.0 (API check)
The stock Descent watch face shows No-Fly Time after a dive. After multiple non-decompression dives on 2026-11-04 it showed 18 hours, which matches the manual's table.
My Connect IQ watch face tries to read the same value, and it never appears:
- The SDK's Complications type table (0-42) contains no COMPLICATION_TYPE_NO_FLY_TIME, confirmed in api.mir.
- I enumerate Complications.getComplications() at runtime and match on the label, covering "no fly", "no-fly", "nofly", "fly", and the Chinese "禁飛" label, on both longLabel and shortLabel, with try/catch around the scan.
- I parse the value as Number/Float/Long/Double (minutes, seconds if > 1440) and as String ("H:MM", "18h", bare number).
- Other complications on the same face work: heart rate, body battery, stress, calories. Only no-fly never resolves to an id, and no arc is ever drawn.
Questions:
1. Is No-Fly Time published as a Connect IQ complication at all on the Descent Mk3i? If yes, what are its longLabel, shortLabel, value type and unit, and its complication type/id?
2. If it is not published, is there any other Connect IQ API that can read no-fly time or the surface-interval dive state?
3. The Descent manual says "you can add the no-fly indicator to a custom watch face". Does that refer only to Garmin's built-in customizable watch face, and not to a Connect IQ watch face?
If the answer to (1) and (2) is no, please treat this as a feature request: add a COMPLICATION_TYPE_NO_FLY_TIME (remaining minutes, like COMPLICATION_TYPE_RECOVERY_TIME) for dive devices.
Thank you,
Joseph Chang
Descent Mk3i 51mm, custom watch face "Mk3i51 Tactical Diver"