Problems with Ant+ connectivity

after few workouts on 3.30 (beta)
- don't see any HR dropouts, except when I put my hand on my back
- except the 1st workout, I cannot identify significant power/cadence/speed sensor dropouts because:
-- its difficult to distinguish between power/cadence dropout and a moment, when i indeed stopped pedaling
-- I believe, that in case of speed sensor dropout, the speed is taken from GPS, so you cannot see it on the graph.
Anyway, for the second point, if any dropouts, these are not significant. Whats interesting, on my first training on 3.30 there were many power dropouts, though.

I have 3.30 om my F5 and have seen NO improvement with Wahoo BlueSC and ANT+ on the bike. Keeps on dropping the link, a 40 k ride becomes a 35k ride wit the F5. Seems like even moving legs while pedalling is a problem for the F5. What i don't get is how the F5 is so poor and the Edge bike computer doesn't have the issue.

What i also don't get is that Garmin doesn't seem to answer our questions especially on very expensive pieces of kit... Poor

How do you choose Bluetooth over Ant+ for Fenix 5 to connect to Stages?
Have searched all over and can't find out how.

Thanks.

When adding a sensor, there's an option at the bottom to search for Bluetooth sensors.

I did this yesterday with a Scosche Rhythm+, first adding as ANT+ then Bluetooth after the ANT+ drops. If I recall correctly, it was the search for all option, then scroll down to the bottom and there's an option for searching Bluetooth sensors. Unfortunately, I don't have any sensors with me right now to test.

I've tried to find this following these suggestions and nothing. I've tried long-pressing, connecting via ANT+ and waiting for it to disconnect and looking for an option/searching again, walking further away after it connects via ANT+ on the initial pairing... Nothing... It does say (for about 0.10 seconds) something about Bluetooth sensors when I initially pair the power meter, I've tried to quickly click, search for the menu/long press... Nothing... It goes away too quickly.

My 4iii's single-sided power meter is unusable on my 5S (98% disconnected on a ride), while having zero issues on my 510. Weirdly, my Tacx Vortex Smart has no issues connecting via ANT+ to the 5S with no drops in close to a dozen rides (and it's probably a meter further away).

Does anyone please have a step by step guide to preferentially connecting bluetooth over ANT+ either device wide or sensor specific? I'd like to get this working just to see if it makes a difference...

I actually wouldn't care about this (I'll use my 510 still as a head unit) if Garmin would fully integrate metrics captured on other Garmin devices with the Fenix 5. I don't like how it MUST be captured on the Fenix 5 to get things like VO2 max, training load, etc...

It's starting to be ridiculous

Really frustrated. This is a pretty expensive watch.

Following a number of runs and bike rides after upgrading to FW 3.3.:
- Continued long dropouts on all devices (Stryd, Powertap P1 & Running Dynamics pod)
- It doesn't matter if I connect my power meter via bluetooth or ANT+
- The running dynamics pod is fairly useless: it is connected at the beginning of a run but the data pages disappear 1-2 min into a run (basically after the first drop)

To make things worse, the F5 switched itself off during a bike ride today and came back automatically 1-2 miles later.

It would be greatly appreciated to get an official statement from Garmin about this. It's been weeks and there is no solution in sight. I have a bunch of equipment such as the Stryd and a powermeter - all this stuff is pretty much useless right now.

Really frustrated. This is a pretty expensive watch.

Following a number of runs and bike rides after upgrading to FW 3.3.:
- Continued long dropouts on all devices (Stryd, Powertap P1 & Running Dynamics pod)
- It doesn't matter if I connect my power meter via bluetooth or ANT+
- The running dynamics pod is fairly useless: it is connected at the beginning of a run but the data pages disappear 1-2 min into a run (basically after the first drop)

To make things worse, the F5 switched itself off during a bike ride today and came back automatically 1-2 miles later.

It would be greatly appreciated to get an official statement from Garmin about this. It's been weeks and there is no solution in sight. I have a bunch of equipment such as the Stryd and a powermeter - all this stuff is pretty much useless right now.

My connections with Stryd and RD Pod are rock solid. So not a software problem with F5X.
There are more widespread Stryd issues reported for F5/5S only. None I have seen for RD Pod except yours.
Have you contacted Garmin? It may be a faulty watch.

Have you contacted Garmin? It may be a faulty watch.

I would guess so. I have 5 Sapphire, and although there were some dropouts, currently I cannot identify any significant problems...

Today another try . F5 with scosche rhythm+ heart rate sensor.



NO DROPS IN ANT+

Difference from last try: I had the scosche armband on same arm as fenix 5

GARMIN Developers: it's the distance between the device and the sensor that cause the problems. Just adjust the test protocol into a safe distance.

So...
What y'all are saying is that my drop problem while using a garmin chest strap is NOT the fault of my physical attributes?

Hmmph. Well it makes sense. I never had problems staying linked before the Fenix 5s.

Difference from last try: I had the scosche armband on same arm as fenix 5

GARMIN Developers: it's the distance between the device and the sensor that cause the problems. Just adjust the test protocol into a safe distance.

I always use the Scosche on the same arm. On the different side I don't have any or very bad connection to my 910xt. I tested it during my runs with F5, Scosche on left arm, 910xt on right arm. Doesn't work with 910xt... Not only a F5 problem.

On the same arm, no problems at all... Only once during my time with a 935. It was very disappointing for me that the highly cheered 935 worked so bad for me. Not even a little extended bluetooth range and dropouts in Ant-connection (only once to be honest).

With a chest strap it doesn't matter on which side you wear the watch. (of course) That's why I used this setup if I wanted to run with two watches to check accuracy etc...