Apple Watch + Fitbit Air, worn sequentially (never together) - does this actually avoid duplicate data in Bevel?

Got my Fitbit Air a few days ago and I'm holding off connecting it to anything until it finishes calibrating (heard it's about a week). In the meantime I want to sanity check my plan before I flip any switches, since I've read enough duplicate-workout horror stories in this sub to be paranoid now.

Quick background: training for a 70.3 and want proper 24/7 tracking, but I also like wearing a normal watch most of the day, so I don't want to be stuck on my Apple Watch all the time. Landed on this setup:

Apple Watch SE only goes on for actual training sessions (swim/bike/run). Rest of the time it's Fitbit Air paired with my regular watch, fitbit doing the background tracking (sleep, resting HR, steps) while the regular watch is just what I'm actually looking at for time. Important bit: I take the Apple Watch off completely before putting the Fitbit on, so there's never a moment where both are actually on my wrist at the same time. Everything funnels into Bevel as my one dashboard.

Here's what I'm planning to actually turn on/off:

Google Health → Apple Health sync:

  • ON — Steps, Sleep, Heart rate, Resting heart rate, HRV, Vitals (SpO2, respiratory rate)
  • OFF — Exercise/Workouts, Active/Resting Energy

Bevel data source priority:

  • Workouts + Energy → Apple Watch as primary
  • Steps, Sleep, Resting HR → Fitbit Air as primary
  • Heart rate + HRV → leaving both on

Figured even without overlapping wear time, the Fitbit's auto-detect could still catch the tail end of a workout when I put it back on (heart rate's still up), or flag random stuff like a fast walk as a "workout," which I don't want bleeding into my training log. Same logic for energy — pretty sure both devices independently guess my daily calorie burn regardless of who's actually on my wrist, so letting both write that number in just gives me two different answers fighting each other.

Curious if anyone's actually running this exact pattern — Apple Watch and Fitbit Air, strictly sequential, feeding Bevel. Does turning off the Workouts toggle on the Apple Health side actually stop it, or does Bevel's Google Health integration grab workouts on its own regardless of that setting? And for anyone who waited out the calibration period before connecting sync — was it actually worth the wait or am I overthinking it?

Would rather sort this out now than clean up a mess of duplicate entries a month in.

reddit.com
u/mreeg — 3 days ago

Apple Watch + Fitbit Air, worn sequentially (never together) - does this actually avoid duplicate data in Bevel?

Got my Fitbit Air a few days ago and I'm holding off connecting it to anything until it finishes calibrating (heard it's about a week). In the meantime I want to sanity check my plan before I flip any switches, since I've read enough duplicate-workout horror stories in this sub to be paranoid now.

Quick background: training for a 70.3 and want proper 24/7 tracking, but I also like wearing a normal watch most of the day, so I don't want to be stuck on my Apple Watch all the time. Landed on this setup:

Apple Watch SE only goes on for actual training sessions (swim/bike/run). Rest of the time it's Fitbit Air paired with my regular watch, fitbit doing the background tracking (sleep, resting HR, steps) while the regular watch is just what I'm actually looking at for time. Important bit: I take the Apple Watch off completely before putting the Fitbit on, so there's never a moment where both are actually on my wrist at the same time. Everything funnels into Bevel as my one dashboard.

Here's what I'm planning to actually turn on/off:

Google Health → Apple Health sync:

  • ON — Steps, Sleep, Heart rate, Resting heart rate, HRV, Vitals (SpO2, respiratory rate)
  • OFF — Exercise/Workouts, Active/Resting Energy

Bevel data source priority:

  • Workouts + Energy → Apple Watch as primary
  • Steps, Sleep, Resting HR → Fitbit Air as primary
  • Heart rate + HRV → leaving both on

Figured even without overlapping wear time, the Fitbit's auto-detect could still catch the tail end of a workout when I put it back on (heart rate's still up), or flag random stuff like a fast walk as a "workout," which I don't want bleeding into my training log. Same logic for energy — pretty sure both devices independently guess my daily calorie burn regardless of who's actually on my wrist, so letting both write that number in just gives me two different answers fighting each other.

Curious if anyone's actually running this exact pattern — Apple Watch and Fitbit Air, strictly sequential, feeding Bevel. Does turning off the Workouts toggle on the Apple Health side actually stop it, or does Bevel's Google Health integration grab workouts on its own regardless of that setting? And for anyone who waited out the calibration period before connecting sync — was it actually worth the wait or am I overthinking it?

Would rather sort this out now than clean up a mess of duplicate entries a month in.

reddit.com
u/mreeg — 3 days ago