06-23-2024
16:08
- last edited on
06-24-2024
03:23
by
MarreFitbit
06-23-2024
16:08
- last edited on
06-24-2024
03:23
by
MarreFitbit
During a long fast walk my Versa 4 will start a pattern of buzzing every 3 to 5 seconds and just keeps doing it until it makes my hand numb and drains the battery. I thought it must be HR zone changes, so I turned that notification off, and it still does it. It doesn't show any notification on the watch face, it just buzzes. I still think it might be HR zone changes, it is just that the switch to disable, doesn't actually disable.
Anyone else have this problem and how did you fix it?
Moderator Edit: Clarified subject
06-23-2024 21:27
06-23-2024 21:27
Hi @Billsnature - have you tried to restart it first (and then check slso the other run settings again as well) by holding the watch button for 10 seconds till it blanks or vibrates and wait for the logo to appear and for it to start?
Author | ch, passion for improvement.
06-24-2024 03:43
06-24-2024 03:43
Hi there, @Billsnature. It's nice to see you around the Fitbit Community Forums. Thanks for bringing this to my attention and for the troubleshooting steps you've tried. I'm sorry to hear that your Versa 4 keeps vibrating every 3-5 minutes. I understand your concern, we're here to help you!
To better assist you, please make sure you've turned off the notifications by following the steps below:
Weekly Active Zone Minutes notifications:
For more information, see What are Active Zone Minutes or active minutes on my Fitbit device?
Have you tried what @Guy_ suggested?
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
07-08-2024 19:02
07-08-2024 19:02
I don't have the problem solved just yet, but there is a chance I figured it out. Somehow, it may have been auto detecting a run during exercise that I declared as a walk. I just turn auto detect in the Run set-up off and the buzz on zone changes in run to off I will see over the next week if that solves it. A reset did not solve it, hopefully this will