Direct answer
For the Fitbit Ace LTE, compatibility, Bluetooth state, app/account, prior phone and reset consequences should be separated. First, update phone/app and place both charged devices nearby.
What this covers
- Fitbit Ace LTE (G4SKY)
- Fitbit device; Google-account migration, onboard GPS, voice, ECG and charging cable vary.
- The specific fault this record addresses: will not pair with the phone
What it does not cover
- ×The same symptom on a different Fitbit product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
Bluetooth is off, busy, or the devices are too far apart
What separates it The app never finds the watch, or finds it and times out.
How to confirm Place both devices charged and side by side, with Bluetooth on and airplane mode off on the phone, and close other apps competing for the Bluetooth connection.
- 2
The watch is still paired to a previous phone
What separates it A used or hand-me-down watch, or your own after a phone change, will not pair to the new phone.
How to confirm Unpair it from the old phone through the app if you still have it; a watch bonded to another phone will not pair to a new one until that bond is cleared, sometimes only by a reset.
- 3
The companion app or the account step is blocking
What separates it Pairing stalls at signing in, updating the app, or a terms/permission screen.
How to confirm Update the companion app and complete the account sign-in and permissions; an out-of-date app or an incomplete account step is a frequent pairing failure.
- 4
The phone or its OS is not compatible or is out of date
What separates it The watch requires a phone platform or OS version the phone does not meet.
How to confirm Confirm the watch supports this phone platform and OS version; some watches pair only with one platform, and many need a recent OS.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Whether the watch is brand new or previously paired to another phone.
- Whether Bluetooth is on, airplane mode off, and both devices charged and close.
- Whether the companion app and the phone OS are current and compatible.
Update the phone and companion app, and place both charged devices nearby
ReversibleRules out an old app and a distance/Bluetooth problem at once.
Clear any stale pairing from the old phone and from this one
ReversibleA bond held by a previous phone blocks a new pairing.
Pair through the official app before considering a factory reset
ReversibleComplete the account and permission steps in order.
Confirm sync, notifications and one app action after pairing
ReversibleProves the pairing is fully functional, not just connected.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- G4SKY. Fitbit device; Google-account migration, onboard GPS, voice, ECG and charging cable vary.
- Model — Ace LTE (kids watch)
- A children's smartwatch with LTE CELLULAR (calls/messages to approved contacts), GPS location for parents, a speaker and microphone, and motion-based games. So it uniquely (for Fitbit) DOES have cellular and speaker/mic symptoms.
- Cellular plan required
- Its calling/location features need an active Ace LTE cellular plan (a Google/Fitbit subscription) — 'calls or location not working' is often the plan/provisioning, not the watch. Set up and managed by a parent in the companion app.
- Parent-controlled
- Contacts, school time and features are parent-managed in the app; many 'restrictions' are the parental settings working as intended, not faults.
- Backup path
- Carries a cellular backup path for alarm signalling. Backup carries signalling, not bandwidth — so the system can report itself online and monitored while everything that needs broadband fails, and can stay in that state for weeks unnoticed.
- Symptom boundary
- This record covers Fitbit Ace LTE when it will not pair with the phone. A different symptom on the same hardware, or this symptom on a different Fitbit product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !Do not factory-reset the watch to force pairing until you understand any unsynced activity and account/activation lock — a reset can strip data and lock a watch to the previous owner's account.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Google Fitbit Help publishes this as "Why can't I set up my Fitbit device?". Google's Fitbit setup/pairing article. Probed 2026-08-28: title-verified. What that article does not carry is the model boundary — it is written for a product line, and G4SKY is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
My child's Fitbit Ace LTE can't call or be located.+
The Ace LTE's calling and location depend on its LTE cellular plan (a subscription), so first confirm the plan is active and provisioned in the parent app — an expired or unprovisioned plan disables calls and live location. Then check the approved-contacts list and any school-time or bedtime restrictions, which intentionally limit features at set times. It needs cellular or Wi-Fi coverage to connect. Most 'not working' cases are the plan or the parental settings, not a hardware fault.
My watch won't pair with my new phone.+
If the watch was ever paired to another phone — including your old one — it is likely still bonded to it and will not pair to the new phone until that bond is cleared. Unpair it through the companion app on the old phone if you still have it. Otherwise make sure both devices are charged and side by side, Bluetooth on and airplane mode off, and the companion app updated. Only reset the watch as a last resort, because that can wipe unsynced activity and, on some watches, requires the previous owner's account to unlock.
Does this answer apply to every Fitbit model?+
No. It is scoped to G4SKY. Fitbit device; Google-account migration, onboard GPS, voice, ECG and charging cable vary.
What should I record before troubleshooting pairing or phone?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing pairing, phone. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not reset until unsynced activity and account recovery are understood.
Answer for the exact device and software version shown above.