If your Fitbit notifications are not working, you may miss incoming calls, text messages, calendar reminders, WhatsApp alerts, emails, or other app notifications on your wrist. In many cases, the Fitbit itself is not the real problem. The issue can come from Bluetooth, phone notification permissions, Do Not Disturb or Focus modes, background app restrictions, or a broken connection between your phone and Fitbit.

Fitbit devices can mirror notifications from a nearby phone, including calls, texts, calendar events, and supported app notifications. Google’s current Health Help Center recommends checking the phone, Bluetooth connection, notification permissions, Fitbit settings, and app connection before moving to more advanced troubleshooting.

The good news is that you usually do not need to factory-reset your Fitbit.

This guide walks through the most useful fixes in order, starting with the quickest checks and progressing to reconnecting your Fitbit if necessary.

Quick Answer: Why Are Fitbit Notifications Not Working?

Your Fitbit notifications may stop working because:

Bluetooth is disconnected or unstable.
Your phone is too far away from the Fitbit.
Notifications are disabled on your phone.
The Fitbit does not have permission to access phone notifications.
Do Not Disturb, Focus, Sleep, Quiet Hours, or Driving Mode is active.
The Fitbit itself has Do Not Disturb or Sleep Mode enabled.
The Fitbit app or Google Health app cannot run properly in the background.
Your phone recently received an operating-system or app update.
The Fitbit is still syncing.
Notification settings for a particular app have changed.
iPhone’s Share System Notifications setting is disabled.
The Bluetooth pairing between your phone and Fitbit needs to be refreshed.

Google states that the phone generally needs to remain within about 30 feet (10 meters) of the Fitbit for notifications to arrive. Text notifications can also behave differently when the conversation is already open on the phone.

Before You Start: Identify What Is Actually Broken

Before changing several settings at once, test the problem.

Ask yourself:

Are all Fitbit notifications missing, or only one type?

For example:

Calls work, but texts do not.
Texts work, but WhatsApp notifications do not.
Notifications arrive but there is no vibration.
Notifications appear several minutes late.
Notifications stopped after switching to Google Health.
Notifications work when the phone is unlocked but not when it is locked.
Nothing appears on the Fitbit at all.

This distinction matters because a Fitbit that receives calls but not text messages may have a different problem from a Fitbit that has completely lost its phone connection.

A recent Google Health Community report, for example, described a user receiving calls and other alerts while text notifications stopped working. A Google Health Community specialist recommended checking message previews and the notification settings for the messaging app.

So don’t immediately reset the entire device. First determine whether the failure affects all notifications or only a particular notification category.

1. Check Bluetooth First

Bluetooth is the communication bridge between your phone and Fitbit for phone notifications.

If Bluetooth has disconnected, notifications cannot reliably reach your Fitbit even if everything else is configured correctly.

On Android

Open your phone’s Bluetooth settings and confirm that Bluetooth is switched on.

Then check whether your Fitbit appears as a connected or recognized device.

After confirming Bluetooth is enabled:

Keep your Fitbit close to your phone.
Open the Google Health app.
Allow the app to sync with your Fitbit.
Test a notification.

Google specifically recommends checking Bluetooth when Fitbit notifications are delayed or missing. It also notes that having multiple Bluetooth devices connected can sometimes create connection problems.

On iPhone

Go to:

Settings → Bluetooth

Make sure Bluetooth is enabled and locate your Fitbit in the device list.

If the Fitbit appears connected but notifications still don’t arrive, don’t immediately remove the device. Continue through the notification settings below first.

A simple Bluetooth refresh

If Bluetooth appears normal but notifications remain broken:

Turn Bluetooth off.
Wait about 10 seconds.
Turn Bluetooth back on.
Open the Google Health app.
Let the Fitbit sync.
Test a call or message notification.

This is one of Google’s recommended troubleshooting steps for missing Fitbit notifications.

2. Make Sure Your Phone Is Actually Receiving the Notification

Your Fitbit generally mirrors notifications that your phone itself receives.

That means you should first check whether the notification appears on the phone.

For example, if WhatsApp notifications are disabled on your phone, your Fitbit cannot simply recreate those alerts independently.

Check the problematic app directly.

Test this

Send yourself a message or ask someone to send you one.

Then check:

Does the notification appear on your phone?

If the answer is no, fix the phone’s notification settings before changing Fitbit settings.

