# Heart Rate on strava issue

**URL:** <https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991>\
**Category:** SYSTM Software\
**Created:** [September 30, 2021, 11:23pm UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991 "2021-09-30T23:23:47Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![MaxT](https://sea2.discourse-cdn.com/flex020/user_avatar/wahoox.forum.wahoofitness.com/maxt/32/7140_2.png) [@MaxT](https://wahoox.forum.wahoofitness.com/u/MaxT)\
**Post date:** [September 30, 2021, 11:23pm UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/1 "2021-09-30T23:23:47Z")

</div>

Is this a known bug ? When I upload my training to strava, the heart rate is weird.  
I did 2 trainings with Wahoo SYSTM and this is the same for both trainings.

Thanks

Strava

 ![image](https://us1.discourse-cdn.com/flex020/uploads/thesufferfest/original/2X/2/291c86c59e00b201bad20569872b483491039cf5.png)  
Systm  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/thesufferfest/original/2X/2/2ac42e35a74d6bb0a346304ee30bf137bf30c581.png)

---

<div class="post-metadata">

**Author:** ![JSampson](https://sea2.discourse-cdn.com/flex020/user_avatar/wahoox.forum.wahoofitness.com/jsampson/32/3148_2.png) [@JSampson](https://wahoox.forum.wahoofitness.com/u/JSampson)\
**Post date:** [October 1, 2021, 1:37am UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/2 "2021-10-01T01:37:36Z")

</div>

@MaxT Definitely looks odd - probably interference or something. Maybe put in a ticket with the minions.

---

<div class="post-metadata">

**Author:** ![Colo\_Bati](https://sea2.discourse-cdn.com/flex020/user_avatar/wahoox.forum.wahoofitness.com/colo_bati/32/7240_2.png) [@Colo\_Bati](https://wahoox.forum.wahoofitness.com/u/Colo_Bati)\
**Post date:** [October 3, 2021, 3:34pm UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/3 "2021-10-03T15:34:30Z")

</div>

Have exactly the same issue with the new app. On the old one works fine. So is not an interference but something related to software…

---

<div class="post-metadata">

**Author:** ![MaxT](https://sea2.discourse-cdn.com/flex020/user_avatar/wahoox.forum.wahoofitness.com/maxt/32/7140_2.png) [@MaxT](https://wahoox.forum.wahoofitness.com/u/MaxT)\
**Post date:** [October 3, 2021, 4:51pm UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/4 "2021-10-03T16:51:44Z")

</div>

On SYSTM, heart rate looks fine. When it syncs with strava, the issue appears.  
When I upload the fit file on strava and on Xert, there is an issue.  
Everything seems fine when I upload the TCX file.  
Some of my workout sync correctly, but the majority have issue.  
I raised a ticket, let’s see …

---

<div class="post-metadata">

**Author:** ![SteveK](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@SteveK](https://wahoox.forum.wahoofitness.com/u/SteveK)\
**Post date:** [October 8, 2021, 10:25am UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/5 "2021-10-08T10:25:26Z")

</div>

I too have exactly this issue. When I “zoom in” using Analyse on Strava, it looks like it’s recorded two data points correctly, then one zero, and repeats that pattern over and over.  
This first started happening to me about a week before the SF-\>System switch over…

---

<div class="post-metadata">

**Author:** ![MaxT](https://sea2.discourse-cdn.com/flex020/user_avatar/wahoox.forum.wahoofitness.com/maxt/32/7140_2.png) [@MaxT](https://wahoox.forum.wahoofitness.com/u/MaxT)\
**Post date:** [October 8, 2021, 1:20pm UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/6 "2021-10-08T13:20:40Z")

</div>

It is not always happening, green = good data, red = 1/3 HR points is 0

 ![image](https://us1.discourse-cdn.com/flex020/uploads/thesufferfest/original/2X/6/6eed52d9586a4197af8a0ad830d14e3df78b4d8c.png)

---

<div class="post-metadata">

**Author:** ![MaxT](https://sea2.discourse-cdn.com/flex020/user_avatar/wahoox.forum.wahoofitness.com/maxt/32/7140_2.png) [@MaxT](https://wahoox.forum.wahoofitness.com/u/MaxT)\
**Post date:** [October 8, 2021, 5:50pm UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/7 "2021-10-08T17:50:05Z")

</div>

Response from Wahoo, makes sense.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/thesufferfest/original/2X/9/94f0455205bf8a3c3059209feea419dc4107938d.png)

---

<div class="post-metadata">

**Author:** ![SteveK](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@SteveK](https://wahoox.forum.wahoofitness.com/u/SteveK)\
**Post date:** [October 9, 2021, 4:31am UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/8 "2021-10-09T04:31:53Z")

</div>

Thanks for forwarding their response. In my case it’s not paired with anything else, but I will remove Garmin Connect from my phone just in case and… hope.

---

<div class="post-metadata">

**Author:** ![titanicus](https://sea2.discourse-cdn.com/flex020/user_avatar/wahoox.forum.wahoofitness.com/titanicus/32/5265_2.png) [@titanicus](https://wahoox.forum.wahoofitness.com/u/titanicus)\
**Post date:** [October 9, 2021, 1:39pm UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/9 "2021-10-09T13:39:51Z")

</div>

FWIW, I’ve never had problems with Garmin Connect on my _phone_ being in the vicinity of my training setup

But

I have nothing other than my Forerunner 920XT paired to GC and I run SYSTM on a laptop, and I don’t usually double-record (i.e. both SYSTM and my watch tracking the workout).

---

<div class="post-metadata">

**Author:** ![SteveK](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@SteveK](https://wahoox.forum.wahoofitness.com/u/SteveK)\
**Post date:** [October 13, 2021, 1:33am UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/10 "2021-10-13T01:33:24Z")

</div>

I just had a response from Wahoo as follows (and kudos to them for the prompt, personalised and genuine reply):

> [@](#):
>
> Thanks for reaching out. We have had some issues with the desktop version of SYSTM connecting to Bluetooth sensors. This is something that is being looked into. We have found that a good workaround for the moment is to connect via ANT+ as there are no issues using this connection.
> 
> Sorry for the inconvenience. Make sure to keep your app up to date as this will likely be addressed in future updates.

So I’ve got a cheap ANT+ dongle on the way from eBay…

---

<div class="post-metadata">

**Author:** ![JureL](https://avatars.discourse-cdn.com/v4/letter/j/2acd7d/32.png) [@JureL](https://wahoox.forum.wahoofitness.com/u/JureL)\
**Post date:** [October 18, 2021, 6:27am UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/11 "2021-10-18T06:27:21Z")

</div>

It makes sense turning off BT on your device with Garmin connect. I’m going to try that next time.  
But I’m not convinced this is a problem with Strava. I’ve also uploaded a couple of activities from Zwift and the HR data looks perfectly fine. (I have used the same setup - laptop(bluetooth) + Garming dual HR strap + Tacx flow smart).

---

<div class="post-metadata">

**Author:** ![SteveK](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@SteveK](https://wahoox.forum.wahoofitness.com/u/SteveK)\
**Post date:** [October 20, 2021, 2:42am UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/12 "2021-10-20T02:42:31Z")

</div>

Yeah it’s not an issue with Strava - it’s an issue with SYSTM and bluetooth sensors. It just shows up on Strava due to how the data is charted. See my post above where I quote a response from Wahoo. They say it’ll be fixed…

I spent $20 and got an ANT+ dongle off eBay. It’s annoying to have to do it, but it works.

---

<div class="post-metadata">

**Author:** ![JureL](https://avatars.discourse-cdn.com/v4/letter/j/2acd7d/32.png) [@JureL](https://wahoox.forum.wahoofitness.com/u/JureL)\
**Post date:** [October 26, 2021, 6:39pm UTC](https://wahoox.forum.wahoofitness.com/t/heart-rate-on-strava-issue/11991/13 "2021-10-26T18:39:03Z")

</div>

Looks like they’ve fixed it now!
