Reminders app waking mac from sleep

Just clean install 10.15.3 and same issue

2020-02-07 09:31:36 +0300 Start               	powerd process is started                                                  	          
2020-02-07 09:40:34 +0300 Sleep               	Entering Sleep state due to 'Software Sleep pid=771':TCPKeepAlive=active Using AC (Charge:100%) 31 secs   
2020-02-07 09:40:37 +0300 AppWakeReason       	AppWoke:com.apple.bluetoothd Reason:Proximity Wake                         	          
2020-02-07 09:40:39 +0300 Wake Requests       	[process=dasd request=SleepService deltaSecs=14855 wakeAt=2020-02-07 13:48:14 info="com.apple.dasd:0:com.apple.apsd.apprefresh"] [*process=dasd request=TimerPlugin deltaSecs=1878 wakeAt=2020-02-07 10:11:57 info="com.apple.dasd:com.apple.rtcreportingd:NRM"] [process=mDNSResponder request=Maintenance deltaSecs=7200 wakeAt=2020-02-07 11:40:39]           
2020-02-07 09:41:05 +0300 Wake                	Wake from Deep Idle [CDNVA] : due to EC.KeyboardTouchpad/User Using AC (Charge:100%)   

This is a bit of a 'me too' post. I recently upgraded a Mac Mini to Catalina and have been puzzling over why it keeps waking up when it should not. I have narrowed it down to wakeups being scheduled for reminders as set in Reminders.app. It doesn't occur on my MacBook Pro and I believe such notifications are automatically disabled when the lid is shut. But as reported here for MacBooks with external displays (mine does not) and I can corroborate that with my Mini which of course has a monitor connected and is surfing from the problem.

As per the others reporting the problem, Do Not Disturb is set appropriately, but those wakeups keep getting scheduled.

Is everyone with a desktop Mac suffering from this? If so, why not more complaints?

Another 'me too' post: I've got an iMac and a MacBook Air. On both, standby worked perfectly until I updated them to Catalina.

Since then, the iMac doesn't go to sleep on it's own at all. I can put it to sleep manually, but it will later wake up for some reason and then stays awake forever.

The MacBook Air seems to wake up from time to time but goes to sleep again afterwards. When it's closed, I used to loose about 3% charge every 24 hours. Now it looses between 10% and 20% a day when it's closed.

This is massively annoying. How could it be that this hasn't been fixed in months?

I had this issue too and it was driving me crazy... none of the posted solutions worked (i.e. do-not-disturb all the time, etc.).

Here is what worked for me. I changed some other seemingly unrelated Notifications settings... removing sounds, badges, etc. for other applications. I suspect these changes forced the OS to 'refresh' the states of all of the Notifications. Coincidentally, I also disabled all notifications for Google Chrome. Now the issue has gone away completely. I hope this helps other folks.

I have the same issue. I have tried as well a lot of things including clean install of Catalina. It is a bug with the reminder app. You can switch all of in Notification Center. It doesn't help. As well, do not disturb, or any of the other settings don't work. Including 00.00-23.59 DnD!

I think the best thing is, switch of iCloud sync of reminder app and clean all reminders within the app on your Mac. So it means you can only use your other staff like iPhone or iPad for the reminders.

Why the Mac don't go to sleep? This is a bug as well. The Prozess apfsd / hidd let the Mac not go to sleep.

I too have this issue and have tried everything

I upgraded the OS to 10.15.4 this week as I saw in the release notes a number of fixes for reminders, hoping this would rectify the issue - however no luck. Can you please advise how I can stop this from happening. I currently have to shut my machine down every time I finish using it to stop it turning on. 

I have created a new user and tested the reminders to see if it was an issue with my account, it still turned on when the reminder was due. I then reinstalled Mac OS after getting advice from Apple however that has also not fixed it.

iMac (Retina 5K, 27 pouces, 2019) 10.15.4 - fusion drive (apple built-in)

