Sleep and multiple watches

[sdsvtdriver]

I don't sleep with a watch on, but I use sleep for alarms and bedtime reminders. I have 2 AW's.

After setting up the second one, I put the old one in my office on a charger so use for outdoor work. The next morning, my morning alarm went off on the phone as usual, but also on the old watch (but not on my new watch as expected since it was near the phone).

I turned off sleep on the second watch and the alarms stopped. All was well.

Yesterday, I used the old watch outside and had my phone with me. When I was done, I put the watch back on the charge and switched to my newer one.

Today, I overslept. My alarm didn't go off. I looked on my phone and sleep was off. It took me awhile to figure out why, but once I made the old watch connection, it kind of makes sense.

With that said -

How do use sleep, have my alarm go off on my phone, but not have old watch also have alarm going off in another room everyday? This should be simple but I'm missing it.

thanks.

 

[joeblough]

i have the same question. amazing you got no responses.

for my part, under ios16 and watchos9, with both watches set to track sleep, both watches would apparently alarm. i say apparently because i usually have the 2nd watch on a charger in a different room. the screen on the watch would be showing the alarm screen when i went into that room later in the morning, but the watch as not making any noise. the watch that i was wearing would always wake me up with haptics, and the phone never made a noise.

after ios17 and watchos10, one of my watches never alarms even if i am wearing it. however, it's like the phone knows that the other watch is far away, because the phone itself starts alarming. the other watch is now making noise on the charger.

i have to do some experiments - first is to turn off sleep on the watch i'm not wearing and see what it does, and the other is to turn on sleep on the watch i'm not wearing but turn it off at the start of the night. because the problem seemed to be confined to one watch, i unpaired it and repaired it already and this did not help. however, i did restore from a backup of that watch and may have then loaded whatevery buggy config caused this again.