If the answer is yes, but the notification does not reach your Fitbit, the problem is more likely related to Fitbit permissions, Bluetooth, notification setup, or background operation.

Google’s current Fitbit notification instructions specifically state that the phone must receive phone, text, calendar, and app notifications for those alerts to be delivered to the Fitbit.

3. Turn Off Do Not Disturb, Focus and Similar Modes

This is one of the easiest things to overlook.

Your phone may be connected to the Fitbit perfectly while a system mode silently prevents notifications from appearing.

Check whether any of these are active:

Do Not Disturb
Focus
Sleep mode
Quiet Hours
Driving Mode
Other notification-blocking modes

Google specifically lists Focus, Do Not Disturb, Quiet Hours, and Driving Mode among settings that can prevent phone notifications from reaching a Fitbit.

Also check the Fitbit itself

Your phone isn’t the only place where notification-blocking modes can be enabled.

If Do Not Disturb or Sleep Mode is active directly on your Fitbit, the device may receive notifications without alerting you normally.

So check both sides:

Phone → notification-blocking modes

Fitbit → Do Not Disturb / Sleep Mode

If either side is blocking alerts, turn the mode off temporarily and test again.

4. Keep Your Fitbit Close to Your Phone

Fitbit phone notifications aren’t designed to work from unlimited distances.

Google currently recommends keeping the Fitbit within approximately 30 feet (10 meters) of the phone for notifications.

This becomes especially important when:

You’re in another room.
Your phone is upstairs while you’re exercising downstairs.
Your phone is inside a bag or locker.
You have thick walls or other obstacles between the devices.
Bluetooth is already struggling with several connected devices.

For a quick test, put the Fitbit directly beside your phone.

Then send yourself a test notification.

If notifications suddenly start working, distance or Bluetooth stability may have been the problem.

5. Check Fitbit Notification Settings

If Bluetooth works and your phone receives notifications, the next step is checking the notification configuration inside the Fitbit/Google Health app.

In the current Google Health app, the general path is:

Open Google Health → Connections → Your Fitbit → Notifications

From there, review which notification categories are enabled.

Depending on your Fitbit and phone, you may be able to configure:

Calls
Text messages
Calendar events
App notifications

Google’s current instructions also allow users to select which apps provide notifications for supported categories.

Make sure the notification type you’re testing is actually enabled.

For example, if calls are enabled but text messages are disabled, receiving incoming calls on your Fitbit does not prove that SMS notifications are configured correctly.

6. Check the Problem App’s Notification Permission

If only one app is failing, focus on that app rather than changing every Fitbit setting.

Suppose:

Phone calls work.
SMS works.
Gmail works.
WhatsApp does not.

That points toward WhatsApp’s phone notification settings or its Fitbit notification permission rather than a complete Fitbit connection failure.

On your phone, open the app’s notification settings and verify that notifications are allowed.

Also make sure notifications can appear when the phone is locked.

Google’s current guidance specifically recommends checking whether notifications appear on the phone’s lock screen and whether the relevant app is actually permitted to send notifications.

This is particularly important if your Fitbit stopped showing notifications after you changed privacy, lock-screen, or notification settings.

Part 1 Takeaway

Before attempting anything drastic, check these six areas:

Bluetooth
Phone notifications
Do Not Disturb / Focus
Distance from your phone
Fitbit notification settings
The individual app’s notification permission

If your Fitbit still isn’t showing notifications after these checks, the next fixes involve background permissions, Android-specific settings, iPhone Share System Notifications, restarting the Fitbit, refreshing notification configuration, and finally re-pairing the device.

7. Give Fitbit or Google Health Permission to Run in the Background

One of the most overlooked reasons Fitbit notifications are not working is restricted background activity.

Your Fitbit needs the companion app to maintain communication with the phone. If Android aggressively puts the app to sleep, notification delivery can become unreliable.

This can happen after:

A phone software update
A battery optimization change
Installing a new battery-saving app
Changing background-data permissions
Manually restricting the Fitbit or Google Health app
Leaving the app unused for a long period

What to check on Android

Open your phone’s app settings and locate the Fitbit or Google Health app.

Look for settings related to:

Battery usage
Background activity
Background data
Unrestricted battery usage
Auto-start
App sleeping

The exact menu names vary by Android manufacturer, so don’t worry if your phone doesn’t use exactly the same wording.

The important point is to prevent your Fitbit companion app from being aggressively restricted while you’re troubleshooting.

