Draft: Initialize Garmin feature branch incl. Mock Garmin watch for Sim

[mountrcg]

The PR aims to

1. make the Trio-Garmin watchface configurable from Trio on the phone.
2. implement proper sensitivityRate for Trio users
3. provide support for the popular AAPS watchface by Swissalpine

• also provide structures to setup other watchfaces and datafields

4. provide data queueing that supports the unique and seldomly used Garmin message queue
5. remedy the issues of watchfaces becoming un-responsive after another watchface has been used, requiering the user to re-install the Trio watchface

• this is due to Trio still providing messages after the watchface has been completely de-activated and some severe system disadvantages of the Garmin message queue

Above the hood only the Garmin configuration view has been expanded to support different watchfaces, data type selection and switching off the messaging queue for the watchface if it is not being used. Comprehensive Help sheets have been created to explain the mechanisms.

App config	Watchface hint	Data queueing hint

Also attached the workflow with Garmin device enabled and without to seperate Device connection setup from Garmin App settings.:

Simulator.Screen.Recording.-.Dev.16.Pro.-.2025-10-30.at.12.29.47.mov

Testing can only be done with real Garmin watches and appropriate prg-files sideloaded onto them.

The watchface & datafield has been re-worked to work with the config options from Trio, spacing for all models has been setup dynamically. The watchface can be found in a newly setup repository. Installables are in the release section. Happy to transfer that to nightscout if deemed appropriate.

Watchface	Datafield

As one could also use the popular Swissalpine xDrip+/Spike watchface, I will make the derivative for Trio available in the release section as prg's only, once Swissalpine agrees. It works quite well!

Of course one could always use the original Swissalpine watchface/datafield with nightscout, but it would be an online only solution needing LTE/Wifi, Nightscout site and Garmin Connect running on phone. Fine in most situations.
Here I strive for true offline capabilities, works even without Garmin Connect running.

[mountrcg]

mock Garmin watch commit shall be reverted when merging in dev, it is just for better testing

[avouspierre]

I have the opportunity to have an access to vivoactive5 from my daughter. Use this feature + create the watch face for this specific watch 🔥 ➡️

I had a issue for the update until I installed the data field (I started to install only the watch face) but not sure it

[mountrcg]

I had a issue for the update until I installed the data field (I started to install only the watch face) but not sure it

no the datafield / watchface are totally independant,is not needed. Just takes a minute or 2 sometimes, the g or sens arrows will disappear on the first update of watch. Up/Down also helps.

[marv-out]

Haven't reviewed everything (its a lot), but I already made some comments from looking at the most critical parts. I also have no Garmin device so its all only code-based

[marv-out]

there are probably more descriptive variables possible

[marv-out]

why was there even autotune in this branch? was it based on latest dev?

[mountrcg]

yes the files were still in dev, just the reference was removed

[marv-out]

see comment above about naming

[mountrcg]

GarminWatchSettings.swift

• GarminDataType1 (enum) → GarminPrimaryDataField
• GarminDataType2 (enum) → GarminSecondaryDataField
• garminDisableWatchfaceData → isWatchfaceDataEnabled
  • ⚠️ Boolean logic reversed: Default changed from true (disabled) to false (disabled)

New struct definition:

struct GarminWatchSettings: Codable, Hashable {
    var watchface: GarminWatchface = .trio
    var primaryDataField: GarminPrimaryDataField = .cob
    var secondaryDataField: GarminSecondaryDataField = .tbr
    var isWatchfaceDataEnabled: Bool = false
}

---

WatchConfigStateModel.swift

• garminDataType1 → primaryDataField
• garminDataType2 → secondaryDataField
• garminDisableWatchfaceData → isWatchfaceDataEnabled
  • ⚠️ Boolean logic reversed: Default changed from true to false
• isDisableToggleLocked → isWatchfaceDataCooldownActive
• remainingCooldownSeconds → watchfaceSwitchCooldownSeconds
• cooldownTimer → watchfaceSwitchTimer
• cooldownEndTime → watchfaceSwitchCooldownEndTime

[avouspierre]

GarminWatchSettings.swift

• GarminDataType1 (enum) → GarminPrimaryDataField
• GarminDataType2 (enum) → GarminSecondaryDataField
• garminDisableWatchfaceData → isWatchfaceDataEnabled

@mountrcg These changes of the name of the attributes must be apply in the garminWatchFace and garminFieldFace code to allow to use it.

statusData = {
                "sgv" => status["sgv"],
                "..."
                "displayDataType1" => status["displayPrimaryAttributeChoice"],
                "displayDataType2" => status["displaySecondaryAttributeChoice"],
                "date" => status["date"]
            };

[mountrcg]

@avouspierre I moved that around a lot. It is fixed now, but moved it to different repo, sending you invites.

[marv-out]

theres a lot happening now in the sink closure of the publisher. I would probably separate this into smaller parts for readability

[mountrcg]

could you elaborate on this please, may be small example

[marv-out]

see comment above reg. readability

[marv-out]

same problem with the formatter

[mountrcg]

done

[marv-out]

you are validating those values several times in the same way. Please use helper methods

[mountrcg]

tried, not sure it's better

[marv-out]

does this work?

[mountrcg]

yep, very nicely, it just creates a fake garmin device which allows the testing of UI elements in sim, which would not be possible without real phone and watch

[marv-out]

creating a timer on the main thread is probably a bad idea and will block the UI. I would suggest using a dedicated queue

[mountrcg]

done

[marv-out]

I think this could be optimized in terms of efficiency and readability. Calculate timestamp outside of the loop, use an early return to avoid unnecessary watchstate initialization...

maybe sth like this:

  let mostRecentTimestamp: UInt64? = {
                    if let latestDetermination = determinationObjects.first,
                       let loopTimestamp = latestDetermination.timestamp {
                        return UInt64(loopTimestamp.timeIntervalSince1970 * 1000)
                    }
                    return nil
                }()

                // Process each glucose reading (up to 24)
                for (index, glucose) in glucoseObjects.enumerated() {
                    // Validate glucose value first
                    let glucoseValue = glucose.glucose
                    guard glucoseValue >= 0, glucoseValue <= 500 else {
                        if self.debugWatchState {
                            debug(.watchManager, "⌚️ SwissAlpine: Invalid glucose value (\(glucoseValue)), excluding from data")
                        }
                        continue
                    }

                    var watchState = GarminSwissAlpineWatchState()

                    // Set timestamp: use determination timestamp for most recent, glucose timestamp for everything previously
                    if index == 0 {
                        watchState.date = mostRecentTimestamp ?? glucose.date.map { UInt64($0.timeIntervalSince1970 * 1000) }
                    } else {
                        watchState.date = glucose.date.map { UInt64($0.timeIntervalSince1970 * 1000) }
                    }

[mountrcg]

done

[mountrcg]

@Sjoerd-Bo3 & @dnzxy
I have added 2 watchface to connectIQ. Can we move the PR into the feature branch to commence testing?

I moved the code for watchfaces and also 2 datafields into private repos, too much interdependance with Trio, the message queueing and energy optimization within GarminManager are too tricky.