Inaccurate time asleep

[krugerk]

A user has reported that Beeminder iOS app (5.8 and later with 5.9) produced inaccurate sleep durations. The duration listed in Apple Health is closer to what the user expected. The datapoint in Beeminder seems to be double the amount.

Perhaps it is worth noting that in this case there are multiple sources providing 'time asleep' data to Apple Health. Furthermore, the app is installed on multiple iOS apps and HealthKit integration is enabled on both.

We've even seen an instance of the Apple Health sleep metric feeding Beeminder more than 24 hours of sleep on one day!

Cognata

• Apple Health Metric Support #338
• Stand hours inaccurate #52

Verbata: autodata maintenance, apple health integration, autodata accuracy, autodata fetches,

[krugerk]

'Time asleep' according to Apple Health:

--
as shown in the Web App:

--
As shown in the app:

[krugerk]

I also see the datapoint comment shows auto-updated and not just auto-entered.
Is the app creating a datapoint on one device the adding to that on the other device? That is, that the error is inter app combining one app's reading of HealthKit data with the existing value already in the goal (created by the same app on another device)?

[krugerk]

A workaround for now might be for the user to deny Beeminder iOS access to sleep data on one of the two installations. The Health data itself is synced across iCloud connected devices so the same data should be available on each device.

[dreeves]

This week we have a user in support saying that the numbers for the "time in bed" metric they see in Apple Health don't match what shows up in Beeminder. Eg, 4 hours in Beeminder, just under 8 hours in the Health app.

https://secure.helpscout.net/conversation/2719893023/197692?folderId=2972058

[theospears]

For ticket hygiene purposes, I note the original issue this ticket was about (beeminder massively overcounting time in bed with multiple data sources) should have been fixed for a while now.

For reported user issues I would confirm:

1. Device timezone matches beeminder timezone
2. Goal deadline is set to a time that's in the middle of their waking hours (e.g. noon)

But in general to diagnose these issues we probably need to build something which can create a diagnostic dump of the data beeminder sees from Apple Health.