Problems with Ant+ connectivity

Fenix 5 Sapphire with HRM-Tri

Got the Fenix 5 Sapphire bundle and was unable to find the HRM-Tri, had to go back to 2.90, anyone else tried the HRM-Tri with the 3.30 version?

ANT+ still drops in a situation where I'd think it shouldn't. Maybe my expectations are too much? Anyway...

• Scosche Rhythm+, fw 2.62, on left arm above bicep with optical unit positioned more towards chest than away.
  
• Spartan Ultra, fw 1.8.26, on left wrist, paired to Rhythm+ via Bluetooth
  
• fenix 5, fw 3.30, on right wrist, paired to Rhythm+ via ANT+
  

Started out the run with both units reporting HR from the Rhythm+, but it didn't take long for the f5 to drop and switch to optical HR. I stopped and switched the f5 optical HR from auto to off, thus forcing it to solely use the Rhythm+. Still had signal drops on the f5. I then switched the Rhythm+ to the same arm as the f5 and no drops at all. For grins, I even switched optical HR back to auto and still had no drops.

My assessment is, the f5 is very temperamental with ANT+ distance. I've been using the Spartan Ultra on my left wrist and Rhythm+ on the right arm above the bicep for, heck, I don't know how long with zero drops. Guess I'll have to try the f5 with Bluetooth on the Rhythm+.

I have exactly the same testresults with F5 sapphire and scosche Rhythm+. I used to wear the rhythm+ on the right side upper arm and the watch on the left. Used this setup for 2 years with a Fenix 3 and never expierenced a signal drop. My thoughts: Garmin reduced transmitting power on the F5 to save battery usage.

More drops occur when running in windy conditions and wearing loose clothing with short leaves. Will do another test today wearing the sensor on the same side as the watch.

RD Pod - Fail

Just got off the phone with Garmin support. They stated the ANT+ connectivity is a software issue. I was prepared to send my F5 in to get a replacement but they asked me to wait for the next software update.
The RD pod is also not working for me. Started using it last week. Nice thing but it constantly drops the signal. The running dynamics screens actually disappear after a few minutes into a run. The data is being collected but you can't see it after the first drop. Big bummer and just another big issue.
At this point my F5 is NOT able to:
- Leverage my PT P1 pedals (tried ANT+ & bluetooth)
- Stryd
- RD Pod

Just got off the phone with Garmin support. They stated the ANT+ connectivity is a software issue. I was prepared to send my F5 in to get a replacement but they asked me to wait for the next software update.
The RD pod is also not working for me. Started using it last week. Nice thing but it constantly drops the signal. The running dynamics screens actually disappear after a few minutes into a run. The data is being collected but you can't see it after the first drop. Big bummer and just another big issue.
At this point my F5 is NOT able to:
- Leverage my PT P1 pedals (tried ANT+ & bluetooth)
- Stryd
- RD Pod

Thanks for the update, much appreciated.

The biggest cause of connectivity issues for me seems to be when my body is between my watch and the sensor it's connecting to. I guess with an RD pod that becomes quite a big problem.

Just got off the phone with Garmin support. They stated the ANT+ connectivity is a software issue. I was prepared to send my F5 in to get a replacement but they asked me to wait for the next software update.

I wonder, why such statement is not provided at least by a Garmin employee on the forum.
Otherwise it could be like this:
cpcervelo01: "I want to exchange my F5"
Random Garmin consultant on the phone: (thinking for a plausible expplanation) "Its definitely software issue" (Problem solved)

Just got off the phone with Garmin support. They stated the ANT+ connectivity is a software issue. I was prepared to send my F5 in to get a replacement but they asked me to wait for the next software update.
The RD pod is also not working for me. Started using it last week. Nice thing but it constantly drops the signal. The running dynamics screens actually disappear after a few minutes into a run. The data is being collected but you can't see it after the first drop. Big bummer and just another big issue.
At this point my F5 is NOT able to:
- Leverage my PT P1 pedals (tried ANT+ & bluetooth)
- Stryd
- RD Pod

Is that only ANT+ at stakes here? what about always dropping the BT connection with phone/GCM that I moan about all over this forum? :). Asking, as I was offered a replacement by Garmin support, because of this BT issue and I still think it's SW problem...

Just done my first run on 3.30. It looks as though I didn't get any dropouts in Running Dynamics data from my hrm-run4, even when dropping my arm. I did however get a complete disconnect from it but this was only when I put my watch arm right up behind my back. It's still only one quick run but so far things are looking good. Hopefully when my Stryd arrives I won't have any issues, fingers crossed.

Just done my first run on 3.30. It looks as though I didn't get any dropouts in Running Dynamics data from my hrm-run4, even when dropping my arm. I did however get a complete disconnect from it but this was only when I put my watch arm right up behind my back. It's still only one quick run but so far things are looking good. Hopefully when my Stryd arrives I won't have any issues, fingers crossed.

This is good news. I really hope software can fix this issue (I am still concerned that this is a hardware design flaw as the Fenix 5x and 935 do not have this problem).

I followed up on progress with Garmin support on Friday and their response was "As stated before we do not have an estimated time of resolution. You will be notified when the case has been closed. At this moment the case is still under investigation."

A reminder to everyone experiencing ANT+ connectivity issues to please log the issue with Garmin support at https://support.garmin.com/en-US/?productID=552982&topicTag=region_sensors so that Garmin is aware of the extent of the problem and you can be notified of a resolution (particularly if a product recall is necessary). I know a few have contacted the beta team but they can only address software problems and it is important that Garmin support is also aware of the issue in case of hardware problems.

This is good news. I really hope software can fix this issue (I am still concerned that this is a hardware design flaw as the Fenix 5x and 935 do not have this problem).

I followed up on progress with Garmin support on Friday and their response was "As stated before we do not have an estimated time of resolution. You will be notified when the case has been closed. At this moment the case is still under investigation."

A reminder to everyone experiencing ANT+ connectivity issues to please log the issue with Garmin support at https://support.garmin.com/en-US/?productID=552982&topicTag=region_sensors so that Garmin is aware of the extent of the problem and you can be notified of a resolution (particularly if a product recall is necessary). I know a few have contacted the beta team but they can only address software problems and it is important that Garmin support is also aware of the issue in case of hardware problems.

Have you tried 3.30 yet? If I remember correctly you had/have what seems to be the exact same problem as me.