After changing the setting, open the app again and allow it to reconnect with your Fitbit.

Then test a notification.

Why this matters

A Fitbit can appear connected while the companion app is being restricted in the background.

That’s why simply looking at the Bluetooth screen isn’t always enough to diagnose notification problems.

8. Check Notification Permissions on Android

Android gives individual apps control over notification access.

If notification permission has been disabled, the Fitbit may not receive alerts from that application.

Go to your phone’s:

Settings → Apps → [Problem App] → Notifications

Make sure notifications are enabled.

Then check the Fitbit or Google Health app’s relevant permissions as well.

If you’re troubleshooting WhatsApp, for example, don’t only check Fitbit. Confirm that WhatsApp itself is allowed to display notifications.

Check lock-screen notifications too

Some phones have separate controls for whether notifications appear when the phone is locked.

If your phone receives a notification only after you unlock it, your Fitbit experience may also be affected.

For testing, temporarily allow the notification to appear normally on the phone’s lock screen.

Then send another test message.

9. iPhone Users: Check “Share System Notifications”

If you’re using an iPhone, there is an important setting that can be easy to miss.

For supported Fitbit notification features, iPhone system notification sharing needs to be enabled.

Go to:

Settings → Bluetooth → your Fitbit → Share System Notifications

Make sure Share System Notifications is enabled if that option is available for your device.

Google’s Fitbit notification guidance specifically identifies this setting when troubleshooting notifications on iPhone. (support.google.com)

Also check the individual app

If calls appear but messages don’t, open the notification settings for your messaging app.

Make sure:

Notifications are enabled.
Lock-screen notifications are enabled where appropriate.
Notification previews aren’t being blocked in a way that prevents the Fitbit from receiving the alert.

This distinction is important because iPhone notification privacy settings can affect what information is available to connected devices.

10. Restart Your Fitbit

If your settings appear correct but notifications suddenly stopped, restart the Fitbit.

A restart can clear a temporary software or connection problem without deleting your personal data.

The exact restart procedure depends on your Fitbit model.

Before restarting:

Keep your phone nearby.
Make sure Bluetooth is enabled.
Close unnecessary Bluetooth connections if possible.
Restart the Fitbit according to its model-specific procedure.
Wait for the device to start completely.
Open Google Health.
Allow the Fitbit to reconnect and sync.
Test a notification.

A restart is especially worth trying when notifications worked previously and stopped unexpectedly.

11. Refresh the Notification Connection

Sometimes the Fitbit remains connected for syncing and activity tracking while the notification connection has become unreliable.

In that situation, refreshing the notification setup can help.

Start with the least disruptive option.

Step 1: Open Google Health

Open the companion app and select your connected Fitbit.

Step 2: Open notification settings

Review the enabled notification categories.

Step 3: Temporarily disable the affected notification

For example, if text notifications are failing, turn the text notification setting off.

Wait briefly.

Step 4: Enable it again

Turn the notification category back on.

Step 5: Sync

Allow the Fitbit to reconnect and synchronize.

Step 6: Test

Send yourself a new message rather than testing with an old notification.

This effectively forces you to test the current notification configuration rather than assuming the previous connection is still valid.

12. Remove and Re-Pair the Fitbit Only as a Last Resort

If none of the earlier solutions work, you may need to refresh the Bluetooth pairing.

This should not be your first troubleshooting step.

Before removing the Fitbit, make sure your recent Fitbit data has synchronized successfully.

Then follow the current Google Health/Fitbit pairing instructions for your specific device.

A clean reconnection can resolve problems caused by a damaged or inconsistent Bluetooth pairing.

Why you shouldn’t start here

Re-pairing creates additional variables.

If you immediately remove the Fitbit, you won’t know whether the actual problem was:

A disabled notification permission
Do Not Disturb
Battery restrictions
A single app
Bluetooth
iPhone system notification sharing

Working through the simpler causes first gives you a much clearer diagnosis.

Fitbit Notifications Still Not Working? Use This Diagnostic Test

If you’re still stuck, don’t randomly change settings.

Run a controlled test.

Test 1 — Phone notification

Send yourself a text message.

Does it appear on the phone?

No: The phone’s notification settings are the likely problem.
Yes: Continue.

Test 2 — Fitbit connection

Open Google Health and check whether the Fitbit is connected and syncing.

No: Focus on Bluetooth and connection troubleshooting.
Yes: Continue.

Test 3 — Fitbit notification

Send another test message.

