Having trouble pairing your NOWATCH with the app for the first time despite meeting all pairing requirements? Follow these troubleshooting steps to get started with the app.
First-time pairing: Troubleshooting steps
Follow these troubleshooting steps only if you have met all initial requirements and are trying to connect your watch and phone for the first time.
Watch on charger
Keep your watch on the charger throughout the entire pairing process.
Pair via the app
During onboarding, the app will prompt you to enable Bluetooth and pair your watch. Follow the in-app instructions to complete this step.
Toggle Bluetooth off and on
If you've completed onboarding without success, try this next:
- Toggle Bluetooth off and, after a few seconds, turn it back on.
- Try pairing through the app again by tapping Device Details (watch icon at the top right of the Now tab)
Forget the device from Bluetooth
- Open your phone's Bluetooth settings and check if you see your NOWATCH serial number.
- If you do, forget the device from Bluetooth.
- Keep the watch on the charger.
- Try pairing through the Device Details screen within the NOWATCH app again.
Force-close the app
Reopen the app.
Keep the watch on the charger.
Restart the pairing process by following the in-app instructions.
If you don't see the pairing screen, tap Device Details (watch icon at the top right) and then Connect.
Android only: Confirm the pairing pop-up
If you own an Android device and are trying to pair your NOWATCH for the first time, your phone will display a system pop-up requesting permission to pair. Make sure to confirm it. Dismissing or ignoring it can cause unexpected behaviour during the pairing process.
If this happens, we recommend forgetting the device from your Bluetooth settings and pairing again via the NOWATCH app.
If, after connecting, you notice that no data is being recorded within a few minutes, check whether the sensors on the back of the device are lighting up while you’re wearing it. If the sensors are not activating, performing a quick reboot should resolve the issue.
Comments
0 comments
Please sign in to leave a comment.