SLEEP Records Unable To View

54 views
Skip to first unread message

Clem Johnson

unread,
Jan 11, 2015, 10:08:38 PM1/11/15
to amiigo-fitn...@googlegroups.com
Received an error this morning when analyzing the sleep data (see attached screenshots):

Uh oh!

It looks like we hit a snag while
processing your sleep data.

We have been notified of the problem. Please check back in a day
or two; your timeline will be
automatically updated when we have fixed the issue.

I have no idea what happened or if the data is gone forever...

Reliability of their servers is in question here.
Screenshot_2015-01-11-09-45-20.png
Screenshot_2015-01-11-09-45-47.png
Screenshot_2015-01-11-12-08-52.png

Clem Johnson

unread,
Jan 12, 2015, 11:58:23 AM1/12/15
to amiigo-fitn...@googlegroups.com
Worked this morning (01.12.15). Hopefully, they have their connectivity issues worked out? No way of knowing what the previous days collected data was. No support to contact no way to know what happened...

Clem Johnson

unread,
Jan 14, 2015, 10:10:30 AM1/14/15
to amiigo-fitn...@googlegroups.com
Unable to process my SLEEP data AGAIN! After 1 hour of updating/syncing it returned with the same error message on the home screen: Error! Touch to view...

This is getting old. As the problem screen says to do I went back and checked a few days back (when I recieved the error for the first time) to see if the data was automatically updated when we have fixed the issue but I am unable to view so assume they have not fixed the issue (most likely they don't know it's an issue. So now I have multiple days with no SLEEP data at all.
Amiigo_Sleep_sync_Error.png
Message has been deleted

Clem Johnson

unread,
Jan 16, 2015, 1:47:08 PM1/16/15
to amiigo-fitn...@googlegroups.com
JANUARY 16, 2015
Function: SLEEP

Woke up this morning and stopped SLEEP.
  • I stopped the sleep program at 0540 (see screenshot: slp_start.png ).
  • It starting the SYNC at 0540 (See screenshot: Slp_Sync.png )
  • Then a series of error messages appeared:
    • Slp_Up_Fail.png
    • Slp_Upload_1.png
    • Slp_Up_Fail2.png
    • slp_Upload2.png
    • slp_upload_fail3.png
  • 41 minutes later, after a seemingly botched upload process was on the horizon - it starting Analyzing sleep data...
    • slp_anal_data.png
  • Then 11 minutes later - Analyzing heart rate
    • slp_anal_hrt.png
  • Finally, after one hour and 27 minutes later in successfully completed.
    • slp_success.png
Looking at the SLEEP data graph (See screenshot: slp_chart.png )
  • Statistics stop at 0451
  • I stopped the sleep program at 0540 (see screenshot: slp_start.png ).
Where did the records from 0451 to 0540 (49 minutes) go?

I have noticed you need to have a WiFi connection for best results. However, its not guaranteed. Using only mobile data to compile the data will almost certainly fail. How amiigo is harvesting their analytic data is poorly executed IMO. Perhaps better algorithms are forth coming? I sure hope so...
slp_start.png
slp_success.png
slp_chart.png
Slp_Sync.png
Slp_Up_Fail.png
Slp_Upload_1.png
Slp_Up_Fail2.png
slp_Upload2.png
slp_upload_fail3.png
slp_anal_data.png
slp_anal_hrt.png

dagu...@gmail.com

unread,
Jan 16, 2015, 11:48:34 PM1/16/15
to amiigo-fitn...@googlegroups.com
I track my sleep nightly and have never seen any issues. I rarely use WiFi at home (dish internet is terrible). Have you tried the reset option in the app? Maybe that would help?

Clem Johnson

unread,
Jan 19, 2015, 8:57:18 PM1/19/15
to amiigo-fitn...@googlegroups.com, dagu...@gmail.com
I reset my devices yesterday for a wristband battery fullness indicator issue. It tracked my SLEEP last night - we'll see how it goes in the coming days...

Clem Johnson

unread,
Jan 28, 2015, 10:06:46 AM1/28/15
to amiigo-fitn...@googlegroups.com
JANUARY 28, 2015
Function: SLEEP


The sleep data that errored out on the days of January 11 & January 14 are now viewable. I don't know the exact date that the data was fixed and viewable - as I just checked this morning - but it's now there for both these days.

It was not however, as the error message indicated (Screenshot_2015-01-11-09-45): fixed in a day or two...
Reply all
Reply to author
Forward
0 new messages