2024-04-13

Apple sleep tracking

I only post this because someone else may be as confused as I.

It is confusing - the instructions are very very clear that the Apple Watch will track sleep only when in "sleep focus", and you can set a schedule for that.

My issue is that I do not got to sleep at the same time - I could go to bed as early as 6pm or as late as 11pm. I could sleep all night, or sleep, and be awake, and sleep again (the old school "two sleeps" that apparently was the norm in medieval times) - last night I was awake and watched the really good "Miss Potter" film between sleeps. And no, I was not "in bed" all that time, so it is a tad confused and probably could have worked that out.

So I did not want to set a sleep focus schedule that was too soon as it stops notifications/alerts/calls. But also did not want to set too late so it does not record sleep. I did not want to set manually as I would forget, plus, it seems, you have to tell it to end the sleep focus (even if you have a schedule). I do get up consistently in the morning, so that helps.

My concerns were totally unfounded, as it seems that Apple are happy to record sleep starting way before your sleep focus is scheduled to start. So I can simply set for a sensible later time.

Why the hell don't Apple explain this? Why make me think I have to fuck about with "sleep focus schedule"?

4 comments:

  1. It's weird, because Fitbit has pretty much always just worked out (somehow) when you're asleep - you don't have to tell it any kind of schedule. So it's not like it's an insolvable problem.

    ReplyDelete
  2. How do you sleep wearing a watch? I've never been able to.

    ReplyDelete
    Replies
    1. I never take my watch off, which is why it needs to be waterproof (shower). I am not sure I would feel right sleeping with it off!

      Delete
    2. If you always keep it on; when do you charge it?

      Delete

Comments are moderated purely to filter out obvious spam, but it means they may not show immediately.

ISO8601 is wasted

Why did we even bother? Why create ISO8601? A new API, new this year, as an industry standard, has JSON fields like this "nextAccessTim...