got it as well.

I have reproduce it on a completely clean install. I added a volume and did install Catalina on it and boot from it.

I did not install anything, just created an account, and an issue is there.

So this is definitively a Catalina issue (I never see on Mojave).

It is related to fusion drive, this does not happen on my MBP that has a SSD, a task will appear after some time or after the 1st sleep/wake sequence.

This task is started by apfsd that starts a user agent that starts com.apple.apfsd/wbc_drain that will never stop and prevent the sleep.

I'm wondering if Apple take care of this as you can find many people having the issue.

I find a workaround, not very clean but this is the only way out, and it will not persist across boot.

The workaround consist in killing this background task by killing the UserEventAgent that supports it.

It turns that it need to be killed several times as it restart

in zsh you can copy past this. This will hide the issue until reboot or may be after sometimes the OS will restart this endless task.

until [ -z $(ps -ef | grep UserEventAgent | grep System | awk '{print $2}') ]
do
ps -ef | grep UserEventAgent | grep System | awk '{print $2}' | xargs sudo kill -9
done

Well there is numerous legitimate reasons for Mac to not sleep.

here I just wanted to point out that the one due to com.apple.apfsd.wbc_drain, might be legitimate but looks buggy as it never ever stops.

This particular background task does run only on Mac having Fusion drive.

zsh is the new standard shell on macOS Catalina. You paste the code from above in a Terminal session. So you start Terminal.app on your system and paste the code into that window. I didn't try the code neither validate it so follow at your own risk.

It seems to kill a process named UserEventAgent to prevent the Mac from waking up. According to https://www.howtogeek.com/338994/what-is-usereventagent-and-why-is-it-running-on-my-mac/ this process is handling several background tasks thus I don't know if it's a really good idea to kill it all the time.

Hi stéphane66

This is interesting, I have just run this looking back at the dates from last week from before I started shutting down my iMac to prevent it turning on. I have a recurring reminder every morning at 07:45 which obviously also wakes my iMac (as all reminders do). Here is what your command shows in my terminal. I'm not very familiar with Terminal nor what its results are, but can you decipher this to try and identify why it's turning on? After 10 minutes the computer appears to go back to sleep due to being idle which is inline with my power settings...

2020-04-03 07:45:00 +0100 Kernel Client Acks  Delays to Sleep notifications: [powerd is slow(5014 ms)] [AppleDeviceManagementHIDEventService driver is slow(msg: WillChangeState to 2)(361 ms)] [AppleThunderboltNHIType2 driver is slow(msg: WillChangeState to 2)(322 ms)] [BroadcomBluetoothHostControllerUSBTransport driver is slow(msg: SetState to 1)(393 ms)] [AppleAHCIDiskQueueManager driver is slow(msg: SetState to 0)(821 ms)]           

2020-04-03 07:45:09 +0100 Kernel Client Acks  Delays to Wake notifications: [AppleHSBluetoothDevice driver is slow(msg: SetState to 1)(302 ms)] [AppleHSBluetoothDevice driver is slow(msg: SetState to 1)(302 ms)] [AirPort_BrcmNIC driver is slow(msg: SetState to 2)(382 ms)] [en0 driver is slow(msg: DidChangeState to 2)(595 ms)] [AMDFramebufferSI driver is slow(msg: SetState to 2)(480 ms)] [AppleHDADriver driver is slow(msg: SetState to 1)(461 ms)] [AppleSDXCSlot driver is slow(msg: SetState to 3)(5109 ms)] [AppleAHCIDiskQueueManager driver is slow(msg: SetState to 3)(8180 ms)]           

2020-04-03 07:56:14 +0100 Sleep               Entering Sleep state due to 'Idle Sleep': Using AC (Charge:0%) 20 secs   

You copy paste only the wake operation, the sleep request are the one of interest in that matter.

