This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connect Issues - Particularly Sleep Reporting?

It looks to me like changes were made to Connect yesterday which may have caused some issues.

Yesterday, my step widget showed 0 steps for about an hour or so although drilling down showed the same steps as my vivosmart. This was fixed later in the day but this morning, my stats from sleep detection are totally off-the-wall. Sleep levels make no sense. The movement graph ends at midnight which is probably why the levels make no sense this morning. Also, Connect said I woke up when I did my first sync of the day although I had been up and moving around for more than an hour by then. My steps for today so far make sense so I don't think it's the accelerometer of my vivosmart that is causing this.

The status page shows everything Green but there is a disclaimer at the top of the page indicating Connect is experiencing issues.

0 pshare over 9 years ago

For the second night in a row, Connect shows no movement tracking stopped after Midnight. Movement tracking starts again when I do my first sync of the day. One difference between 2 nights ago and last night is that, after midnight, it showed I was in deep sleep. For last night, it showed I was in light sleep after midnight.

Obviously, something is going on for me. Is there no-one else who has the same issue? My concern is that, about 2 weeks ago, support gave me a refurb to replace a vivosmart that had a display problem. I wonder if it may be defective.

0 Former Member over 9 years ago

For the second night in a row, Connect shows no movement tracking stopped after Midnight. Movement tracking starts again when I do my first sync of the day. One difference between 2 nights ago and last night is that, after midnight, it showed I was in deep sleep. For last night, it showed I was in light sleep after midnight.

Obviously, something is going on for me. Is there no-one else who has the same issue? My concern is that, about 2 weeks ago, support gave me a refurb to replace a vivosmart that had a display problem. I wonder if it may be defective.

Hi Phil,
We have sleep reporting issues on two devices since 7 October as well. One Forerunner 15 & one Vivofit. Both have a records missing up until this morning and the information displayed this morning is showing "Deep sleep" for most of the night on both devices which is not normal according to past history. I doubt that all three devices have developed the same fault simultaneously so feel that it is more likely a Garmin Connect issue. Time will tell I guess. Anyone else seeing this yet?

Brian

0 pshare over 9 years ago

Hi Brian,

This was thread I had started back on the 7th that no-one responded to. Now all the sub-forums are overrun with similar issues.

It just shows we're ahead of our times.

0 Former Member over 9 years ago

Thanks Phil. It would be my preference to be leading the "news" with a positive development however we can hope that Garmin is taking some notice and actions to resolve. I noted that my Vivofit sleep record for the 12th is missing rather than showing erroneous data so perhaps this means someone is working on it as the GC Status webpage shows "Limited" service at present at least.

0 SUSSAMB over 9 years ago

For anyone having issues with Connect it's best to check the sticky at the top of this forum

https://forums.garmin.com/showthread.php?185049-Garmin-Connect-Webpage-Status-Tool

0 pshare over 9 years ago

I've been using a vivosmart and a vivofit since the issue began. Last night, my vivosmart gave me an auto-sleep graph that finally made sense. My vivofit still doesn't show anything.

This is an update Garmin sent me last night.

Philip I have added the additional notes to your open case. Also the days that are not showing sleep is a new thing.
We have received multiple reports from customers who are missing sleep data. We are aware of the issue and we are working to resolve it as soon as we can. At this time the status page has been updated to reflect this issue.