Phone receives it, Fitbit doesn’t: Focus on Fitbit notification permissions and notification configuration.
Fitbit receives it but doesn’t vibrate: Check Fitbit notification behavior, Do Not Disturb, Sleep Mode, and related device settings.

Test 4 — Different app

Try another notification, such as an incoming call or calendar alert.

If calls work but WhatsApp doesn’t, the problem probably isn’t the entire Fitbit connection.

It’s more likely related to the specific application’s notification permission or configuration.

Why Fitbit Notifications May Be Delayed

Not every notification problem means notifications are completely broken.

Sometimes they arrive several seconds or minutes late.

Possible causes include:

Weak Bluetooth connection
Phone distance
Background app restrictions
Battery-saving settings
Temporary Bluetooth instability
Phone notification delays
Too many connected Bluetooth devices

Google recommends keeping the Fitbit within approximately 30 feet (10 meters) of the phone and checking Bluetooth when notifications are delayed or missing. (support.google.com)

For a reliable test, put the Fitbit and phone next to each other.

Then send three separate notifications.

If all three arrive promptly, the problem may be connection stability rather than the Fitbit notification feature itself.

Why Fitbit Shows Calls but Not Texts

This is a particularly useful troubleshooting clue.

If incoming calls appear on your Fitbit but text messages don’t, your Fitbit is probably still communicating with the phone.

That means you shouldn’t immediately assume the Bluetooth connection is completely broken.

Instead, check:

Text-message notification permission.
Messaging-app notification settings.
Lock-screen notification settings.
Fitbit’s text notification setting.
Message preview/privacy settings.
Whether the messaging conversation is already open on the phone.

Google’s current troubleshooting documentation specifically notes that text notifications can behave differently depending on the state of the conversation on the phone. (support.google.com)

This is why testing different notification types is much more useful than simply saying, “My Fitbit notifications don’t work.”

Why Fitbit Notifications Work Sometimes but Not Always

Intermittent notification problems are often harder to diagnose.

Your Fitbit might work perfectly at home but stop receiving notifications when you’re at work or exercising.

In that case, investigate environmental and phone-related factors.

Check the distance

Keep your Fitbit within the recommended Bluetooth range.

Check battery optimization

Make sure the companion app isn’t being restricted when the phone’s screen is off.

Check Focus and Do Not Disturb

A scheduled Focus or DND mode may activate automatically at certain times.

Check Bluetooth

Other connected devices can sometimes complicate Bluetooth behavior.

Check after phone updates

If the problem began immediately after an Android or iOS update, review the notification and Bluetooth permissions again.

What Not to Do When Fitbit Notifications Stop Working

Troubleshooting can become unnecessarily complicated when you change several things at once.

Avoid these mistakes:

Don’t factory-reset immediately

A factory reset is a major step and is rarely the logical first response to missing phone notifications.

Don’t delete every Bluetooth device

Start with the Fitbit connection and identify the actual problem.

Don’t assume the Fitbit is defective

A notification failure can originate entirely on the phone.

Don’t ignore phone notification settings

Your Fitbit depends on the phone’s notification system for many mirrored alerts.

Don’t test only one notification type

Test calls, messages, and another supported app when possible.

Don’t overlook Focus or Do Not Disturb

Scheduled modes can make a perfectly functioning Fitbit appear broken.

The Fastest Fix Order

If you don’t want to work through every section individually, use this order:

1. Keep the Fitbit close to your phone.

2. Confirm Bluetooth is enabled.

3. Confirm the phone receives the notification.

4. Turn off Do Not Disturb/Focus temporarily.

5. Check Fitbit notification settings.

6. Check the individual app’s notification permission.

7. Check background/battery permissions.

8. iPhone users: check Share System Notifications.

9. Restart the Fitbit and phone.

10. Refresh notification settings.

11. Re-pair the Fitbit if necessary.

This order starts with the simplest and least disruptive solutions and leaves reconnection as the final major troubleshooting step.

Final Takeaway

When Fitbit notifications are not working, the problem isn’t necessarily the Fitbit itself.

In most cases, you should investigate the complete connection chain:

Phone notification → Phone permissions → Bluetooth → Google Health/Fitbit connection → Fitbit notification settings → Fitbit alert behavior

Testing each stage separately makes it much easier to identify where the failure occurs.

