You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Stand goal 50% completed while sleeping following 3.1.1 update

I updated my series 2 watch without issue (though it did take a while) - had not read about the issues it's been causing - so guess I was lucky!


However, I have noticed it is saying I'm standing regularly overnight, even though I'm sleeping. I know I'm asleep as my whithings sleep sensor thing shows I am. It's doing it when I'm wearing it and when it's in charge.


Not sure what is going on. Anyone else noticing this?

Posted on Dec 14, 2016 2:05 AM

Reply
69 replies

Jan 31, 2017 7:36 PM in response to xenopain

I guess you did not see my last post. I went to the Apple Store to inquire about fixing the bug in 3.1.1, and they didn't know anything about it. Their "latest" update was 3.1. I explained what 3.1.1 was doing with the stand time. The person said he thought it was the sensor, but I insisted that I thought it was 3.1.1. He sent it in to repair. Repair restored the software and firmware. They put it back to 3.1. Now stand time works. I heard 3.1.3, the newest update, causes the problem again, so I'm staying put on 3.1.

Jan 23, 2017 11:34 PM in response to happy kayaker

So the new update 3.1.3 did not change the behavior, I did update my watch yesterday evening and still it did count every hour during my sleep. So far I did not recalibrate, but this should not be necessary for the standing activity. let see how long it will take until this will be fixed.

At least I did not see any other negative impact so far and the update did not brick my watch either....

Jan 31, 2017 11:44 AM in response to happy kayaker

I am also now having this issue. My 42mm Series 1 has worked fine since September, near-perfect sleep-tracking. However, it went wrong from last week, the exact day I updated to 3.1.3. I've been onto Apple Support and, apparently, this is not an issue they have ever heard about...I guess they haven't found this thread yet!


We updated my wife's 38mm Series 1 at the same time and hers is fine.


I have tried restore from backup, erase and set up as a new watch - all to no avail. Come on Apple, sort this out.


It's like the update has made the sensor too sensitive.

Jan 31, 2017 12:14 PM in response to happy kayaker

I talked with a senior advisor yesterday, through a scheduled call from AppleSupport on Twitter and I described the situation to them. My discussion with the support also included links to this discussion as well as other related ones I found in here and on reddit. They said they will look into it.


I don't think it is a sensor or sensitivity issue. Today I had stand hours for hours that had no steps logged for them. I see other hours during sleep that somehow log a few steps, and I might be moving in bed. In any case stand hours require about 100+ steps to count, and it is weird that hours with no steps also can be counted.

Feb 1, 2017 12:09 PM in response to happy kayaker

Huh, I just saw this issue in action. As I was sitting, typing along some code, I got the notification to stand up and move around a bit. I finished whatever I was doing, then lifted my wrist up to see what the notification was, and immediately got the "You did it" notification for standing up. I checked the steps and it did not look like it accidentally registered some random movements as steps and I did not have any steps for the hour at all.


It is weird after I actually got no stand hours corresponding to the time I slept today.

Feb 6, 2017 10:18 AM in response to happy kayaker

I have a series 2. Was not having a problem with 3.1.1 or 3.1.2. Updated on Saturday to 3.1.3 and now have this exact same problem mentioned by others in this thread. No way is this a 'sensor' or 'calibration' issue as suggested by Apple. Unfortunately though it seems this issue has been ongoing for sometime with many of you hoping the next update resolves it. Other than the person who gave their watch back to Apple for a week for them to reset it to version 3.1... Which if this was simply a sensor issue seems Apple would have given it back with the latest update. Hmmmm.....

Feb 10, 2017 9:00 AM in response to happy kayaker

I have an original 42mm watch and also have this issue. I have removed all apps that were listed as sources to the Health app, deleted calibration data and re-calibrated the watch, erased all watch content and unpaired, then setup as a new watch. None of these things changed the behavior. I wear the watch to bed so it can wake me at 4:50am (while allowing my wife to sleep) and this morning it showed -0- steps and 4 "stand" hours. I have a Genius Bar appointment set for early tomorrow afternoon, not sure if they will be willing to replace it or not.

Feb 10, 2017 9:24 AM in response to prodemann

Prodemann, I called Apple Customer Support and was transferred to a "specialist". After spending about an hour on the phone and pointing her to this thread and also she found 'internal' discussions about this issue she set me up as something called an Apple Watch profile. Which they sent a link where you download some software to your watch and when the problem occurs again you let them know. They time stamp it and download data from your phone to help figure out the issue. Why I'm saying this? I got on a plane for Europe for a biz trip and can't do it. Not that you should. Just saying. Not sure the Genius Bar can help. BTW. I have a friend bought a series 2 last week. Same issue. He updated to watchOS 3.1.3 and has same problem. Cheers!

Feb 10, 2017 9:51 AM in response to prodemann

I posted previously that the Genius Bar person thought it was a sensor problem, and thought the latest update (as he had) was 3.1. He said it needed to be sent in for repair. I insisted he put on the ticket that I believed it was the 3.1.1 update. I didn't think it was a sensor problem as it worked fine before I updated to 3.1.1. Repair restored the firmware to 3.1 and I haven't had the problem since. I did not download the newest update 3.1.3.

Feb 13, 2017 10:51 AM in response to happy kayaker

As I posted earlier I had an appt Saturday with the Genius at Apple. I had noted in the appt all the steps I'd taken to resolve the problem unsuccessfully. He took the watch and is sending it in with a recommendation to replace it. I realize that the replacement may or may not have the same problem but I will be receiving a brand new refurbished original Watch. 3 to 5 business days and we'll see. I may just sell it and take this as an opportunity to upgrade to a Series 2.

Feb 16, 2017 5:53 PM in response to prodemann

I went back to the Apple Store today to pick up my watch after it came back from the technicians at Apple. They ran hardware diagnostics on it and sent it back to the store saying nothing is wrong with it. I wound up explaining why this is wrong to the Senior Genius and he said that the Apple Watch was not designed to wear to bed and that is why it is doing what it's doing. No matter that it worked fine until the WatchOS update. VERY FRUSTRATING! I refused to accept the watch and went into great detail about this thread and the 3.1.1 update, insisting they return it again to Apple for either rolling back or replacing under AppleCare. When I left the store I called 800-AppleCare (800-275-2273) and escalated the case. One thing I wish I could do was point the Advisor to other case numbers regarding this same problem. My case number is ****. If I am able to get some resolution others can refer to this case as help in their active case. ****
<Edited by Host>

Stand goal 50% completed while sleeping following 3.1.1 update

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.