Closed vanthomiy closed 3 years ago
Its possible that the two different calculations of the isSleeping can cause some weird behaviour in the last hours. Thats because we detect "no sleep" with the first function and then later recalculate it with the more accurate function and detect "sleep". Thats why we often get more sleep time afterwards.
Actually we have a 10 to 30 min lag to the real sleep time. This is caused be the define user wakeup lag. We should handle it diffrent before the wake up point is calculated. Maybe we should "add" this time or take the 0 lag isUserSleeping calculation.