**AutoPresets** Automatically activate a Loop override presets during walking/running activity

[taylorpatterson-T1D]

Summary

How many times are you out and about and you forget to set your Loop Preset and then you go low? Happens to me on vacations a lot because I do a ton more walking than normal life. The more automation of Loop we can bring to our lives the better. So here I have just automated our Presets so forgetting doesn't put you in a medicaly risky situation. Part of the Loop AI PowerPack.

The Problem That We're Solving

People with Type 1 diabetes who use Loop often need to manually activate an override preset before physical activity like walking or running. This is easy to forget, especially for spontaneous activity — a walk with the dog, touring a new city on travel, or an unplanned errand on foot. Forgetting to activate an exercise preset can lead to lows, since Loop's algorithm doesn't know the user is moving and continues dosing at normal rates.

There is currently no way in Loop to automatically respond to real-world physical activity by adjusting insulin delivery. Users must either remember to manually activate a preset before every walk or run, or accept the risk of going low. This is a big quality-of-life gap, especially for active users who move throughout the day.

New Feature's Impact

AutoPresets adds automatic, hands-free override preset activation based on real-time walking and running detection using Apple's CoreMotion framework. When the user starts walking or running, Loop detects the activity and activates the preset they've chosen for that activity type. When they stop, Loop automatically deactivates it.

What it does

• Detects walking and running activity using CMPedometer (step counting) and CMMotionActivityManager (activity classification)
• Applies a user-selected override preset automatically when sustained activity is confirmed
• Removes the override automatically after activity stops, with a configurable delay
• Respects manually-activated overrides — won't override a preset the user set themselves
• Supports separate preset assignments for walking vs. running (e.g., a mild reduction for walks, a stronger reduction for runs)
• Geofence triggers — auto-activate presets when arriving at or leaving saved locations (gym, park, office)
• Calendar triggers — scan your calendars for keyword-matched events and activate presets before scheduled activities

User-configurable settings

• Enable/disable the feature entirely
• Activity types — toggle walking and/or running detection independently
• Preset selection — choose which existing override preset to apply for each activity type
• Continuous Activity Time — how long sustained activity must continue before the preset activates (10 sec to 10 min, acts as a confirmation to avoid false triggers from brief movement)
• Stop Delay — how long to wait after motion stops before deactivating the preset (10 sec to 2 hours)
• Require High Confidence — optionally require CoreMotion's high-confidence classification for stricter detection
• Location Triggers — create named locations with configurable radius (50–500m), trigger on arrival/departure/both, auto-deactivate on exit
• Calendar Triggers — add keywords (e.g. "Gym", "Spin Class"), choose a preset, set lead time (0–60 min before event), filter which calendars to watch, auto-deactivate when event ends
• Activity log — view recent activation/deactivation events with timestamps and durations
• Debug logging — optional detailed logging for troubleshooting

How detection works

1. CMPedometer counts steps in real-time
2. After 20+ steps, a "Continuous Activity Time" timer starts
3. CMMotionActivityManager classifies the activity as walking or running
4. When the timer fires, it verifies steps are still accumulating (> 5 additional steps)
5. If confirmed, the mapped preset is activated via Loop's existing override system
6. A stop timer monitors for inactivity — if no significant steps occur during the stop interval, the preset is deactivated
7. If the user resumes walking/running during the stop interval, the deactivation is cancelled

How geofence triggers work

1. User creates named locations (Gym, Office, Park) with "Use My Current Location" or map picker
2. Each location gets a preset, trigger type (arrival/departure/both), and configurable radius (50–500m)
3. Uses iOS CLCircularRegion monitoring — battery-efficient, no continuous GPS
4. On region entry/exit, the assigned preset is activated/deactivated
5. Won't override a manually-set preset

How calendar triggers work

1. User adds keywords that match calendar event titles (case-insensitive)
2. Each keyword maps to a preset to activate
3. AutoPresets scans all calendars (iCloud, Google, Outlook, Exchange) every 15 minutes for events in the next 24 hours
4. When a match is found, the preset activates at the configured lead time before the event starts
5. Optionally deactivates when the event ends
6. User can filter which calendars to watch

Safety considerations

• Uses Loop's existing TemporaryScheduleOverride system — no new insulin delivery pathways
• Will not override a manually-activated preset
• Automatically deactivates when activity stops / you leave a geofence / calendar event ends
• All activation/deactivation events are logged
• Feature is off by default and requires explicit user configuration
• Errors in motion detection do not disable the feature or affect Loop's core operation

Architecture

• 12 new files, all within Loop/Loop/ following Loop's layer-based architecture (Views, Managers, Models)
• 2 existing files modified with minimal changes:
  • /Loop/Loop/Views/SettingsView.swift — NavigationLink to the new settings screen
  • /Loop/Loop/Managers/LoopDataManager.swift — ~40-line delegate extension for preset activation/deactivation
• Self-contained feature with a single delegate protocol for all communication with Loop
• No changes to LoopKit, LoopAlgorithm, or any other submodules
• Developed from v3.10.0 DEV branch

New files

File	Location	Purpose
AutoPresets_SettingsView.swift	Views/AutoPresets/	SwiftUI settings UI
AutoPresets_GeofenceSettingsView.swift	Views/AutoPresets/	Geofence location management UI
AutoPresets_CalendarSettingsView.swift	Views/AutoPresets/	Calendar trigger keyword management UI
AutoPresets_AIRecommendationView.swift	Views/AutoPresets/	AI-powered preset recommendations
AutoPresets_Coordinator.swift	Managers/AutoPresets/	Main coordinator — activity detection and preset activation logic
AutoPresets_Delegate.swift	Managers/AutoPresets/	Protocol for communicating with LoopDataManager
AutoPresets_Storage.swift	Managers/AutoPresets/	UserDefaults persistence
AutoPresets_Logger.swift	Managers/AutoPresets/	Debug logging infrastructure
AutoPresets_ActivityDetectionManager.swift	Managers/AutoPresets/	CoreMotion wrapper (CMPedometer, CMMotionActivityManager)
AutoPresets_GeofenceManager.swift	Managers/AutoPresets/	CLLocationManager region monitoring
AutoPresets_CalendarManager.swift	Managers/AutoPresets/	EventKit calendar scanning and timer scheduling
AutoPresets_Models.swift	Resources/AutoPresets/	Data models (ActivityType, Settings, LogEntry, etc.)

---

Screenshots

1. Settings menu showing the Auto-Apply Presets entry

2. AutoPresets main settings screen (feature enabled, activity types visible)
3. Preset selection for an activity type
4. Detection settings (sliders for timing)

5. Activity log showing activation/deactivation events

---

Video Demo

https://youtube.com/shorts/H45iZCnL2XQ

---

Recent Updates (since initial PR)

• Geofence location triggers — Auto-activate presets when arriving at or leaving saved locations (gym, park, office). Uses iOS CLCircularRegion monitoring — battery-efficient, no GPS polling. Configurable radius (50–500m), trigger on arrival/departure/both, auto-deactivate on exit.
• Calendar event triggers — Scan all calendars (iCloud, Google, Outlook, Exchange) for keyword-matched events. Activate presets at configurable lead time (0–60 min before event). Per-calendar filtering and auto-deactivation when event ends.
• AI Preset Advisor — LoopInsights-powered recommendations that analyze glucose patterns and suggest optimal preset configurations.
• False activation fix — Stale pedometer callback guard + fixed recency window to prevent phantom activations after app resume.
• Stop Delay extended to 2 hours — Supports longer post-activity recovery periods.