Multiple Fitbit Sync has a nasty bug/feature?

[SunsetRunner]

I've owned a Charge HR for a year. Recently I bought a Zip to use at formal events or when mowing the yard (since Charge HR is pretty inaccurate when your arms are still) and the multiple Fitbit Sync has been perfect, I literally take one off and put the other on and everything is taken care of for me. SOOO... I decided to go all in and replace my Garmin GPS running watch with a Fitbit Surge so everything would be on a single platform... and I have a problem.

The sync of the three Fitbits continues to work great UNLESS for any reason the Fitbit Surge aquires data when I am actively using a different Fitbit. Why would BOTH Fitbits get data? Well I'm an Airline Pilot and I wear the Charge HR while flying but have the Surge in my luggage (kept in the cockpit). I have tried turning off the Surge but on occasion the super easy to press buttons turn it back on in the luggage and it begins recording a few hundred steps on a bumpy flight. This wouldn't be a problem but the instant BOTH the Charge HR and Fitbit Surge sync the Fitbit system replaces the step data on the Charge HR, often THOUSANDS AND THOUSANDS OF STEPS AHEAD, with the lesser amount from the Surge. It seems Fitbit doesn't even attempt to do a common sense check that if both devices recorded info for a given time they should take the info from the unit with MORE steps. Also the Charge HR is the only one recording a HR! It seems instead Fitbit simply priortizes the Surge over all other Fitbit devices if two devices record information for a given time even if the Surge has recorded vastly less steps and no HR which is plain dumb. The sad part is the HR from the Charge HR IS kept and the graph of when I walked shows the steps, it just simply takes away the steps from my total. I get to literally watch the Charge HR go from 8000 steps to 2000 for example in real time on the Charge HR.

I hope Fitbit either puts in more sophesticated checks or simply puts a better delay on the button to start up the Surge or something. As it stands I'm kinda stuck on my idea of going all in on the Fitbit platform unless I can find a hard cover case for the Surge to somehow prevent the button from turning the watch on when in my luggage.

First world problems I know but its fixable...

[Blade7658]

I love your "first world problems" comment!

Not a fix to the issue, but you can delete the steps by logging "driving" and listing the time involved in your flying.

[SunsetRunner]

I could care less about the steps when flying because its a couple hundred and that doesn't skew much, the problem is the surge couple hundred steps CANCELS the thousands of real steps in airport terminals counted by the Charge HR! I literally several times watched as my Charge HR recorded thousands of steps and then the display literally would reset to match the Surge which is "alive" in my bag and bring the total down. Just seems crazy the logic with two Fitbits both recording data would be to keep the data recorded by the one with no valid HR and 2% of the step total of the other. Weird.

[Blade7658]

Yea, I get it, I was just thinking if you told it to ignore that data, maybe it would fix the issue.  Only other idea I have is to sink the Charge before flying and turn off the Surge while flying.

Good luck!