If calls work but texts don’t, investigate messaging permissions. If no notifications work, start with Bluetooth, phone notification permissions, Do Not Disturb, and the Fitbit connection. If notifications work only intermittently, pay particular attention to Bluetooth distance, background activity, and battery restrictions.

And before deleting or resetting anything, make sure your Fitbit has successfully synchronized your recent data.

Frequently Asked Questions

Why are my Fitbit notifications not working?

Common causes include Bluetooth problems, disabled phone notifications, Do Not Disturb or Focus modes, restricted background activity, incorrect Fitbit notification settings, and problems with the individual app sending the notification. (support.google.com)

Why does my Fitbit get calls but not texts?

Calls and text notifications can have separate settings. Check your messaging app’s notification permissions, Fitbit text notification settings, lock-screen notifications, and message-preview settings.

Why does my Fitbit stop showing notifications when my phone is locked?

Check whether notifications are allowed on the phone’s lock screen and whether battery or background restrictions are preventing the Fitbit companion app from operating normally.

Do I need Bluetooth for Fitbit notifications?

For phone-based Fitbit notifications, Bluetooth communication between the phone and Fitbit is important. Keep the devices within the recommended range and verify that Bluetooth is enabled. (support.google.com)

Why does my Fitbit vibrate but show no notification?

Check the Fitbit’s notification behavior and the phone’s notification privacy settings. The phone may be sending an alert while restricting the amount of notification content available to the connected Fitbit.

Should I factory-reset my Fitbit if notifications don’t work?

No. A factory reset should generally be considered only after simpler troubleshooting has failed. Start with Bluetooth, notification permissions, Focus/DND settings, background permissions, and notification configuration.

Why aren’t WhatsApp notifications showing on my Fitbit?

First confirm WhatsApp notifications are working normally on your phone. Then verify WhatsApp is permitted in the Fitbit notification settings and that phone notification permissions haven’t been restricted.

Can a phone update break Fitbit notifications?

Yes. A system or app update can change notification permissions, Bluetooth behavior, background activity, or battery settings. If notifications stopped immediately after an update, review those settings first.

Why Are Fitbit Notifications Not Working?

Fitbit phone notifications depend on several parts of the phone-and-Fitbit connection working together.

A notification can fail at different points.

For example:

App → Phone notification system → Bluetooth → Google Health/Fitbit connection → Fitbit → Wrist alert

If an app is not allowed to send notifications, your Fitbit cannot display that alert.

If the phone receives the alert but Bluetooth is disconnected, the Fitbit may not receive it.

If Bluetooth is working but Do Not Disturb is enabled, the notification may be suppressed.

This is why troubleshooting should happen in a logical order rather than immediately resetting the Fitbit.

Google’s current troubleshooting guidance recommends checking Bluetooth, notification settings, Do Not Disturb/Focus-related settings, distance between the phone and Fitbit, and notification configuration.

1. Check Bluetooth First

Bluetooth is one of the first things to investigate when Fitbit notifications suddenly stop.

Open your phone’s Bluetooth settings and confirm Bluetooth is enabled.

Keep the Fitbit close to your phone and open Google Health so the device can reconnect and synchronize.

If Bluetooth appears connected but notifications are still missing, try:

Turn Bluetooth off.
Wait approximately 10 seconds.
Turn Bluetooth back on.
Open Google Health.
Allow the Fitbit to reconnect.
Send yourself a test notification.

Google recommends checking Bluetooth when Fitbit notifications are missing or delayed. It also notes that multiple Bluetooth connections can sometimes complicate connectivity.

2. Confirm Your Phone Receives the Notification

Before blaming the Fitbit, check your phone.

Send yourself a text message or trigger a notification from the app you’re testing.

If the notification doesn’t appear on the phone, fix the phone notification settings first.

If it does appear on the phone but not the Fitbit, continue troubleshooting the Fitbit connection and notification permissions.

This simple test can immediately tell you which side of the connection is causing the problem.

3. Turn Off Do Not Disturb or Focus

Check your phone for:

Do Not Disturb
Focus
Sleep modes
Quiet Hours
Driving modes
Other notification-blocking features

These settings can prevent alerts from being delivered normally.

Also check whether Do Not Disturb or Sleep Mode is active directly on the Fitbit.

For troubleshooting, temporarily disable these modes and test again.

If notifications immediately return, you have identified the cause without needing to reset or re-pair the Fitbit.

4. Keep Your Fitbit Close to Your Phone

Your Fitbit isn’t designed to receive phone notifications from unlimited distances.