The Kernel Client Acks just shows how slow are the various driver to process the WakeUp.

In case of and non plan wakeup the reason appears in the lines after the Kernel Client Acks as in this exemple below.

Wake Request at 21:31:56 for the earliest wake up at 22:14:32 for updating the SafeBrowsing data base

Sleep operational at 21:31:56 PM Client asks likely this means Power Manager Client Acknowledge the request

At 21:53:14 the Kernel wakes the Mac, so before the earliest wee request.

We can see why the wakeup happens before the program time the following lines

IODisplayWrangler then Display turned on.

So I did wakes the Mac by interacting with it.

2020-04-06 21:37:56 +0200 Wake Requests       	[process=mDNSResponder request=Maintenance deltaSecs=2439 wakeAt=2020-04-06 22:18:35] [process=dasd request=SleepService deltaSecs=77021 wakeAt=2020-04-07 19:01:38 info="com.apple.dasd:0:com.apple.apsd.apprefresh,501:com.apple.mail.ApplicationRefresh"] [*process=dasd request=TimerPlugin deltaSecs=2196 wakeAt=2020-04-06 22:14:32 info="com.apple.dasd:501:com.apple.Safari.SafeBrowsing.BrowsingDatabases.Update"] [process=powerd request=UserWake deltaSecs=62523 wakeAt=2020-04-07 15:00:00 info="com.apple.alarm.user-visible-com.apple.remindd.time-alarm,543"]           
2020-04-06 21:37:56 +0200 PM Client Acks      	Delays to Sleep notifications: [com.apple.apsd is slow(1003 ms)] [mDNSResponder is slow(5006 ms)]           
2020-04-06 21:53:14 +0200 Kernel Client Acks  	………           
2020-04-06 21:53:14 +0200 Assertions          	Kernel Idle sleep preventers: IODisplayWrangler          
2020-04-06 21:53:14 +0200 Notification        	Display is turned on                                                       	          

the programs requiring the wakes are in the wakeRequest.

Now the easiest way to know if your Mac did sleep is to use this command

pmset -g log | grep 'Total Sleep/Wakes'

it gives this kind of result

Total Sleep/Wakes since boot at 2020-04-06 20:52:59 +0200 :28

The number after the : is the number of sleep since the last boot.

PS: When you copy paste log from terminal please select the text and use the <> button for formatting it as code.

The thing is that we know how the problem occurs. When entering sleep a wakeup call is placed for any upcoming Reminders. The real question is why Catalina is placing those wakeup calls. It obviously should not be doing any such thing and I've yet to receive a response from Apple that they even acknowledge there is a problem.

It is normal if you have a Reminder that is visible to user that the Mac is awake for this reminder.

The log shows

com.apple.alarm.user-visible-com.apple.time-alarm

as the requester of the the wake.

Nothing strange.

I check in my logs I have no occurence of com.apple.alarm.user-visible-com.apple.time-alarm while I'm using Reminders app sync with iCloud.

Here his my advise to completely isolate things.

Add a volume to your disk, with APFS it is easy.

Install a fresh Catalina create an account, do not sync with any online service like iCloud dropbox messenger ..

See if it happens.

Obviously you have an instance of reminders app that seems to cause this.

If you are saying that any set reminder should wake the Mac at that time, then I have to disagree with you. First of all it would be stupid to wake the Mac for every reminder that triggered while sleeping and second, Apple have apparently agreed with that until Catalina as no previous version of OSX/MacOS did any such thing.

There's no question that the Mac should NOT wake up from sleep just due to a reminder - the user is after all unlikely to be there to see the reminder, that's why the Mac is asleep. Most likely explanation is that this is simply poor coding in Catalina, but it would be good to know that Apple are aware of the issue.

I disagree.

I can be sitting close to my mach in an armchair reading a book and thus the Mac is asleep, however I would like the reminder to remind me that I need to get catch my daughter at airport, and need do some task or whatever.