False incident detection.

I have the latest software (20.32). This morning's workout (using wrist heart rate) was 4 miles EZ + 2 x 9 Drills + 2 miles w-6 x (0:20 Stride + 0:20 Recovery). About the 6th drill, the incident detection started, but I was rested and feeling just fine, so I stopped it from sending. But as I was wrapping up with drill 9, it started again. But when I pressed the buttons to stop sending, it kicked me out of my workout.

Also, it is my vibe over the years that I have had the FR955; its wrist-based heart rate doesn't sync up with reality. A couple of years ago, I was a half-mile into an easy run, and it alerted me that my heart rate was 178 bpm and that I may need to stop to breathe. I was just fine and continued with my easy run.

Anyway, there was no reason to kick off incident detection this morning. If you want me to actually set up incident detection, then I believe you need to work on the wrist heart rate sensitivity or calibration.

  • Same thing has happened with my FR955 twice since last night, while my watch was plugged in and charging.  Last night my wife and I heard a weird sound while we were watching TV and had no idea what it was.  This morning I was emptying the dishwasher, heard the same sound and saw the emergency contacts alert on my watch so I quickly turned it off and let my parents know I was ok.  They had gotten an emergency notification.  In both cases there was clearly no emergency so I'm not sure what's triggering this??

  • Same to me with latest beta, during rest phase of an interval training started the countdown for incident detection

  • Same for me, but it's been like that for at least a year. If finish a sprint and sit down a little too heavily the Incident Detection triggers.