Google recommends keeping the Fitbit within approximately 30 feet (10 meters) of the phone.

For a quick diagnostic test, place your Fitbit next to your phone.

Then:

Send a text.
Make a test call.
Trigger a notification from another app.

If notifications work reliably at close range but fail when you move farther away, Bluetooth range or connection stability may be contributing to the problem.

5. Check Fitbit Notification Settings

Open Google Health and select your connected Fitbit.

Review the available notification settings.

Depending on the Fitbit model and phone, notification categories may include:

Phone calls
Text messages
Calendar events
App notifications

Make sure the category you’re testing is enabled.

If calls work but text messages don’t, don’t assume the entire notification system is broken.

Instead, concentrate on the text-message settings.

6. Check the Problem App’s Notification Permissions

If only one application is failing, investigate that application first.

For example:

Calls → Working

SMS → Working

Gmail → Working

WhatsApp → Not working

That pattern suggests WhatsApp’s notification settings may be responsible.

Open the phone’s app notification settings and verify:

Notifications are enabled.
Lock-screen notifications are allowed where appropriate.
The app isn’t being restricted by a notification-blocking setting.
The app is permitted to run normally in the background.

Then check whether that app is enabled in the Fitbit notification configuration.

7. Check Background and Battery Restrictions

Android phones can restrict background activity to improve battery life.

If Google Health or the Fitbit companion software is heavily restricted, communication with the Fitbit can become unreliable.

Review the app’s:

Battery usage
Background activity
Background data
Battery optimization
Auto-start settings where applicable

The exact location varies between Android manufacturers.

The objective is simple: make sure the Fitbit companion app isn’t being aggressively stopped when you’re not actively using it.

This is particularly worth checking if notifications work while the phone is being actively used but fail after the screen has been off for a while.

8. iPhone Users: Check Share System Notifications

iPhone users have an additional setting worth checking.

Open:

Settings → Bluetooth → Your Fitbit

Look for:

Share System Notifications

If the option is available, make sure it is enabled.

Also review notification permissions for the individual application you’re testing.

If the phone is receiving the notification but the Fitbit isn’t, this setting can be an important part of the troubleshooting process.

9. Restart the Fitbit

If everything appears correctly configured, restart the Fitbit.

A restart is considerably less disruptive than a factory reset.

After restarting:

Keep your phone nearby.
Confirm Bluetooth is enabled.
Open Google Health.
Wait for the Fitbit to reconnect.
Allow synchronization to finish.
Send a new test notification.

This is particularly useful when notifications worked normally and then suddenly stopped.

10. Refresh Notification Configuration

If notifications remain broken, refresh the affected notification category.

For example, if text notifications aren’t arriving:

Open the Fitbit notification settings.
Disable text notifications.
Wait briefly.
Enable text notifications again.
Allow the Fitbit to synchronize.
Send a completely new test message.

This gives the notification configuration a chance to reinitialize without requiring a full Bluetooth reset.

11. Re-Pair Your Fitbit

Re-pairing should be considered a later troubleshooting step.

Before doing this, make sure your Fitbit has synchronized your recent activity.

Then follow the current pairing procedure for your specific Fitbit model.

A fresh Bluetooth pairing can resolve problems caused by a corrupted or inconsistent connection.

However, don’t jump directly to re-pairing.

If a simple notification permission is the problem, re-pairing adds unnecessary complexity without fixing the underlying cause.

Fitbit Notifications Not Working: Diagnostic Checklist

Use this quick checklist before making major changes.

Test	Result	What to Investigate
Phone receives notification	No	Phone notification settings
Phone receives notification	Yes	Continue
Fitbit connected	No	Bluetooth/connection
Fitbit connected	Yes	Notification configuration
Calls work	Yes	Text/app settings
Calls work	No	General notification connection
Notifications work nearby	Yes	Bluetooth range/stability
Notifications work after restart	Yes	Temporary connection issue
Only one app fails	Yes	App notification permissions
iPhone notifications fail	Yes	Share System Notifications

Why Does My Fitbit Get Calls but Not Texts?

This is one of the most useful clues.

If calls reach your Fitbit but texts don’t, the Fitbit is communicating with your phone in at least some capacity.

Instead of immediately resetting it, check:

Text notification settings.
Messaging app permissions.
Lock-screen notification settings.
Message-preview settings.
Fitbit text notification configuration.
Whether the messaging conversation is already open on your phone.

