Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Liked your blog and reviews. I have tried several sleep trackers and stuck with sleep Watch as it didn't require me to install the apps. It will eventually report on your sleep but doesn't have much info and it can struggle to know my actual sleep so much I have to adjust and what knows if that is accurate. I just know that it didn't take an hour for me to fall asleep.
 
Liked your blog and reviews. I have tried several sleep trackers and stuck with sleep Watch as it didn't require me to install the apps. It will eventually report on your sleep but doesn't have much info and it can struggle to know my actual sleep so much I have to adjust and what knows if that is accurate. I just know that it didn't take an hour for me to fall asleep.
Thanks :)

Sounds like it works similar to Autosleep. No apps are installed on the watch and it uses data from health to work out the sleep. I guess if Apple offered native sleep tracking, it would work like this.
 
So I got my watch a few days ago and was looking froward to trying this.

I don't know if I am the only one but I was having 2 problems with "Sleep Tracker: Auto Sleep Cycle Watch Monitor" which I tried first:
- It was hitting the battery life quite a bit, even during the day (I had no other third party app installed and battery immediately and clearly improved after I deleted it, so I am pretty sure it was the problem)
- For some reason it was recording two identical sleep entries per day

So I moved on to AutoSleep, and though I don't like the IU (ugly and unclear in my opinion), it seems like a better technical solution to me at the moment and this is what I will go for.
 
Autosleep 2.0 is now available. It mostly seems to be a UI change in terms of how you adjust settings/sensitivity and manually correct data. Slightly better but still fairly ugly looking and not super user friendly in my opinion.
 
I updated my Watch from watchOS 3.1 to 3.1.33 days ago, and FYI this seems to lead inconsistencies in Autosleep.

Basically for me the level I need to set on the sensitivity slide to get accurate sleep information is quite different depending on whether the data was collected by the watch running watch 3.1 or 3.1.3.

In the long term an assuming this will not change again with further version it is not a big issue, you can chance adjust the sensitivity.

But it is still a bit of a concern if you have historical data which was collected by both versions: since the sensitivity setting affects all days, you will have to chose for which version the data will be displayed properly and accept that it won't be foe the other version.

I suspect issue will go away over time as HealthKit won't have motion data for the old watchOS version anymore, but I have dropped an email to the dev to ask about this.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.