iOS 14 sleep wake up alarm sound not working on iPhone

"Today, my alarm sounded on my watch only (which is too quiet), while it was on the charger. This never happened before the recent ios updates. What makes the watch think it's on my wrist?"

Turn off nightstand mode for the watch.

For some reason nightstand mode may now reroute your alarm to the watch, when the watch is on the charger. There's a little note about it somewhere in the settings now.

Yeah, I know.... Anyways, that's the reason, and the "fix," although it's technically working as iOS 14 intended it.

Thanks! And that's stupid. I set my alarm on my phone because I want it to ring on my phone. When it's on nightstand mode, I can see on the watch the time of the alarm I set ON MY PHONE. It worked fine before ios 14.x (never noticed before 14.1 or 14.2). And this older article describes how I wanted it work - you have to set it on the watch for it to go off on the watch. Apple get on it! https://store.cultofmac.com/blogs/learn-about-your-apple-watch/how-to-use-apple-watch-s-fantastic-nightstand-mode

OK, I thought I'd be clever and turn off the watch alarm that had obviously mirrored from my phone, but once I did that it turned off on my phone. Anyone know any way to not have the watch alarm mirror the phone? Again, this is stupid.

Actually, it would just be nice if they'd add a toggle to let the user decide whether the alarm should play on the phone too. I tried to adjust after I had turned OFF nightstand mode as suggested above.

I like nightstand mode, but the watch alarm isn't loud enough to wake me up.

There should be a way around with the regular alarms as an audible backup without having to be on silent mode, although I can't pinpoint one last problem.

Ok, so the regular wake with sound is pretty much out for most of us in this thread, if we intend on having the watch do sleep through the Apple app as well.

Disabling silent and so forth shouldn't be required for the non-sleep alarms, as they should be audible no matter what, but they aren't always, and I'll explain what I mean.

First, I now set it so DnD and Sleep are not turned on automatically. I enable it on the watch or on the phone, and moved the toggle in both "control centers" to an easier to spot location. Enabling sleep manually allows you to have it toggle DnD on/off with it, so that if you go back to sleep after your alarm you can just make sure you still have sleep mode on.

So that takes care of the tracking part not having to be locked solely to your bedtime schedule on the device.

Second, I set Alarmy as my secondary alarm, and make sure it's always running in the background before bed. (You shouldn't need to do this, as the non-bed alarms should break through the silence, but they don't always).

Here's the problem, even with manual work arounds: This morning, I had the bed alarm set as usual, knowing it would only vibrate. It was set for 9am. The first regular Apple alarm was set for 9:15, and should have been audible. It was not, and the only reason I can think of is that the iPhone gets confused if there are two alarms trying to play at once, and the net result can be that you get nothing at all. This appears to have been what happened to me today, although Alarmy still kicked in as a fail safe at 9:25am.

Tonight I'll see how the following works... I'm going to leave the bedtime alarm turned off permanently, but leave the homescreen sleep shortcut settings and sleep time in place, and run everything manually, with only the regular alarms, and see how that goes. If the regular alarms won't get defeated by the silent one, that's good enough.

It would have just been so much easier to make it a simple option to have the wake up alarm do vibration and audible.

I can understand that.

In the same way that I would prefer to not have to manually enable and disable sleep and the alarms, I guess some people would prefer the opposite, and not want to have to make sure their alarms aren't set to go off during the middle of their day....

It sounds strange to me, but I can see the flip-side.

That's why a toggle is the simple solution for all.

It could even be in the control center: because you can already put the alarm app there anyways. If there was a way to have that show that an alarm is armed for audible, and have a toggle right in the alarm app that it takes you to, it would solve the problem and everyone can have it however they want it.

I think that would be a good compromise over having to reverse the new design. If you ever get to that level of support again, maybe you could make a suggestion that you think might work for everyone.

^^^^

For others with the issue, please use the link IdrisSeabright posted, in order to help get the word to Apple that we would like the option to still have our bedtime alarm be audible.

I filed my suggestion and bug report awhile back when Apple support told me that it would be considered a new bug.

They said as there wasn't any warning explaining the exact changes to the user settings that were already in place, that it should not be considered a feature change, so I put in the suggestion for a toggle to give the user a choice when I filed the bug report. But of course, I'm just one out of many.

My alarm did not go off this morning I was on my phone at zero 4:59 and my alarm was set for 5 o’clock and it did not go off. I was reading a text at zero 4:59 when I look back at my phone it was 0502 there is no way I was reading that text for that long. iPhone 12pro

Yes, exactly the same experience here. I'll try it too!

Has anyone tried setting a normal alarm (outside of sleep/wake) to see if that still works? At least to use while they address this? 😖

Yes, I posted that earlier in this thread.

Watch app>sleep > don't use this watch for sleep>turn off.

I went through this also. Please go to the watch app on your iPhone, then sleep, then select don't use this watch for sleep, turn off.

val_in_the_desert wrote:

Same issue. Was convinced I hit snooze but now 2nd day late to work. Apple - wth?! PUT BEDTIME BACK IN ALARMS! I hate the Health app.

Tell Apple:

Product Feedback - Apple

Me too; same problem. Let’s hope the next update fixes this or......can we go back to update 13?