Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Versa thinks I bike every night in my sleep

Replies are disabled for this topic. Start a new one or visit our Help Center.

Hi all, I got my Versa three weeks ago and it was working great. As of the beginning of last week (11 days ago), my watch is telling me I'm biking every night in my sleep, which of course results in excessive active minutes and an average sleep record of 1 or 2 hours. Why, just last night I biked for 32 minutes at 3AM with an average heart rate of 66. I have reset my watch multiple times, have worn it on both my dominent and non-dominent wrists, have tried tightening the watch, loosening the watch, moving it up my wrists by two or three finger-widths, disabled notifications while sleeping (I'm diabetic and have alerts come through on my watch in the event of dangerous blood sugars levels, which ironically is why I bought the Versa in the first place so I really hope it's not the vibrating of notifications that makes the watch act like this). I've tried everything I've seen on the forums, to no avail. I've attached some screenshots of what's going on, and would love some feedback if anyone knows what's happening. Thanks in advance.

 

 

Best Answer
0 Votes
4 REPLIES 4

I would contact Fitbit support.  This sounds like an internal issue of the Fitbit and you'll likely need a replacement device.  Sorry this is happening to you!

Heather | Community Council | Eastern Shore, AL
Want to discuss ways to increase your activity? Visit Get Moving in the Lifestyle Discussion Forum.
Best Answer
0 Votes

That's what I was afraid of... thanks so much for your help xo

Best Answer
0 Votes

Hi @cyoung1024 - A call to Customer Support may very well be needed, however, I do suggest a restart of your device first. Sometimes little glitches happen in the firmware and a reboot has a way of fixing them. Follow the link below and let us know if it works.

 

https://help.fitbit.com/articles/en_US/Help_article/1186

Best Answer

Have reset it 3 times since the problem started occurring, hasn't fixed the problem. I'll just have to call, I guess.

Best Answer
0 Votes