Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bug report: HR spiking when stopping at a red light

FoleyRose
over 2 years ago

My HR seems to spike up when I stop at a red light, which seems illogical to me. It then seems to go back down to where I think it should be when stopping. It seems to happen whether I pause the activity at red lights or not, and also whether I use a chest strap or not.

This is my last run that I did yesterday, you can see the worst example around the 30min mark:

I upgraded from a Forerunner 645 in January and my old watch never showed anything like this. Do you guys think this is a bug or maybe a defect? I'm on the latest beta right now but this has been happening since I got the watch.

  • Former Member
    0 Former Member over 2 years ago in reply to FoleyRose
    [deleted]
  • 0 over 2 years ago in reply to Former Member

    From the table you posted, the spike starts 3 seconds before I even start moving.  It tends down for 8 seconds, starts going up while I'm still standind still, I start running, it keeps raising and after around 22 seconds of running, it plummets to where I think my 12 seconds or so of not running should have lowered my HR.

    Nothing particularly noteworthy happens during those stops.  I just stare at the pedestrian crossing countdown for the other directions and wait.  It would also be highly unlikely that something worhty of a spike in HR is happening at every red light, every time I run.

    The way I see it, there's only 2 possibilities:

    1, my HR does spike when I stop for some biological reason

    2, there's a bug somewhere that introduces errors

    I'm more inclined to think it's the second option.  I have a similar length run this afternoon, I'm gonna use my HR chest strap and see the results.

  • Former Member
    0 Former Member over 2 years ago in reply to FoleyRose
    [deleted]
  • 0 over 2 years ago in reply to Former Member

    Today's run isn't going to help us.  It was really hot here for the first time this year (22°C) and I struggled to keep my heart rate down and then completely gave up and just picked up the pace.  I also switched from chest strap to watch to chest strap again, paused and forgot to resume.

    All in all, it was a mess of a run data wise.  Besides that it was actually really enjoyable.

    My next run that could help is gonna be on Saturday morning, so I'll post that one instead.

    Side note, reached out to me by email and I went through the steps to submit my data, so hopefully we'll have an answer or a fix soon.

  • 0 over 2 years ago

    After some more investigation, it seems like this issue started for me when I updated from SW version 13.23 to 14.13.  Before then, my HR readings were as I would expect them to be when stopping at a red light.

    I wasn't really paying attention to my HR back then, so I didn't catch the change.

  • 0 over 2 years ago

    It's still happening with beta SW version 5.11. And it seems like my hunch was right, I need to stop for at least 5 seconds to trigger the HR spike. I had a 3 second stop and it looks fine on the graph.