Can someone explain "not compatible"?

[vice86]

I have a Charge 2 and a Moto Z Play that's NOT on the compatible phone list...yet it seems to show all the info on the phone/website and even alert me to texts/calls/calendar on the Charge 2.

So what exactly wouldn't be compatible? Am I missing out on features having a phone not compatible vs a compatible phone? What features am I missing out on? How many more times could I say compatible? 

[Rich_Laue]

What's missing @vice86 is that this model phone hasn't been tested yet.

For a phone to get on the compatable list means Fitbit has tested, and if needed made changes to the app. 

[vice86]

so does that mean that possibly everything may be working correctly, all features working, just that Fitbit hasn't officially made it compatible yet? I can't tell if something's not syncing/working/showing...seems to all be there.

[Rich_Laue]

As i posted above, Fitbit might not have to do anything to make a phone compatible,  many phones share the same hardware and simply will work even though Fitbit hasn't done their official testing.

[shipo]

---

@vice86 wrote:

so does that mean that possibly everything may be working correctly, all features working, just that Fitbit hasn't officially made it compatible yet? I can't tell if something's not syncing/working/showing...seems to all be there.

---

As @Rich_Laue says, the Moto Z Play may indeed be 100% compatible for some or all of Fitbit's devices, but until the official testing and sign-off happens, it will not be listed in the Compatible Device chart.

FWIW, I upgraded my old Moto X (Gen 1) to a Moto Z Play this last May and have had zero issues with my Surge; I'll be switching over to the new Fitbit Ionic next week so hopefully I won't have any compatibility issues.  I'll update this thread regardless.  🙂