Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

cubedweller

macrumors 6502
Original poster
Nov 25, 2007
305
52
Sort of a weird issue. I have a Sleep schedule set on my iPhone and it's always worked well with my old S5. Since upgrading to my AWU2 (and 10.0.1 and 17.0.3), Sleep focus behaves really weird. When Sleep focus enables on the iPhone it also enables on the AWU2 (so far so good). When the alarm goes off in the morning, however, I "Stop" it from the AWU2 and Sleep focus appears to exist for a minute or two on the AWU2, after which, Sleep focus re-enables itself on the AWU2 and never exists from the iPhone. Similarly, the alarm on the iPhone still shows as it's "going off." I have to manually exit Sleep focus on the iPhone and AWU2.

I'm pretty sure that with my S5, when I stopped the alarm via my watch, Sleep focus exited on both devices and the alarm was stopped on my iPhone as well. Is this the expected behavior? Should I unpair/repair? Is it a bug? Anyone else experiencing this?
 
I don’t use sleep with alarms but focus definitely doesn’t work like it used to and IMO it is buggy. I use 15PM w/ S8. I have a house alarm app set up as emergency override to send text for events. Before iOS17, it worked fine. When the alarm state was changed I’d get a text that would override the DnD on my S8, which I wear when sleeping.

If I set the sleep focus on my iPhone it will appropriately set my watch DnD settings but it never sends the override notifications to my watch like it used to in iOS 16 and earlier versions. The iPhone gets the notification but the watch does not. Since the iPhone is silenced does not alert me.

The work around for me is to set the focus on the watch instead of on the phone & just set the phone ringer to silence. This way my watch gets the DnD overrides which is what I want since I wear the watch when sleeping.

This problem is the same w/ normal DnD or Sleep. This sounds to me like the way it is working is the way it is working for your situation. I did do an unpair several weeks ago to fix a notification issue so it seems to me that doing another unpair is not going to help. But then again I’m just a person on the other end with a keyboard and no specific skills on this matter.

If the upcoming release doesn’t fix this then I’ll file w/ Apple feedback.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.