03-29-2017
08:53
- last edited on
07-20-2017
15:52
by
AlessFitbit
03-29-2017
08:53
- last edited on
07-20-2017
15:52
by
AlessFitbit
I have the most up to date app and my iphone is up to date as well. Yesterday, my sleep stages tracked, but last night it did not. I've restared the Fitbit, the phone, installed, uninstalled, and reinstalled. Nothing worked. Any idea how to fix?
04-28-2017 07:38
04-28-2017 07:38
04-28-2017 22:31
04-28-2017 22:31
05-02-2017 21:32
05-02-2017 21:32
Same isue here sleep stage shows first night only after that it shows only sleep pattern. Hope fitbit will fix or any solution
05-03-2017 01:57
05-03-2017 01:57
Still not working for me, I feel like an official message from fitbit would be useful at this stage given the size of this thread and apparent prevalence of the issue.
05-03-2017 02:34
05-03-2017 02:34
I think that's unlikely. They don't seem to know the answer and are clutching at straws.
Every time anyone starts to suggest that it might be down to fitbit rather than you or me and the silly things we do with our Fitbits (like wear them to go to sleep or take them off to charge them) they close the thread down!
05-03-2017 05:03
05-03-2017 05:03
I went straight to Fitbit and they determined from looking at my account that my Fitbit is actually faulty and not charging properly and I've been sent a new one 😊
05-03-2017 08:43
05-03-2017 08:43
Same here... Fitbit Support determined that mine isn't working properly as well, and is sending me a new one.
05-03-2017 09:13
05-03-2017 09:13
My blaze fitbit stop tracking my sleep patten, any suggestions on what to do?
I've cleaned all the connections.
05-03-2017 13:59
05-03-2017 13:59
05-04-2017 07:22
05-04-2017 07:22
Mine worked 2 days and then stopped last night. Have any of you gotten an actual solution/reason for this or is it just glitchy?
05-04-2017 10:47
05-04-2017 10:47
My Charge HR 2 sleep stages worked only for two days as well. May 2 & 3 it us there, and now back to the old sleep pattern this morning 5/4. Disappointing.
05-04-2017 11:15
05-04-2017 11:15
That's the same model/experience I had. 😞
05-04-2017 13:16
05-04-2017 13:16
05-04-2017 14:31
05-04-2017 14:31
It's a software issue IMO. I have a Charge 2 and and the iPhone app. I think the app is the culprit. If I sync the Charge 2 quickly after waking up, sleep stages are not displayed. If I wait and sync later, the same data seem to be processed differently and sleep stages are calculated as expected. I think the tracker and the data are OK. But sometimes data are not processed correctly. I think that if we sync to quickly, the software does not understand that the night is actually over.
Anyway there is room for improvement, Fitbit !
05-04-2017 22:44
05-04-2017 22:44
05-05-2017 11:36
05-05-2017 11:36
My Fitbit Blaze worked for one night then stopped again after resetting
05-07-2017 14:59
05-07-2017 14:59
05-07-2017 16:24
05-07-2017 16:24
Forgot charge 2 worked the first night & not since. I don't need any more hassles of something I'm going to have to stuff around d with. I'm taking g it back if it's not a reliable product.
05-08-2017 04:44
05-08-2017 04:44
Just got my new charge 2 on Saturday. The first two nights recorded my sleep stages and was awesome. I eagerly opened the app this morning and it's back to the format my Alta had. It recorded my heart rate all through the night, so I know it's not because of that. Should I send the charge 2 back? It's brand new and completely updated.
05-08-2017 04:56
05-08-2017 04:56
This appears to be an ongoing problem with all models of fitbit that support sleep stages. I have a Blaze and my husband has a Charge 2. They both work perfectly in every other way except for sleep stages.
Have posted here and messaged fitbit. Only sensible help came from another forum user. Nothing from Fitbit. Mine is now working every day as long as I don't manually set sleep on the app.
My husband's had been better using this method but he still had one night last week where it reverted to the old style.
I doubt that it is a problem with individual Fitbits. Much more likely to be a software problem that Fitbit seem unable /unwilling to sort out.