Friday, January 15, 2016

Fitbit: More than one tracker found

A few days ago when going to sync the Fitbit HR, the message "more than one tracker found" appeared. Since then the message now appears every time.



A check on the internet reveals this problem started to occur for hundreds of others mostly since yesterday. For me, if I recall correctly, it started a couple of days ago. I thought it may have been related to seeing the message when a couple of others in the house had their Fitbit on, and the software when synchronising, located multiple Fitbits which was at the time correct. However since then there's been no other Fitbit devices in the area.

The workaround at this time unfortunately is to log on each time. I'm using a MacBook Air and the Fitbit Connect software. I've noticed others with the issue using Windows.

A moderator on the Fitbit community forum has indicated Fitbit are aware of the issue and the team are working on a fix.

All we can do really is wait until a fix is provided by Fitbit. Hopefully it will happen soon because logging in to sync each time is resulting in a poor user experience.

Kelvin Eldridge
www.OnlineConnections.com.au
Call 0415 910 703 for IT support.
Servicing Doncaster, Templestowe, Eltham and the surrounding area.


Update: 21 Jan 2016
Found the following on the Fitbit forum.

Fitbit Update 1/19: Hey all- we've just checked in with the software engineering team, and it looks like we're just about putting the finishing touches on the fix for this. 

We're expecting a resolution in a few days, at which time you should all be able to return to normal sync behavior. Thank you all for your continued patience. Please keep an eye out for updates from me later on in the week. 

To save others time I tested removing, restarting and reinstalling. This made no difference. For the MacBook Air the set up file I downloaded a couple of weeks ago where there was no problem, is still the same version number, so the file has no yet been updated.

Update: 29 January 2016
This particular problem now appears to have been fixed. I still continue to get issues connecting which is quite frustrating, but this problem is no longer occurring.

No comments:

Post a Comment