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

Apple Health Sleep Syncing "asleep" data displaced by several hours

Sorry if this isn't the right place, I haven't used the forum before!

I've got a problem with the way Garmin Connect is syncing sleep data. The data for "In Bed" are syncing correctly, and showing the correct time, but the "asleep" datapoint is syncing with a six to seven hour offset, even if I've manually set the sleep time in the connect app.

Here's a couple examples of what's happening:

[IMG2=JSON]{"data-align":"none","data-size":"full","src":"https:\/\/forums.garmin.com\/filedata\/fetch?filedataid=45956&type=thumb"}[/IMG2]

The "In Bed" time is accurate, the "asleep" part... not so much.

I'm actually getting really good accuracy sometimes, for example compared to Sleep Cycle here:

[IMG2=JSON]{"data-align":"none","data-size":"full","src":"https:\/\/forums.garmin.com\/filedata\/fetch?filedataid=45957&type=thumb"}[/IMG2]

But the "asleep" time offset throws off any analysis I might want to do.

Has anyone else had this problem, or has a solution to possibly fix it? ciq.forums.garmin.com/.../1308714.png ciq.forums.garmin.com/.../1308715.png
  • Former Member
    0 Former Member over 7 years ago
    I pointed this out to support and they pass the blame to Apple, which is false. The Garmin Connect app writes the data to healthkit, Apple does not sync data from Garmin Connect. How do I know? I gave permission to Garmin Connect iOS app to read/write to Apple Health and never Apple Health to read data from Garmin Connect (website). Mine seems to be 8 hours off. Seeing that it's 8 hours forward for me, I assume Garmin Connect iOS app is writing the data as UTC 0 and not respecting my timezone at UTC -8. The support person I had never tested anything, simply relied on my screenshots and Garmin's misinformation. I've disabled sleep tracking writing into Healthkit as the data is wrong. Today's update did not fix the issue either.
  • Thanks for letting me know I'm not the only one / crazy!

    Seeing that it's 8 hours forward for me, I assume Garmin Connect iOS app is writing the data as UTC 0 and not respecting my timezone at UTC -8. The support person I had never tested anything, simply relied on my screenshots and Garmin's misinformation. I've disabled sleep tracking writing into Healthkit as the data is wrong. Today's update did not fix the issue either.


    Timezone issues are my guess as well, it seemed to start being a problem more once I was going between UTC -8 and -7 more often. I did the same as you and disabled it—I now use a separate system for sleep tracking.
  • Former Member
    0 Former Member over 7 years ago
    Thanks for letting me know I'm not the only one / crazy!



    Timezone issues are my guess as well, it seemed to start being a problem more once I was going between UTC -8 and -7 more often. I did the same as you and disabled it—I now use a separate system for sleep tracking.


    The iOS app that was released yesterday, v4.4 appears to have fixed the issue.