The Fitbit API used at the time of this development only allowed for N number of sleep logs (max 100) recorded to be retrieved before a certain date (unlike the other parameters in which you could set date bounds of when you wanted the data to be between). There should be some way to address this in either the retrieval (if possible) or the post-processing, since 100 logs ago could be the past 100 days (if recorded) or it could go back several years to their last recorded log.
The Fitbit API used at the time of this development only allowed for N number of sleep logs (max 100) recorded to be retrieved before a certain date (unlike the other parameters in which you could set date bounds of when you wanted the data to be between). There should be some way to address this in either the retrieval (if possible) or the post-processing, since 100 logs ago could be the past 100 days (if recorded) or it could go back several years to their last recorded log.