Virtual Run with F6S Pro - How close should receiver be?

My wife and I tried to pair Zwift with the F6S. We noticed that the Receiver, a Laptop with internal Bluetooth has to be quite near for Zwift to recognise it. Just half a meter, otherwise a connection is not possible. Is the Fenix the culprit of this issue or is it the internal Bluetooth of the Laptop? I guess this should work across a few meters without interruptions.

  • A way to test the range of Bluetooth on your Fenix to help rule it out at a suspect, would be to go to Phone > Alerts > and toggle to On. Then walk slowly away from your smartphone and when your watch loses Bluetooth connection, you will be alerted to your watch.

    You will most likely choose to then turn the feature off again since each and every single time your watch is outside of range of your phone or when your phone will constantly do its own things to conserve battery, you will receive an endless stream of "Connected" and "Disconnect" messages all day long to your watch.

  • Thank you Chris, we tried this and didn't receive a disconnected message on the watch, even through walls. A Bluetooth Mouse connected to the same Receiver works across the room 6-8 meters without issues. Even with that mouse turned off and just have the fenix connected to it doesn't work. We tried to get rid of all distortion signals as well, since they might interfere. Hard to tell what is causing this, since other devices work with that receiver in longer ranges.

    Which Bluetooth version is installed at the F6? The Receiver seems to be v4.0, so it is not that old, but will check again.

  • Most wearables have pretty aggressive power management on bluetooth, which cuts range. Although half a meter sounds pretty low.

    I am wondering about the internal layout of your laptop, and whether the BT receiver is somehow shielded. Does turning the laptop around improve things?

    Also, BT signals don't really go through the body, so can you have the laptop the same side as your watch?

    If repositioning the laptop isn't feasible, can you run the bluetooth connection through the Zwift companion app on your phone?

  • Thank you for your input. The Receiver has Antennas which are build inside the backcover of the screen. (Lenovo T530) Bluetooth Verion on the Laptop is LMP 6 = Bluetooth 4.0

    I also tried to open the lid and move the laptop around. Zwift shows how good the connection is to the watch with four bars. The seem to flicker somehow. One way they show all 4 bars, then next second only 2 or 1 or even nothing, then back to 3 bars again and so on (1meter away) Moving the laptop  nearer somehow improves this a bit, but even then the bars flicker a lot.

    The watch never looses the connection to the paired phone, even when te phone is 5times the distance away than the laptop. so I'm beginning to assume the receiver has an issue somehow.

  • @Garmin-Chris To test whether it is the bluetooth on the watch or the Laptop, we used a different device and tried to pair the watch with Zwift on the iPad. But we encounter the same issue. Flickering bars and barely a connection. The bars change every second from full connection to none, 2 bars, or 1 bar, and sometimes no connection at all and then full bars again and so on. So it seems that it is the watch for some kind of reason.

    This is kind of interesting, since the Connection from the watch to the mobile phone with CGM (Android) is rock stable, there never is a connection loss at all, even with a large distance. We could only provoke a connection loss if we have thick walls in between the mobile phone and the watch, which is normal.

  • The current Bluetooth version you should see in your System > About menu is version 6.11.

  • Thank you, but this is the firmware version of the Bluetooth module. This is on v6.11. What I was looking for is the Bluetooth version of the hardware itself. E.g. If the chip inside F6 is Bluetooth v4.2, there is no need to buy a Bluetooth v5.1 adapter since the fenix doesn't support the higher features by hardware.