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] Virtual run app won't start because it is stuck in "Ready to pair"

This feature does not work for me on the beta or the new release. I've searched all of the other posts on the forum and also watched the youtube videos to make sure I wasn't missing something about how it works. Everything works as it should until the point where I want to actually start the app on my watch. The 945 is transmitting the correct data to the 3rd party app of my choice, but it's still not saying "connected" so nothing happens when i hit start.

I've read other posts so I've tried shutting off GC on my iPhone, or connecting to the 3rd party app on my iPad and no dice. Anyone have this issue and figure out how to resolve it?

Thanks in advance!

  • Former Member
    0 Former Member over 4 years ago

    I got exactly the same issue when using TheSufferfest App! Anyone able to help here? 

  • I have the same problem. I pair to Zwift on my Samsung Galaxy S8 or on my Google Pixel Slate. The FR shows the name of the device above the 0:00 time clock. Zwift on the target device shows the heart rate but I'm unable to start the activity on my watch. The watch just says ready to pair at the top, and pressing the start button does nothing.

    While it is transmitting a rate to the device, it doesn't seem nearly as accurate as when I'm actually in an activity. I'm huffing and puffing like there's no tomorrow and it says I'm under 90 bpm. I suspect it doesn't monitor as aggressively before the activity starts, but I can't start it.

    Is that similar to what others are seeing?

  • I'm having the exact same problem as you. I can't start the activity, but it will still transmit my HR to the Zwift app, which is already paired with my Strava.... So this would be fine without starting the activity IF the HR data it was transmitting was correct, but I can barely break 100bpm and I can confirm I'm up around 160bpm by pulse. So, the data uploaded to Strava is all wonky and looks like I put in no effort. Frustrating!

    Did you manage to sort this out?

  • Nope, I never did get this to work. I've switched devices such that ANT+ is an option for me. So I've started using ANT+ broadcasting with the Virtual Bike activity, and this works fine. I believe I was trying to use bluetooth broadcasting when I was having trouble and I recall that I could never get it to work.

    Regardless of whether you're trying to broadcast or not, it seems the watch simply is not good at recording an accurate heartrate if an activity is not running. Just yesterday I did a Zwift race and forgot to start the activity on my watch. For the first 9-10 minutes my heartrate was sitting at around 90 bpm until I clued in I'd forgotten to start the activity. After starting, it quickly jumped to the 160's. I suspect this is simply a problem related to how they conserve power and the device likely samples much less aggressively without an activity running, which makes it hard to get an accurate heartrate. I suspect it does fine for "normal" HR variations, but a sudden increase due to a sudden change in exertion is just harder to detect without more aggressive (and power hungry) sampling. I have no idea if this is really what is going on, but it is consistent with what I've generally observed. Bottom line -- if you want reasonably accurate heart rate, you have to start an activity.

    My biggest concern with my original comment is that I simply wasn't able to start the activity at all, and I assume that is your main concern as well. As far as I know there is no workaround, unless you are able to switch to an ANT+ based setup.

  • I am using this Feature quite often in my Forenrunner 945 and Fenix 6. Working on both without a Problem. Will try your "wrong HR Data Problem" next time, but 99% i use a Heart strap for my Training