The important lesson is that one working notification type doesn’t automatically mean every notification category is configured correctly.

Why Are Fitbit Notifications Delayed?

Delayed notifications can have different causes from completely missing notifications.

Start by checking:

Bluetooth stability
Phone-to-Fitbit distance
Background activity
Battery optimization
Focus/DND modes
Phone notification delays
Other Bluetooth connections

For testing, put the Fitbit and phone close together and send several notifications.

If they arrive quickly when the devices are close, connection stability may be the issue.

Why Do Fitbit Notifications Work Sometimes?

Intermittent notifications can be caused by settings that change automatically.

For example, your phone might activate Focus or battery-saving restrictions at a particular time.

You might also move beyond a reliable Bluetooth range while exercising.

Check whether the problem occurs:

At a particular time of day
Only when the phone screen is off
Only at work or outside your home
Only with one application
After a phone update
After switching to another Bluetooth device

Finding the pattern can be more useful than repeatedly reconnecting the Fitbit.

Should You Factory Reset a Fitbit for Notification Problems?

Usually, no—not as your first step.

A factory reset is a much more disruptive solution than checking Bluetooth and notification permissions.

Start with:

Bluetooth
Phone notification permissions
Do Not Disturb/Focus
Fitbit notification settings
Individual app permissions
Background/battery restrictions
Restart
Notification configuration refresh
Re-pairing

Only consider more drastic measures after these steps have failed.

Expert Troubleshooting Tip

The fastest way to troubleshoot a Fitbit notification problem is to change only one variable at a time.

For example, don’t simultaneously:

Reset Bluetooth
Delete the Fitbit
Reinstall Google Health
Disable every battery setting
Reset the Fitbit

If notifications suddenly start working, you won’t know which change fixed the problem.

Instead, run a controlled test.

Phone receives alert → Fitbit connected → notification enabled → test again.

That approach makes the troubleshooting process much easier to repeat if the problem returns.

Frequently Asked Questions

Why are my Fitbit notifications not working?

Common causes include Bluetooth problems, disabled phone notifications, Focus or Do Not Disturb, incorrect Fitbit notification settings, background restrictions, and individual app permissions.

Why does my Fitbit get calls but not texts?

Calls and texts can have separate notification settings. Check your messaging app’s phone permissions and the Fitbit’s text notification configuration.

Why isn’t WhatsApp showing on my Fitbit?

First confirm WhatsApp notifications appear normally on your phone. Then check WhatsApp’s notification permissions and whether WhatsApp is enabled in your Fitbit notification settings.

Why does my Fitbit stop receiving notifications when my phone is locked?

Review lock-screen notification permissions and background/battery restrictions for the Fitbit companion app. If the problem occurs only when the phone is locked, background operation is particularly worth investigating.

How far can my phone be from my Fitbit for notifications?

Google’s current guidance recommends keeping the Fitbit within approximately 30 feet (10 meters) of the phone for phone notifications.

Does Do Not Disturb affect Fitbit notifications?

Yes. Phone-level Focus or Do Not Disturb modes can prevent notifications from being delivered normally. Also check notification-blocking modes directly on the Fitbit.

Do iPhone users need to enable Share System Notifications?

For supported Fitbit notification functionality, iPhone users should check Share System Notifications under the Fitbit’s Bluetooth settings.

Should I restart my Fitbit if notifications suddenly stop?

Yes. Restarting is a reasonable low-risk troubleshooting step when notifications previously worked and suddenly stopped.

Should I remove my Fitbit from Bluetooth?

Only after simpler troubleshooting has failed. Make sure recent Fitbit data has synchronized before attempting a fresh pairing.

Final Takeaway

When Fitbit notifications are not working, don’t assume the Fitbit hardware is defective.

Start at the beginning of the notification chain:

Phone notification → Notification permission → Bluetooth → Google Health/Fitbit connection → Fitbit notification setting → Wrist alert

Test each stage separately.

For most problems, the best first checks are Bluetooth, phone notifications, Focus or Do Not Disturb, notification permissions, and the distance between the phone and Fitbit.

If the problem affects only one application, investigate that app instead of resetting the entire Fitbit. Android users should also review background and battery restrictions, while iPhone users should check Share System Notifications.

And if everything else fails, restart the device and consider re-pairing it before taking more drastic action.

The goal isn’t simply to make notifications work once. It’s to identify why they stopped working, so you can prevent the same problem from returning.