Wildly wrong sleep data imported from Garmin Connect

"Sleep" metrics have sync'd over from my Garmin watch, but they're wildly wrong.

Here's a breakout for the past 4 days:
5/18: 7h23m Garmin, 9.55 Cron
5/17: 8h46m Garmin, 1.42 Cron*
5/16: 7h57m Garmin, 9.62 Cron*
5/15: 6h34m Garmin, 6.57 Cron*, **

*These were back-synced when I opened my Cronometer account
**This one's dead-on.

There doesn't seem to be any mapping or way that I can make sense of what's getting transferred, it's almost as though there's a data field mismatch -- i.e, some completely different piece of data is getting read as "sleep" & then rendered as a number of hours. I have my doubts about the accuracy of Garmin's sleep data, but this is clearly a data transfer error.

I understand I can simply omit the sleep data from sync, but this calls into question the accuracy of all the other data. I'd been hoping to pull data into Cronometer (as it's better-focused on the health metrics I care about most right now), but I'd rather not have to manually verify the data transfer every day. (And once transferred, it doesn't look like data can be removed - it's just wrong forever in one's Cronometer DB.)


  • I'm seeing the exact same issue.
    Also in May 2020.

  • Would you mind writing in to [email protected] with a few details about dates and times reported in your Garmin app vs. Cronometer? Screenshots of your Garmin app would be a big help!

    Were there any interruptions in your sleep on those dates? Sleep data can be a bit trickier to import compared with other metrics because they are usually recorded over two different dates and then reported as a single value - it can cause issues that we wouldn't see with other imported data.

    Thanks for bringing this to our attention so that we can look into this further!


    Karen Stark
    As always, any and all postings here are covered by our T&Cs:

Sign In or Register to comment.