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

Wahoo Tickr X - ANT + vs Bluetooth

I'm having issues with my new Tickr-X reporting wildly high HR for 5 - 10 minutes in my runs when paired in ANT + with my 935. The 935 is on version 20.0 firmware.

You can see that my pace is slowly increasing, yet the HR reading thinks I'm over max until suddenly it drops to the correct rate and functions properly from then on. This doesn't happen over ANT+ when connected to my Garmin Edge 530 or my iMac (for Zwift). I also confirmed that if I connect to the 935 via Bluetooth, the readings are correct. But then I don't get the running dynamics offered by the Tickr-X.

Anyone have this same issue?

  • I wonder if your Bluetooth vs Ant comparison with the FR935 is random luck or another factor solving the issue.  That aspect of your description truly sounds really weird.

    It also seems like you are questioning device (Edge vs PC vs FR935) but i presume these tests were each with different activities and not simultaneous recording of the same activity with notably different data observed.

    For me personally, I’ve seen early HR data errors like this usually with strap / shirt / sweat issues.  I would see it most in colder + less humid weather when it takes some time for me to start sweating and my shirt rubs the strap of the sensor causing a static issue.  Often some combination of wetting the strap, contacts, shirt or getting a new strap helped me.  The HRM TRI seems to work very well for me and hasn’t shown this year, while older Garmin straps and Wahoo straps (I have 2  TICKR X original model) show it from time to time.

  • Yes with regard to the different activities, as the edge is a bike computer. But regardless of whether the bike is on the road or on my trainer in the house, it records the HR data correctly. I suppose I could put the edge in my pocket and let it record on a run to verify that they both record the same or differently. Good idea...

    I am confident of the connection and strap connectivity to my skin. I've been using these things since the days of the early Polar straps back in the 1990s. Good moisture amount before the strap goes on.

    So I ran again today, but I did something slightly different... No workout was loaded. I just did a short 20 minute run, but used the ANT+ connection and did not have the same issue! I'm going to try this again early tomorrow morning for my long Sunday run to see if it acts any differently. I did run a different route today than normal, but started from the same location.

  • Former Member
    0 Former Member over 4 years ago in reply to 7204891

    Hey! I’m having the exact same problem. The tickr x is my second heart rate replacement from wahoo and I can’t use it in workout mode with the FR 935

    did you find a solution? 

  • My solution was to purchase a Garmin HRM-Tri. The Wahoo strap is in a drawer. No issues at all with the Garmin device.

  • Yes, I've had the issue and have gone through 2 Tickr X sensors and 3 HR straps before I figured it out. It's not the best answer, but it has something to do with the speed and cadence sensor. After I went through the first sensors and straps (all under warranty through Wahoo) I decided not to update the TIckr's firmware or connect speed and cadence. All worked fine.

    Didn't actually realise this was the reason until last week when I accidently paired the speed and cadence sensor (thought I was pressing start on the watch, but clicked 'yes' to pair) and my HR was so low. Went into settings, removed the speed and cadence and voila, HR back to normal.

    Obviously this goes against the fact that you're using the Tickr X as you can't get the dynamics data, as you've said before. But it's the only workaround I've come across so far.

  • I wonder if your Bluetooth vs Ant comparison with the FR935 is random luck or another factor solving the issue.  That aspect of your description truly sounds really weird.

    It also seems like you are questioning device (Edge vs PC vs FR935) but i presume these tests were each with different activities and not simultaneous recording of the same activity with notably different data observed.

    For me personally, I’ve seen early HR data errors like this usually with strap / shirt / sweat issues.  I would see it most in colder + less humid weather when it takes some time for me to start sweating and my shirt rubs the strap of the sensor causing a static issue.  Often some combination of wetting the strap, contacts, shirt or getting a new strap helped me.  The HRM TRI seems to work very well for me and hasn’t shown this year, while older Garmin straps and Wahoo straps (I have 2  TICKR X original model) show it from time to time.

    Thanks for the clarification