Apple Watch Ultra 2 (sleep+workouts) + Garmin Cirqa (24/7) both feeding Bevel — how do you avoid double data during overlap windows?
Setting up a hybrid tracking approach and want to sanity-check it before I buy the Cirqa.
Why bother with two devices at all: I want to stop wearing a smartwatch on my wrist all day and switch to a mechanical/analog watch instead — but I don't want to lose 24/7 health data in the process. So the Cirqa is there specifically to quietly cover the day, while the AWU2 only comes out for sleep and workouts.
The plan:
- AWU2 for sleep tracking and all structured workouts (strength 3x/week + half marathon training block)
- Garmin Cirqa 24/7 for everything else — daytime HR, steps, quick unlogged walks/activities where I don't bother putting the watch on
- Everything feeds into Bevel as the main hub
The obvious problem: during sleep and during workouts I'm wearing both devices at once. That means Bevel is getting two HR/sleep/activity sources for the exact same time window.
Questions for anyone running a similar dual-device setup:
- Does Bevel let you set a priority source per data type (sleep, HR, workouts), or does it just take whatever syncs first/last?
- Does it detect and merge duplicate workouts (same start time from two sources), or do you end up with two entries and inflated Cardio Load / calories?
- For Garmin Cirqa specifically — has anyone confirmed whether the Health Stats sync to Apple Health matches what's in Garmin Connect 1:1, or is there a gap (e.g. continuous background HR vs. just summary numbers)?
- Anyone just turn off auto-activity-detection on the Cirqa during sleep/workout windows to avoid the conflict entirely, instead of relying on Bevel to sort it out?
Context if it matters: using Bevel to track recovery/strain for a half marathon block (Nov target) plus strength training. Trying to keep the AWU2 for what it's best at (sleep accuracy, workout precision) and let the Cirqa fill the daytime gap without buying a full second smartwatch.
Would love to hear from anyone who's actually run this combo rather than guessing — Bevel's changelog mentions direct Oura integration but I can't find anything concrete on native Garmin support, so not sure if this is even a common setup yet.