“Device Not Found”: Troubleshooting Initial Pairing for New Smartwatches

Seeing “Device Not Found” when setting up a brand-new smartwatch means your phone’s companion app cannot detect the watch’s Bluetooth Low Energy (BLE) pairing signal. This usually happens because the watch was paired directly in the phone’s Bluetooth menu first, its battery is too low to broadcast, it timed out of Pairing Mode, or a denied phone permission is blocking discovery.

Quick Answer: How to Fix “Device Not Found” on a New Smartwatch

Never pair a new watch from your phone’s Bluetooth settings—always start inside its official companion app. Charge the watch on its dock, make sure Bluetooth, Location, and Nearby Devices permissions are enabled on your phone, turn off any VPN, and reboot the watch so it re-enters active Pairing Mode.

Device & Signal Snapshot

  • Affected Devices: Apple Watch, Samsung Galaxy Watch, Google Pixel Watch, Garmin, Fitbit, and other BLE wearables
  • Common Causes: Manual pairing in system Bluetooth settings, denied app permissions, timed-out Pairing Mode, low unboxing battery, or OS incompatibility
  • Data Risk: None on a brand-new setup; if setting up an open-box or refurbished watch, clearing prior bonds restores factory pairing

What Is Actually Happening?

When you unbox a new smartwatch and reach the “Welcome” or language screen, the watch turns on a temporary Bluetooth Low Energy advertising beacon. That beacon broadcasts only while the watch sits in active Pairing Mode and disappears the moment the watch connects to anything—including your phone’s regular Bluetooth menu—or goes idle to save power.

On the phone side, your companion app cannot hear that beacon unless the phone grants explicit wireless permissions (Bluetooth, Location, and on Android, Nearby devices). If either side hides or blocks the signal, the scan spins and ends in “Device Not Found.”

What Can Cause “Device Not Found”

  • Manual Bluetooth pairing mistake: Pairing the watch in Settings > Bluetooth before opening the watch app hides the watch from the app’s setup scanner.
  • Denied OS permissions: Tapping “Don’t Allow” on the first Bluetooth, Location, or Nearby Devices prompt makes the app blind to nearby wearables.
  • Timed-out Pairing Mode or drained battery: Watches that sat on a warehouse shelf for months often lack enough power to sustain BLE advertising, or exit Pairing Mode after sitting idle too long.
  • Outdated phone OS or incompatible platform: New watches regularly require up-to-date iOS or Android versions to recognize new hardware IDs. (Also remember: Apple Watch only pairs with iPhones, and modern Wear OS watches like Galaxy Watch 7/8 and Pixel Watch 3/4 require compatible Android phones.)
  • Open-box, returned, or nearby device interference: A refurbished watch may still be locked to a previous owner’s phone bond, or a nearby tablet/old phone may be grabbing its signal.

What to Do: Get Your New Watch Detected

Step 1: Charge the Watch and Undo Any Manual Bluetooth Pairing

  1. Place your new smartwatch on its powered charger for at least 15–20 minutes and keep it inches away from your smartphone during setup.
  2. Open your phone’s Settings > Bluetooth. If you already see the new watch listed under “My Devices” or “Previously connected,” tap Forget This Device / Unpair immediately.
  3. Also turn Bluetooth OFF temporarily on any other phones or tablets sitting in the same room.

Step 2: Check Phone Permissions, VPNs, and OS Updates

  1. On iPhone: Go to Settings > Privacy & Security > Bluetooth and confirm the toggle for your watch’s companion app (Watch, Garmin Connect, Fitbit, etc.) is On. Also turn Location Services ON temporarily for initial setup.
  2. On Android: Open Settings > Apps > [Your Watch App] > Permissions and set Nearby devices and Location to Allow (also make sure global Location is turned on in Quick Settings). If you tapped deny earlier, see The “Bluetooth Permission” Prompt: Why “Don’t Allow” Bricks Your Initial Setup.
  3. Turn off any active VPN or ad-blocker profile, and verify your phone OS and companion app are fully updated—see Why Your New Wearable Won’t Pair Until You Update Your Phone OS.

Step 3: Restart the Watch to Trigger Fresh Pairing Mode

  1. Force a fresh restart on the new watch (or cycle it back to the welcome screen) so it starts broadcasting a new BLE pairing beacon.
  2. Immediately open the official companion app (Apple Watch, Galaxy Wearable, Google Pixel Watch, Garmin Connect, or Fitbit) and start Add Device / Pair right away so the pairing window doesn’t expire. Read Why Your Phone Won’t See Your New Watch (The “Pairing Mode” Timing Trick) if the scan times out quickly.

What to Check If That Doesn’t Work

Toggle Wi-Fi and Clear Bluetooth Cache

Open-Box or Refurbished Watches

If the watch looks already set up (showing an existing watch face instead of a welcome/pairing prompt) or was bought refurbished, it is still paired to a prior phone. Run a full watch-side factory reset first, or follow Troubleshooting Setup Errors for “Refurbished” Devices on Official Apps.

When It’s Actually a Hardware Problem

Exchange the new watch with the retailer or contact the manufacturer if:

  • No pairing screen or radio activity: Even after charging for an hour on a known-good outlet, the watch never turns on or stays stuck with no discoverable Bluetooth signal on two different compatible smartphones.
  • Confirmed compatibility failure: Both phones run the latest iOS/Android and updated companion apps with full permissions granted, yet neither phone can detect the watch while sitting right next to it (while detecting other Bluetooth accessories normally).

Leave your phone’s Bluetooth menu alone—charge the watch, turn on Location and Nearby Devices permissions in the companion app, and reboot the watch right before tapping Pair so you catch its active Pairing Mode beacon.