Problems with Ant+ connectivity

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?

This is what the rest of us are experiencing as well. It is "normal" in the sense that most Fenix 5's exhibit this and your unit is not faulty. However, it is clearly a design defect that requires rectification but Garmin has been unwilling to acknowledge the issue (as a recall will likely be very expensive). I would suggest logging a call with support and making sure you have get a reference number so that you have some recourse in future when this is addressed by Garmin.

Update from Garmin support

Hi Everyone

Just to keep you in the loop. This is the latest reply received from "Chris" at Garmin support on the ANT issues:

The fenix 5 watch series does not have any issues with the Garmin fitness sensors it was designed to operate with. I'm sorry that you're having issues getting it to work with 3rd party sensors, but we would suggest using Garmin sensors with your fenix 5 watch.

He then has the audacity to close his email by "thanking" me for choosing Garmin. I replied emphasising that the ANT issues are evident with Garmin sensors such as running dynamics data on the HRM TRI but it is clear that Garmin is being dishonest and has no intention to take any repsonsbility for a major design flaw in tneir flagship product.

My advice: Avoid Garmin and coose a company that acts ethically and respects its customers.

Hi Everyone

Just to keep you in the loop. This is the latest reply received from "Chris" at Garmin support on the ANT issues:

The fenix 5 watch series does not have any issues with the Garmin fitness sensors it was designed to operate with. I'm sorry that you're having issues getting it to work with 3rd party sensors, but we would suggest using Garmin sensors with your fenix 5 watch.

He then has the audacity to close his email by "thanking" me for choosing Garmin. I replied emphasising that the ANT issues are evident with Garmin sensors such as running dynamics data on the HRM TRI but it is clear that Garmin is being dishonest and has no intention to take any repsonsbility for a major design flaw in tneir flagship product.

My advice: Avoid Garmin and coose a company that acts ethically and respects its customers.

Not everyone is having the same problems though. My personal experience...

• I have two HRM-RUN heart rate sensors (the ones with the detachable module), I have have had no issues with drop-outs on either. All running dynamics data, HR etc has been solid.
  
• Two Tempe sensors, again no issues at all. In contrast to the Fenix 3 where it would occasionally drop connection and replace the temperature measurement with the internal one.
  
• Again, two bikes both with speed and cadence sensors. No problems at all. Rock solid.
  
• Not Ant+ but the Bluetooth connection to my smartphone (Nexus 6P) has been more reliable than the F3. On the occasion that the connection has been lost, a simple toggle of the connection setting restores it.
  

For info, watch is a Fenix 5, received 16th March in the UK.

The fenix 5 watch series does not have any issues with the Garmin fitness sensors it was designed to operate with.

I presume Chris has never seen the list of compatible products here? You need to escalate your support call to the next level because Chris doesn't seem to be providing correct information. It states clearly on the page "*This [fenix 5] product is ANT+ Certified".

Not everyone is having the same problems though. My personal experience...

• I have two HRM-RUN heart rate sensors (the ones with the detachable module), I have have had no issues with drop-outs on either. All running dynamics data, HR etc has been solid.
  
• Two Tempe sensors, again no issues at all. In contrast to the Fenix 3 where it would occasionally drop connection and replace the temperature measurement with the internal one.
  
• Again, two bikes both with speed and cadence sensors. No problems at all. Rock solid.
  
• Not Ant+ but the Bluetooth connection to my smartphone (Nexus 6P) has been more reliable than the F3. On the occasion that the connection has been lost, a simple toggle of the connection setting restores it.
  

For info, watch is a Fenix 5, received 16th March in the UK.

Same here. I use Tempe, Bike Speed, Cadence and Premium Soft strap HRM and all have worked without issue. Even the GPS works fine. In fact, the last couple of rides / walks, it has been spot on. Literally within a couple of metres of where we were. It seems that all F5's are not performing the same for whatever reason.

Here's an example of an afternoon dog walk, which many feel return the worst tracks due to slower speeds.


I'm running 4.1 FW and I've been using the Beta releases as they become available.

