Ventura 13 Power Events

In the meantime I found a solution to get rid of the power events. By "I found" I mean actually I found this thread:

Reminders app waking mac from sleep - Apple Community

So I tried it!

Behaviour before the fix:

• "pmset -g sched" reports our beloved friends

[0] wake at 12/17/2022 00:41:44 by 'com.apple.alarm.user-visible-

com.apple.CalendarNotification.EKTravelEngine.periodicRefreshTimer'.

  [1] wake at 12/17/2022 19:23:54 by 'com.apple.alarm.user-visible-com.apple.acm

• "sudo pmset schedule cancelall"
• "pmset -g sched" -> all good!
• put Mac to sleep
• wake it up by keystroke
• "pmset -g sched" -> bad again

Now the fix:

"sudo pmset sched cancelall"

AND

"sudo chflags schg /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist"

"This prevents the system from updating the file and my MacBook no longer wakes to reminder events. Needles to mention that it prevents all scheduled system events like sleep, power-on and such."

"I recommend removing the flag before a system update:"

"sudo chflags noschg /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plist"

Behaviour AFTER the fix:

• "pmset -g sched" -> all good!
• put Mac to sleep
• wakeup Mac by keystroke
• "pmset -g sched" -> all good and hope it remains as it is...

Will see tomorrow what "pmset -g log" reports...

Good luck to all...

I've had sporadic wake events on the wife's iMac and the screen would light up multiple times a night. On Ventura, I am seeing these same wake events but in my wife's scenario it was a Logitech bluetooth mouse triggering the screen wakes. At first, I turned off the mouse before going to bed and that seemed to stop the frequent wake events. Recently I configured the mouse to use the Logitech bolt receiver instead of bluetooth and now it's not waking the screen at night. The Ventura scheduled events still fire but they are not fully waking the entire Mac. The screen stays off. The wife's Mac has an Apple Magic Keyboard that is bluetooth and that's not having an issue but the Logitech bluetooth mouse was the problem.

Others have commented about bluetooth being an issue. Seems the Apple Magic Mouse and Keyboard don't have the problem. But third party bluetooth mice have an issue.

I've tested on 3 other Ventura Macs and they all have the same calendar scheduled upkeep wake events. Mostly an hour apart there are a few events. I don't think these particular events are the problem. Look for anything else, especially bluetooth related. Or perhaps an external accessory such as a USB / USB-C hard drive.

Hi guys,

I am on Ventura 13.1, MBP M1 Pro 14. I followed this thread as I am getting crazy too with these "wake events" which are consuming 10% of battery every night. I tried pretty much everything that was suggested.

No success, the two schedules

com.apple.alarm.user-visible-com.apple.CalendarNotification.EKTravelEngine.periodicRefreshTimer

and

com.apple.alarm.user-visible-com.apple.acmd.alarm

always came back.

I found now that in calendar settings the three calendars that I had installed had a refresh option set on respectively Push and every 15 mins. I set the three of them on manually and for the moment the two schedule calls didn't reappear (few hours).

Not sure if this a solution, but I wanted to share with you, as I could share my frustration with you until now.

I have the same exact issue. However, these issues were occurring way before Ventura (Big Sur & Monterey). I read up on a few forums and the only [temporary] solution is to input a 'command' in the Terminal app. The two commands that have worked for me are:

1) sudo pmset schedule cancelall

2) sudo pmset -b tcpkeepalive 0

Hope this helps!

The fact that only you four are reporting the problem it probably isn't envy on Apple's radar.

Do you have these enabled in Settings?

Have you installed and run any "cleaning", "optimizing", "speed-up", anti-virus or VPN apps on your Mac?

Give this a try: boot into Safe Mode according to How to use safe mode on your Mac and test to see if the problem persists. Reboot normally and test again.

NOTE 1: Safe Mode boot can take up to 3 - 5 minutes as it's doing the following; 

• Verifies your startup disk and attempts to repair directory issues, if needed

• Loads only required kernel extensions (prevents 3rd party kernel/extensions from loading)

• Prevents Startup Items and Login Items from opening automatically

• Disables user-installed fonts 

• Deletes font caches, kernel cache, and other system cache files

