Problems with Ant+ connectivity

My new F5 SN: 53701...

i got also a new one as replacement because of poor ant+, new one is better. SN is same, 53701xxx

I got a replacement watch, due to elevation problems, and did one ride on my home trainer, with garmin HR and garmin speed sensor. Lot of dropouts. Previous SN 53A..., new SN 53A...
https://imgur.com/ZXfS9Jo
:( :( :(
I need to go test outside, but did you encounter more problems while indoors?

You know that 53A means that you got a sapphire model. More interested in 53A??xxx

I think F5 is totally a bad product with so many issues like ANT+ and GPS weakness.

I can't believe Garmin still keeps these issues and get money from customer via sell these.

Even my old Vivosmart HR+ gives better experience on GPS tracking and Heart Rate measurement.ciq.forums.garmin.com/.../1281366.png

I’ve been facing problems with F5s connectivity since June when I bought my first HRM Run.
Yesterday I decided to sent back to garmin both, watch and strap. I’m really disappointed. Just look at the pictures... :(ciq.forums.garmin.com/.../1282904.jpg

I have a Tacx genius trainer and connected my F5 to the power, cadence and speedsensor on the trainer. Massive dropouts! My recorded ride on PC was 27k and on my F5 it was only 17k. Is there any news from Garmin on this issue yet? I am on the newest Firmware (7.1) .

Just to note again that HRM-RUN seems to be better avoided with this watch.HR came through solid and clean but RD would cut out when hand was moved back and would not even reconnect when brought back front. And would still cut out even when kept in "range". The stated 3m range clearly seems not to apply with the F5 (well for running dynamics anyway).

I believe running dynamics uses a separate channel than HR and not even possible to connect separately. Only way to know it's not working is that you lose all the RD related screens until it connects back again.

Not going to change the watch (might get a worse watch in change) as GPS works great, and also phone connection and other sensors is satisfactory. Only problems so far with HRM-RUN and an old MIO BT optical HR band, which I don't really need since the watch has built in optical.

It is a bit bummer as I was hoping to test out the new running power feature. I already have Stryd which works fine, so not really a problem for me, but still this is not good news for F5 owners wanting to use the feature. Will test the RD pod and see if it's any better.

Good news (if can be called that) is that running power apparently works even when RD data cuts out, but will rely on speed / altimeter data as the vertical / horizontal components are left out of the calculation, probably last known value is used. This might affect the data to some extent, although largely seemed to still work ok for pacing.

I've already exchanged my HRM-RUN (it's going back to Garmin) for the RD pod. So far only tested pairing it, but it's immediately obvious it works much better. Even without removing from the package I could pair it and register RD values by waving the package behind my back and at other hand arm extended away from the watch.

Will update here after more testing.

Garmin replace for me f5 with hrm Tri , footpod,Tempe . New battery and still disconnect .
what you suggest again complain to Garmin ?