Skip to content

WHOOP 5.0 on iOS — BLE authentication/encryption failure after re-pairing #633

Open

Description

@soldatovilya

WHOOP 5.0 on iOS — BLE authentication/encryption failure after re-pairing

Device: iPhone 14 Pro, iOS 27.0.1
App: OpenStrap Edge 0.11.3+78
Band: WHOOP 5.0

The band was syncing successfully until October 21, 2026, at 17:57 (MSK). Since then, Edge has been unable to establish a working connection.

iOS reports the WHOOP as connected, and Edge recognizes it as a paired Gen 5 band (Tier 2), but Edge remains “Not connected”.

I have restarted the phone, checked Bluetooth permissions, and forgotten and re-paired the band. The issue persists.

The diagnostic logs repeatedly show:

setNotifyValue | apple-code: 5 | Authentication is insufficient.

setNotifyValue | apple-code: 15 | Encryption is insufficient.

Both occur when registering notifications for cmd_from.

Could you investigate whether this is a BLE bonding/key issue or a Gen 5 authentication issue, and advise on a safe recovery procedure that preserves local data?

I can provide the diagnostic ZIP privately if needed.

Activity

  1. kurexw commented on Nov 15, 2026

    @kurexw
    Contributor

    "Authentication is insufficient" (5) and "Encryption is insufficient" (15) on the first setNotifyValue mean the band is refusing the encryption key iOS still holds for it: usually a stale pairing record on the phone, not a band fault. On iOS that's the only place a rejected key shows up. It's a different problem from the 50.43.x firmware lock in #673, where the band connects and accepts commands but sends no data.

    What has worked for others (see #627):

    1. Remove the band in Edge, then Forget This Device for it in iOS Settings → Bluetooth.
    2. Take the band off your wrist and wait for the green lights to go out.
    3. Hold it by the sides and tap the top firmly with two fingers until only blue flashes (keep tapping if blue and white show together). That puts it in pairing mode.
    4. If the WHOOP app is on the phone, force-quit it.
    5. Pair again in Edge. One reporter needed several tries.

    Edge already recognises this error as a refused pairing and shows these steps. From the next release after 0.11.3 it also puts "forget the band in Bluetooth settings" first, because retrying while iOS still holds the old record keeps failing. If it still fails after a reset, an in-app report (Settings → Report an issue) from right after an attempt would help.

  2. abdulsaheel commented on Nov 17, 2026

    @abdulsaheel
    Collaborator

    that error means the band is refusing the key your phone still holds for it, so it's the old pairing record rather than your data. in 0.12.2 the pairing screen now lists "forget the band in Bluetooth settings" as the first step when it hits this. your local data stays, forgetting only removes the phone's bluetooth record. if you update and it still refuses after forgetting it in iOS settings and pairing again with the band in pairing mode, send a report from the app (settings, report an issue) right after the attempt.

  3. soldatovilya commented on Nov 18, 2026

    @soldatovilya
    Author
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions