This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Garmin Speed Sensor pairing spam on iPhone during Edge 1040 rides

Strivike
2 months ago

Hello,

I'm experiencing a recurring issue when cycling with my Garmin Edge 1040 and a Garmin Speed Sensor (v2). If I open the Garmin Connect app on my iPhone during a ride, I start receiving a cascade of Bluetooth pairing requests from the speed sensor. These appear continuously—dozens per minute—making the phone nearly unusable. If I accept one, the Edge 1040 starts acting as if I've stopped moving, even though I'm still riding.

The only workaround is to "Forget Device" on the iPhone, but of course, the same problem returns later. The issue has been happening intermittently since 2022. At one point, the phone even started logging duplicate or partial ride activities, seemingly on its own.

All devices are fully updated: iPhone, Garmin Connect app, Edge 1040, and the speed sensor firmware.

This screenshot illustrates how repeated Bluetooth pairing prompts from the Garmin Speed Sensor prevent any normal interaction with the iPhone.

Please advise if there’s a fix or a way to permanently prevent the phone from interfering with the sensor during active Edge rides.

Thank you,

  • 0 1 month ago in reply to Strivike

    Update: Possible workaround:
    I’ve found that removing the Speed Sensor from the Garmin Connect app's "Garmin Devices" section (not just forgetting it in iOS Bluetooth settings) completely stops the pairing spam during rides.

  • 0 1 month ago in reply to Strivike

    Update: the sensors are fighting back.

      After 6 days of peace, the ecosystem has found a new way to torment me: this time it's the Cadence Sensor spamming Bluetooth pairing dialogs on the iPhone.

    And here’s the twist: it doesn’t even show up under Garmin Connect > Devices, making it even sneakier than the Speed Sensor.
    creenshot of Bluetooth pairing spam on iPhone from Garmin Cadence Sensor
    So the previous workaround; removing the sensor from the app; doesn’t apply here.

    I’m starting to suspect the machine uprising has begun — and it's targeting cyclists first.