Problems with Ant+ connectivity

As someone thinking of buying an F5 that's worrying. What's confusing is there seems to be many with no issues. But I agree the lack of response by Garmin is bad customer service.

A related question: Has anyone with F5 who DID have ANT+ problems had the problem fixed by newer firmware versions?

Also, anyone successfully using the Garmin speed and cadence sensors as well as Scosche HRM?

Same here, also thinking about spending 700 (!) EUR for a running watch.

Even more disappointed I am by Garmin not acknowledging this issue. Avg pace and accurate distance is key for a running watch - at least either by GPS or pairing a footpod; both seems to be impossible for the Fenix 5.

Is anyone able to explain to me, how this can be a software issue. I really would like to believe this; just I can't (before someone explains).

BTW, is Garmin not testing these devices before they are placed on the market? I once had the FR620; similar issue with GPS.
I have never seen something like this by Polar so far (unfortunately Polar does not offer a watch that is suitable to wear all day).

I think this is issue happen, because limit only one device can be pair , and HRM+footpod is too much

I thought it would be useful to summarise what I know about this issue so far:

I followed up with Garmin Support on my support case again but they refuse to provide a meaningful update and only stated that "I apologize for the wait as we are investigating this issue. I see that this case is still currently being worked by our engineers. Unfortunately I am not able to give a set timeline for the resolution."

It appears that, while many experience ANT+ (and Bluetooth) issues, many others do not. I do suspect that this may be related to each use case as I note on the serial number thread that many have not yet tried to connect to ANT devices or have only connected to HRM straps. Many of us that have experienced the issues have tested with different ANT devices and different Fenix 5 devices (from different manufacturing batches) and can reliably reproduce the issues. We typically do not experience the issue with HRM (apart from minor drops) but do experience the issue with more complex ANT signals that, presumably, require more bandwidth. In my case it is running dynamics data that drops out on my HRM-TRI whenever my wrist is further away from the HRM-TRI. Others have had similar issues with power meters and STRYD pods. It is important to note that these issues are not present on other Garmin devices - only on the 5/5S.

We also know that the issue on the 5/5S is bad enough that STRYD has removed the devices from their supported devices list (at least until Garmin can resolve the issue). There is, of course, no technical reason why the STRYD does not work (as it works fine on the 935 and 5X) - it is just that the signal reception on the 5/5S is too poor and unreliable.

Some have the view that this is a software issue. I think this is unlikely as both the 935 and 5X work fine - which points to a serious design flaw that was not properly tested by Garmin's engineers during the development phase. If this deduction is correct, the only solution is a full and costly recall which may explain Garmin's silence on the matter and reluctance to provide any meaningful information despite multiple complaints of the device not performing as claimed.

I find Garmin's response to the matter completely unsatisfactory and unacceptably poor. They need to own up to their mistakes and take accountability regardless of the cost. In the meantime, my advice to anyone considering the 5/5S is to avoid the product until Garmin has formally responded to this issue so that you know what you are in for. The rest of us need to continue complaining to Garmin until they act responsibly and "do the right thing."

I posted my experience with 935 sensor drop outs in this thread...https://forums.garmin.com/showthread.php?374826-Power-meters-and-the-935/page4

I tested with latest beta firmware and still no luck. I used a 935 & 820 together to test results.

I also have not managed to connect my old Kickr to my 935 over Bluetooth.

Pretty sure the former factor of the 935 is creating a weaker ANT signal that is prone to drop outs or interference.

Dropouts with PowerTap

Does anybody NOT have problems with third party ANT+ devices and the F5? My experience is as follows:
- Stryd: not usable; tons of drop-outs on runs. Most importantly long pauses of 30-60s with zero values
- Powertap P1 pedals: around 10-20 drop-outs on a 50 mile ride; most of these drops are really short
- Stages: Useless - zero connectivity - tried Bluetooth and ANT+

Wondering if the F5 is just flawed (weak antennas?) or if I got a bad model. Spoke to Garmin support two weeks ago and they asked me to wait for further software updates.

Are there people out there that do not have these kind of problems?

I connect to the Fenix5 and an 520. About once a month on long cycling trips I will experience that the Powermeter stops reporting after around 2.5 hours on the Fenix5. The reporting on the Edge 520 is 100%. Except for this the trips (compared to my Fenix3 and 520) is always about 3-8% shorter on the fenix5). The issue with dropping the connecting to the powermeter is not consistant, I.e it will not always cut out on long trips.

(this is over and above the issues of syncing the alarm - but that appears to be a phone related software problem)

I have saved trips to show this.

Leon

PS: How do i contact garmin directly to send them sample files.

...just got the fenix 5 and it won't find any ANT sensors... when i start an activty the sensors are paired but i cannot pair them in the settings menu.. anybody got a solution for that?

ps: I'm running 3.30

Does anybody NOT have problems with third party ANT+ devices and the F5? My experience is as follows:
- Stryd: not usable; tons of drop-outs on runs. Most importantly long pauses of 30-60s with zero values
- Powertap P1 pedals: around 10-20 drop-outs on a 50 mile ride; most of these drops are really short
- Stages: Useless - zero connectivity - tried Bluetooth and ANT+

Wondering if the F5 is just flawed (weak antennas?) or if I got a bad model. Spoke to Garmin support two weeks ago and they asked me to wait for further software updates.

Are there people out there that do not have these kind of problems?

So far I've had success with Stryd footpod, Wahoo TICKR hrm and Garmin HRM run also the Garmin run dynamics pod. It's better than I expected so good until I sent my Forerunner 935 back to the retailer. My plan was to use the 935 for workouts and runs and use my F5s when I'm not working out or running but to my surprise all of my ANT+ devices work just fine as well as my Polar H7 that I use for HRV (heart rate variability) measurements every morning which is BLE as I'm sure you know.

Fenix 5 & HRM TRI

My experience so far with my Fenix 5 silver (non sapphire) is mixed. I had Fenix 3 silver before. The bluetooth range and ant range is shorter with Fenix 5. My watch is loosing connection to the phone after a few meters. The connection to my hrm tri is dropping if I raise my hands above my head or take my hands to the back, which I do sometimes when running.

I had another strange issue but it is probably not related with fenix 5. A couple of days ago I replaced the battery in my hrm tri because it was giving battery low warning. I noticed today before running that it was transmitting a very high heart rate before I even started my workout. It went fine during the workout but after I finished and took it off it continues to transmit HR over 200 which is not real. I took the battery off again ant put it back and it seems normal right now but it is a strange issue... anyone has any explanation for what my have happened?

HRM-Run fall offs

Today I had the opportunity to use the HRM-Run for a short walk trying to calibrate a MiCoach footpod. When I got home, and checked it out, I noticed a bunch of data drops for the running dynamics part of the data, however, the heart rate seems about right. Is this normal, or is this what the folks in this thread are talking about?

https://connect.garmin.com/modern/activity/1789215559