So I took my brand new F5 to the gym for the first time today, and used it with my Scosche Rhythm OHR band on my right arm above my bicep, connected via ANT. It was also connected to my iPhone via Bluetooth. The watch was on my left wrist.

On the Recumbent spinbike, a couple dropouts not too bad:




On the treadmill, a lot of dropouts I even saw it on the watch at the time saying "No zone" and the HR way low:




...continued in a second post because apparently you can only include 4 images in one post....

The dropouts may be coinciding with faster pace (and greater arm movement??):



Activity simultaneously recorded to iPhone via BT, maybe not very helpful:



As a comparison, here is an outdoor run with the inbuilt wrist HR sensor:



So it seems to me there is a fair few dropouts occurring which is not very impressive. Next time I will try it on the same arm, or via Bluetooth, but really you shouldn't have to do that.....

I received a similar useless response from Garmin

Hi Everyone

Just to keep you in the loop. This is the latest reply received from "Chris" at Garmin support on the ANT issues:

The fenix 5 watch series does not have any issues with the Garmin fitness sensors it was designed to operate with. I'm sorry that you're having issues getting it to work with 3rd party sensors, but we would suggest using Garmin sensors with your fenix 5 watch.

He then has the audacity to close his email by "thanking" me for choosing Garmin. I replied emphasising that the ANT issues are evident with Garmin sensors such as running dynamics data on the HRM TRI but it is clear that Garmin is being dishonest and has no intention to take any repsonsbility for a major design flaw in tneir flagship product.

My advice: Avoid Garmin and coose a company that acts ethically and respects its customers.

My Stryd so far works fine with my 5s and its on opposite foot to arm. I moved to garmin from polar (v800) and have not been impressed with various issues. TBH if polar come out with a V900 or whatever I'll be moving back.

Missing Information

For the record, ColinvZ is not mentioning the rest of the conversation we had: I suggested that if he is having connectivity issues with a sensor to call and speak with product support so that the issue can be troubleshot. I also suggested that he check the data he is getting somewhere else besides Connect to see if he really is losing data. I mentioned the last point in another thread where we saw that total ascent and descent number change and match up between a fenix 5 and an Edge 500 when compared in BaseCamp.

To add a different perspective and maybe even show that I am not the "hobgoblin" that I am reported to be: as you see with the previous posts, some people aren't having any issues with 3rd party sensors. I have conversed earlier today with another "regular" to these forums, and he has noticed that his power meter dropouts occur only when he has his four Connect IQ apps installed to his watch, but no dropouts when they aren't installed. He said a different post inspired him to look at some previous data on a hunch. He's going to test it. If this turns out to be the case, it links the problem with a vector that was beyond anyone's imagination.

So, for anyone having sensor drop out issues, try removing all of your Connect IQ apps, watch faces, widgets, and data fields. Make sure to restart the watch after all the Connect IQ stuff is uninstalled. The person I was talking with earlier today is bright and meticulous, and he just might be on to something. I'll leave it up to him to reveal himself if he wishes to do so.

Hi Chris

Thanks for joining the discussion. I would like to put the record straight. I previously called support and was told that my running dynamics problems (with Garmin sensors) were as a result of me walking between intervals (some running dynamics data like stride length should still record). The person was unwilling to escalate the matter or give me a reference number. I then logged the fault via email and in all responses I was told that Garmin is "working on the problem" until your response (with which I was clearly disappointed).

You have also neglected to mention that I sent you signal tests proving the inferiority of the Fenix 5 and 5S signal (by a factor of more 10x!) compared to four other similar Garmin units (including the 5X and 935) clearly pointing to a hardware fault.

I have done all the usual troubleshooting such as factory resets etc. I do not have any ConnectIQ apps installed. Other people experiencing the problems such as TheIncredibleFlash (earlier in this forum) have experienced the same. He tried two Fenix 5s units with no success but his problems were immediately resolved when moving to the 935.

Finally, why does Stryd list all other Garmin units, including the 935 and 5X as compatible but exclude the Fenix 5 and 5S if there is no hardware defect?

I agree with c0052350. We should really not be spending so much time troubleshooting products that cost so much. Garmin should be doing it before they launch the products.