NOTE 2: if you have a wireless keyboard with rechargeable batteries connect it with its charging cable before booting into Safe Mode. This makes it act as a wired keyboard as will insure a successful boot into Safe Mode.

com.apple.alarm.user-visible-com.apple.CalendarNotification.EKTravelEngine.periodicRefreshTimer

My only guess is it relates to calendar events with travel notifications set. That may wake the computer to refresh the time to depart. I tried to create an event with a travel time alert, but it didn't generate any wake events.

com.apple.alarm.user-visible-com.apple.acmd.alarm

I couldn't find anything on the internet or in my logs that referenced acmd.

You should be able to cancel them all using pmset in Terminal

pmset schedule cancel wake

or

pmset repeat cancel

None of these should be waking the Mac permanently. The wake events are to accomplish some task then let it go back to sleep. It is possible that whatever kicks on gets hung up and drains the battery, but that is not the intent of the wake events, so the scheduled wake events should not be the direct cause of any issues such as battery draining. If they always cause battery drain, use the Get Support links to talk to Apple support.

Make sure any Apps you have installed that were not installed by the Mac App Store have been updated but that they are also compatible with Ventura. There have been Apps such as Rogue Amoeba, Zoom, etc. that can cause these wake events due to a bug that was fixed in an update. Might need to look at the entire pmset.log around the time range of the issue to see if there's other earlier log entries that might clue you into the root cause.

May have gotten a clue.

terminal

pmset -g log | grep -A 5 "DarkWake"

2023-01-31 15:14:21 -0500 DarkWake            DarkWake from Deep Idle [CDN] : due to NUB.SPMI0.SW3 nub-spmi0.0x02 rtc bluetooth-pcie/ Using BATT (Charge:67%) 5 secs    

2023-01-31 15:14:21 -0500 WakeDetails         DriverReason:NUB.SPMI0.SW3 - DriverDetails:                                

DriverReason:nub-spmi0.0x02 - DriverDetails:                               

DriverReason:rtc - DriverDetails:                                          

DriverReason:bluetooth-pcie - DriverDetails:                               

2023-01-31 15:14:21 -0500 HibernateStats      hibmode=3 standbydelaylow=0 standbydelayhigh=0                                       4453      

--

2023-01-31 15:14:28 -0500 DarkWake            DarkWake from Deep Idle [CDN] : due to NUB.SPMI0.SW3 nub-spmi0.0x02 rtc wifibt bluetooth-pcie/ Using BATT (Charge:67%) 14 secs   

2023-01-31 15:14:28 -0500 WakeDetails         DriverReason:NUB.SPMI0.SW3 - DriverDetails:                                

DriverReason:nub-spmi0.0x02 - DriverDetails:                               

DriverReason:rtc - DriverDetails:                                          

DriverReason:wifibt - DriverDetails:                                       

DriverReason:bluetooth-pcie - DriverDetails:                               

--

2023-01-31 15:14:44 -0500 DarkWake            DarkWake from Deep Idle [CDN] : due to NUB.SPMI0.SW3 nub-spmi0.0x02 rtc wifibt bluetooth-pcie/ Using BATT (Charge:67%) 1 secs    

2023-01-31 15:14:44 -0500 WakeDetails         DriverReason:NUB.SPMI0.SW3 - DriverDetails:                                

DriverReason:nub-spmi0.0x02 - DriverDetails:                               

DriverReason:rtc - DriverDetails:                                          

DriverReason:wifibt - DriverDetails:                                       

DriverReason:bluetooth-pcie - DriverDetails:       

I've now shut bluetooth down. And will give it a retry.                        

I have some interesting findings.

I've not closed the tab with the person yet so will be detailed.

BTW, I did not use my MBP the usual time of 10am until 2pm, and wow down to 82%. Crazy.

After showing some logs,

A: The main reason its draining is cause of the apps running on the background.

But I only have Chrome opened, and even once I closed everything and still drain.

Q: Is it the Bluetooth waking it too? (This is to my concern only but maybe useful to some of you)

A: Yes that also contributes to the battery consumption. With 2 Bluetooth devices will definitely make significant changes.

