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

Venu 2 Sleep data not synching with App

I have had Venu 2 for 5 days now. The sleep data does not sync with the app consistently. When sleep data are synched it takes a long time to show up in the app. My sleep data were not recorded last night. I called Garmin Support to inquire about the issue. Do other folks have similar issues with sleep being recorded and synching with the Garmin Connect App?

  • Guys, you do realise that automatic sleep tracking is a server-side activity which analyses the data recorded by sensors 'after the fact' to determine the time you (actually) fell asleep, when you woke up and everything in between. It will take time for the software to ascertain that you have finally woken up and then only it will compile and present your sleep data. So, there will never be any data immediately after you wake up. In fact, if you wake up, get out of bed, drink some water or visit the bathroom and then go back to bed and sleep, the software will (later) consider everything as part of the same sleep cycle. 

    I realised this years back when I moved on from Microsoft Band 1 to Band 2. The earlier version had manual sleep tracking so you had to 'stop' it when you woke up and the sleep data would be available immediately. But Version 2 had automatic tracking and it would always take some time after waking up that sleep data could be seen. 

    Therefore, give your Venu 2 some time before checking for sleep data. How much time? I'm not sure about that, but I have gotten into the habit of looking for it after my morning workout etc. 

  • Does not sync the night I miss anymore when it fails

    One possible idea:

    If Venu2 is NOT the prefereed Tracker but the Fenix is powered on in docking station. Even if this seems not to be a problem with all other measurments it could be an explantaion fot sleeping data.

  • All - this issue was resolved with a fix included in the 4.67 firmware update.  If you are still experiencing this issue, please start a new thread and confirm what firmware version that your watch is running.