I've noticed a small, plastic flake inside the far, right sensor on the back of my versa. The sensor itself doesn't appear to be damaged and the flake doesn't move. However it's clearly blocking part of the sensor's surface area when wearing the watch.
I've attached two pictures for reference and have a two questions:
As a developer, accuracy is doubly important. I have a few app ideas I'm looking forward to developing, but want to make sure the readings I'm getting are accurate first!
Best AnswerExchange/return will depend on where you bought the device. In Australia, it would be a case of just taking it back and swapping it due to our consumer laws.
How long have you had the Versa for? As that might also impact whether it's a simple exchange or not. ![]()
Best AnswerThanks GenieFish, I've had it about a week, which is well within the exchange period here.
To elaborate, I've found the return/warranty page, but the customer service site it directs you to doesn't seem to be configured correctly.
https://www.fitbit.com/ie/legal/returns-and-warranty
The second link returns a site host page that says "Error: Login is required to access this URL." Contact info points you to a gmail address rather than ...@fitbit.com.
Best Answer@SunsetRunner
Helen | Western Australia
Want to discuss ways to increase your activity? Visit Get Moving in the Lifestyle Discussion Forum.
Best AnswerFitbit does not make it easy.
Best AnswerAfter further troubleshooting, it appears that parts of the help.fitbit.com site may be blocked on the network I'm accessing from. In contrast, I can get there on my phone.
I'll submit a question to customer service and report back if a plastic flake can cause an issue with sensor readings.
Best AnswerI found info on three of the four on the back, which are as follows (pg 71 of user guide😞
There's also an ambient light sensor which I believe is on the front, to the right of the screen. I'm not sure what the fourth sensor on the back is, nor have I discovered which back sensor is which.
Best AnswerQuick update on this issue: While support has confirmed this is indeed a manufacturing fault, it's been almost a month and largely no action by Fitbit. I've detailed my experiences in this thread.
Best Answer