Really annoying that I'll have to turn off Bluetooth from now on, and so will always have to open the lid to access the keyboard and go turn it on to use externals.

Q: What is this:

com.apple.alarm.user-visible-com.apple.CalendarNotification.EKTravelEngine.periodicRefreshTimer

A: Check your Notification Center, It has widgets hence the power usage.

So it's the widgets you guys!! Will remove them tonight and see. I have two (S and M) Calendar widgets.

Q: Could you just tell me if you know what this is? com.apple.alarm.user-visible-com.apple.acmd.alarm

A: Screen Time to do Power Event Wakes all night, so when its off it wont do those.

All this trouble, I'll give some of these a shot, but will just shutdown from now on.

So I noticed this too the past few days. I tried several things to stop the messages. The latest thing I have tried, is I turned off the schedule for focus on the mac. I had it syncing across all my devices. With that turned off on the mac (I told it not to share focus across my other devices, the Wake request messages appear to have stopped. I will leave it overnight and see what happens.

Just to cover all the bases, Under Battery-->Options, what do you have for Wake for Network Access? I have mine set to "Only on Power Adapter". Last night, just on battery, I only had a view Wake Requests. My battery level barely changed. You might try that just to see if it makes any difference. Worst case, it might be another data point.

Also, I just learned about this as well. Under System Information-->Hardware-->Power, you can see scheduled power events under Power Events. Not sure what it means yet, since I stopped all scheduled events, but I still see three of them.

Investigation continues.

I'm working on a MacPro 2019 running Ventura 13.1.

The machine had no sleep issues in Monterey 12.x.x, altough I had to shutdown the AddressBook SourceSync Service for proper sleep by executing

"launchctl unload -w /System/Library/LaunchAgents/com.apple.AddressBook.SourceSync.plist"

By doing so, the system was sleeping fine, without a single wakeup regardless how long the sleep time was.

In the last years, more and more interconnectivity features were implemented in MacOS which constatntly interacting with iPads, iphone, appleWatches and so on, applying wireless technology. Since I'm using the MacPro mainly for source code development and number crunching as my primary work horse, I wanted to get rid off all this stuff by switching off Bluetooth and Wifi, since I do not really use these features on this machine. All peripheral are wired. Printers are connected through wired ethernet. The office is professionally equipped to do this. So I think do not have any wireless communication or interference from the millions of iDevices out there.

Now with Ventura 13.1, I got this ugly power events, nobody seems to know who is actually scheduling this.

On this machine, I do not use Apple Calender, nor Contacts or anything from Apple pointing into the direction of

"com.apple.CalendarNotification.EKTravelEngine.periodicRefreshTimer".

In the meantime, I know when the mysterious power events are re-scheduled after clearing them with

"sudo pmset schedule cancelall":

Just put the Mac to sleep and immediately wake it up by a keystroke - and voila, you will have again your best two friends on your side, rescheduled at completely random times.

"pmset -g sched":

[0] wake at 12/16/2022 16:28:44 by 'com.apple.alarm.user-visible-com.apple.CalendarNotification.EKTravelEngine.periodicRefreshTimer'

 [1] wake at 12/17/2022 12:03:06 by 'com.apple.alarm.user-visible-com.apple.acmd.alarm'

I'm lazy to go through the previous messages, but I think I said some wake requests was from the Calendar widgets so if you remove all Calendars it should not have this Power Event. And the acmd is because of Screen Time being used. I have the Find this Mac feature on so it's a must. So in the end, I use Calendar widgets, and I use Find this Mac so the Power Events will stay. But yeah time to time I run the command to see and it does bother me that from time to time it wakes. Again, from the first few pages of this thread I mentioned SDXC and bluetooth being a problem too. In this logs, every hour there is like five wakes per hour. Imagine that but all night!

I can confirm this solved the problem.

I downloaded a nifty utility called Bluesnooze.

Once installed and running - problem solved.

Me seeing the exact same. Running on M1 MBP 14.

Why can't someone from Apple just come and fix it and done? Leaving us all looking around..

As some of you suggested:

sudo pmset schedule cancelall

In the terminal would clear it, and seems that why, but it just comes back again.