Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Spacecadet.jr

macrumors newbie
Feb 13, 2022
1
0
After updating to 12.2.1 my M1 Mac Mini started to wake by itself constantly. The Mini is in a small office so at first I didn't notice that it was actually waking from sleep all the time when not using it but I did notice that I started getting random notifications that my Apple Watch had unlocked the Mini even when not being close to the Mini (ie in a different room). Prior to updating to 12.2.1 my Watch only unlocked the Mini when I was already sitting at the desk or otherwise very close to the Mini - so working as expected.
I'm using a Logitech MX Ergo via Bluetooth and have just tried removing the Bluetooth pairing and use the Logitech Unifying USB receiver instead - this seems to have stopped the Mini from waking by itself!
I have Logitech Options installed.

PS: On a sidenote: After updating to 12.2.1 I've also have had trouble Airplay'ing from my Mini to a HomePod Mini - it works when the Mini has been restarted but after it's been in sleep-mode for some time it stops working. When playing a youtube video and selecting the HomePod Mini as output it pauses the video as when syncing and after a few seconds the HomePod Mini lights up and the video resumes but there is no sound...
So looks like Bluetooth is a bit buggy in 12.2.1 :confused:
 
Last edited:

Bucks_Fizz

macrumors member
Mar 18, 2018
57
17
Hi all. I am not sure if this is the same issue but this is my finding:

I have a Macbook M1 13" connected to an external monitor. After experiencing multiple wakeups, I switched off bluetooth, closed music and pressed the sleep button on the touchbar.(customised strip). When i closed the lid, 5 seconds later the external monitor came back on as though the mac is in clamshell mode. So definitely not a bluetooth issue for me.

However, when i put the machine to sleep by using the sleep option under the apple logo (not touchbar) and close the lid, the machine remains asleep. This only started happening after 12.2.

Any ideas or am i in a completely wrong thread? :rolleyes:
 

Sheppardhazemaze

macrumors newbie
Jan 28, 2022
3
0
Ich have had some progress with my problems and it might help you as well:

My M1 Mac Air didn't go to sleep anymore and because of this thread i thought it would be because of Monterey. So I downgraded to Big Sur - but still, my Mac didn't go to sleep. Then I found out, that my LG-Bluetooth-Adapter in the kitchen (for music) was continuously trying to connect to my mac, even after deleting it and resetting my bluetooth. So I unplugged it and: Sleep problem solved!

So there must me something like an old bluetooth protocol that wakes up the Mac (Still a mac's problem though!) That brought me to the idea, that the problems with my Trackpad (which was laggy) could have a similar problem: Our router had both 2,4 Ghz and 5,0 Ghz WiFi Connections activated. I deactivated the 2,4 Ghz Connection and the problem was gone as well.

So go and search for old devices that connect to your Mac. Maybe you'll be lucky.
 

indigodelta

macrumors newbie
Feb 28, 2022
1
0
Ich have had some progress with my problems and it might help you as well:

My M1 Mac Air didn't go to sleep anymore and because of this thread i thought it would be because of Monterey. So I downgraded to Big Sur - but still, my Mac didn't go to sleep. Then I found out, that my LG-Bluetooth-Adapter in the kitchen (for music) was continuously trying to connect to my mac, even after deleting it and resetting my bluetooth. So I unplugged it and: Sleep problem solved!

So there must me something like an old bluetooth protocol that wakes up the Mac (Still a mac's problem though!) That brought me to the idea, that the problems with my Trackpad (which was laggy) could have a similar problem: Our router had both 2,4 Ghz and 5,0 Ghz WiFi Connections activated. I deactivated the 2,4 Ghz Connection and the problem was gone as well.

So go and search for old devices that connect to your Mac. Maybe you'll be lucky.
This is exactly the problem I have too. I connected a bluetooth-enabled soundbar used mostly for my TV to my Mac and now, although I've deleted the connection, whenever I turn on my TV, my Mac wakes up. No amount of resetting of bluetooth on the Mac and the soundbar will get them to forget about each other. There needs to be a way for the Mac to not react to every Bluetooth noise it hears. That's way too sensitive.
 
Last edited:

ChildOfTheWW

macrumors member
Nov 7, 2014
36
18
Got the same issue. After going into sleep the screen always wakes up again after around 15 minutes. Problem seem to be my Logitech devices (MX Anywhere 2 and MX Keys Mini). Super annyoing.
 

robertjoe

macrumors member
Feb 17, 2022
41
55
I had faced this same problem with my MacBook Pro (2020) when I update it to 12.2.1. Computer often wakes up automatically from sleep mode.

I got solved this problem, I noticed that when I turned off my mac's Bluetooth the automatic wake up issue has gone, so I just turned off my internal Bluetooth and put my external USB Bluetooth dongle on an empty USB port. It works seamlessly and seems to be a good solution.

The good thing about the Hideez dongle is that it works with the Apple keyboard and Magic Mouse, as well as other BT devices.
 
  • Like
Reactions: lungbutter

benjaminv

macrumors newbie
Nov 29, 2010
2
2
Since someone tried 12.3 beta still with the issue i dont believe the recently released 12.3.1 will resolved the issue, although I did have reviewed the release note which mentioned bluetooth connection issue with certain peripherals.

I've done almost everything here and there till I removed permission that was given to Logi Options App under the system preferences > Security & Privacy > Input Monitoring > Logitech Options Daemons. I tend to record my full story here, and this has referred to everyone that contributes here.

The scenario:
Part 1, macOS removed advanced options where you can disable "Allow bluetooth devices to wake this computer" and so far there isn't an official command can trigger this in the terminal.

Part 2, in most cases, the OS was waken up by Logitech devices connected via bluetooth, where again in most cases, had the configuration app Logi Option installed.

The causes:
Due to Part 1, we are no longer able to force the waking up function shut
Due to Part 2, in particular, system preferences > Security & Privacy > Input Monitoring > Logitech Options Daemons option enables Logitech devices constantly interact with the OS therefore immediately wake it up when put to sleep (otherwise energy saving configurations will never execute)

The fix:
removed permission that was given to Logi Options App under the system preferences > Security & Privacy > Input Monitoring > Logitech Options Daemons. This will revoke customised shortcut on the devices' keys to default - I'd not to f... care about this as I do prefer my macbook to sleep.

One further step:
I eventually decided to completely removed the Logi Options App. And I can confirm my macbook stops having sleep issues.

Other things to know:
1. When computer is asleep, touching the keyboard keys or moving mouse does wake it up because scenario>Part 1 was not fixed by apple yet. For those carrying laptop and mouse together to commute, the advice is to power the mouse off before or immediately after putting laptop to sleep.
2. Without Logi Option App, some functions, for me, only the Previous / Next buttons stopped working as intended. The fix is to use a very light open sourced app called SensibleSideButtons. Just download from https://sensible-side-buttons.archagon.net and throw it somewhere that you can easily access to, when you do lose Previous / Next buttons.

Conclusion:
Logitech becomes complicated and a pain the ass these days.
 

golfnut1982

macrumors 6502a
Oct 12, 2014
543
1,383
Chicago, IL
By updating to the Logitech Option Plus Beta application, it seems to fix it. Before the beta, my screen would wake multiple times while I ate dinner. I'll keep an eye on it. Beta fixed it.
 
Last edited:

kaz219

macrumors member
May 8, 2006
36
6
Interestingly I am on macOS 12.3.1 and I sill have the issue: if I carry my macbook (MB Pro 15" 2017) in my backpack (sleeping, in theory) while using bluetooth headsets on with my smartphone, my macbook will get out of the backpack hot and with a significantly depleted battery. If I turn off bluetooth before closing the lid of the macbook, no issue, battery does not deplete, laptop is cold when getting it out of the backpack.
 
  • Like
Reactions: Flyview

creativesmith

macrumors member
Sep 28, 2011
64
49
Interestingly I am on macOS 12.3.1 and I sill have the issue: if I carry my macbook (MB Pro 15" 2017) in my backpack (sleeping, in theory) while using bluetooth headsets on with my smartphone, my macbook will get out of the backpack hot and with a significantly depleted battery. If I turn off bluetooth before closing the lid of the macbook, no issue, battery does not deplete, laptop is cold when getting it out of the backpack.

Same.
 

waterchill

macrumors member
Aug 19, 2016
38
7
I have a very similar issue on my MacMini M1. It wakes up always 30min after going to sleep. This happens one time till I wake the mini and go to sleep again.

With this command I have found:

log show | grep -i "wake reason"

2022-06-27 17:31:17.420300+0200 0x167ed Error 0x0 303 0 powerd: [powerd:sleepWake] PID 348 is not entitled to set wake reason

And with this command:

pmset -g assertions

Assertion status system-wide:

BackgroundTask 0
ApplePushServiceTask 0
UserIsActive 1
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
ExternalMedia 0
PreventUserIdleSystemSleep 1
NetworkClientActive 0

Listed by owning process:


pid 357(WindowServer): [0x0000002600098066] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle serviceID:100000b0d name:AppleHIDKeyboardEve product:Magic Keyboard with eventType:3"

Timeout will fire in 2700 secs Action=TimeoutActionRelease

pid 380(coreaudiod): [0x00002db7000180aa] 00:33:32 PreventUserIdleSystemSleep named: "com.apple.audio.BuiltInHeadphoneOutputDevice.context.preventuseridlesleep"

Created for PID: 641.

pid 348(bluetoothd): [0x0000358000018de6] 00:00:19 PreventUserIdleSystemSleep named: "com.apple.BTStack"

pid 348(bluetoothd): [0x00002d8c00098b01] 00:34:14 UserIsActive named: "Bluetooth HID Activity"

Timeout will fire in 645 secs Action=TimeoutActionRelease

pid 348(bluetoothd): [0x00002d9a00098bee] 00:34:01 UserIsActive named: "Bluetooth LE HID Activity"

Timeout will fire in 659 secs Action=TimeoutActionRelease

pid 303(powerd): [0x00002d8c00018b03] 00:34:14 PreventUserIdleSystemSleep named: "Powerd - Prevent sleep while display is on"

pid 641(Music): [0x00002db700018c5d] 00:33:32 PreventUserIdleSystemSleep named: "com.apple.Music.playback"

Kernel Assertions: 0x8=BT-HID

id=510 level=255 0x8=BT-HID creat=27.06.22, 14:00 description=com.apple.driver.IOBluetoothHIDDriver owner=AppleHSBluetoothDevice

id=511 level=255 0x8=BT-HID creat=27.06.22, 13:51 description=com.apple.driver.IOBluetoothHIDDriver owner=AppleHSBluetoothDevice

So PID 348 is Bluetooth LE HID Activity

I'm using MX Master 3, an Apple mouse and an Apple Keyboard with fingerprint. The solutions here cannot use because there is no lid to wake up, so I have to always press the button on mini. If power off all 3 devices, no change. Any suggestions?
 

milleron

macrumors regular
Oct 23, 2014
102
18
Columbus, Ohio
Since someone tried 12.3 beta still with the issue i dont believe the recently released 12.3.1 will resolved the issue, although I did have reviewed the release note which mentioned bluetooth connection issue with certain peripherals.

I've done almost everything here and there till I removed permission that was given to Logi Options App under the system preferences > Security & Privacy > Input Monitoring > Logitech Options Daemons. I tend to record my full story here, and this has referred to everyone that contributes here.

The scenario:
Part 1, macOS removed advanced options where you can disable "Allow bluetooth devices to wake this computer" and so far there isn't an official command can trigger this in the terminal.

Part 2, in most cases, the OS was waken up by Logitech devices connected via bluetooth, where again in most cases, had the configuration app Logi Option installed.

The causes:
Due to Part 1, we are no longer able to force the waking up function shut
Due to Part 2, in particular, system preferences > Security & Privacy > Input Monitoring > Logitech Options Daemons option enables Logitech devices constantly interact with the OS therefore immediately wake it up when put to sleep (otherwise energy saving configurations will never execute)

The fix:
removed permission that was given to Logi Options App under the system preferences > Security & Privacy > Input Monitoring > Logitech Options Daemons. This will revoke customised shortcut on the devices' keys to default - I'd not to f... care about this as I do prefer my macbook to sleep.

One further step:
I eventually decided to completely removed the Logi Options App. And I can confirm my macbook stops having sleep issues.

Other things to know:
1. When computer is asleep, touching the keyboard keys or moving mouse does wake it up because scenario>Part 1 was not fixed by apple yet. For those carrying laptop and mouse together to commute, the advice is to power the mouse off before or immediately after putting laptop to sleep.
2. Without Logi Option App, some functions, for me, only the Previous / Next buttons stopped working as intended. The fix is to use a very light open sourced app called SensibleSideButtons. Just download from https://sensible-side-buttons.archagon.net and throw it somewhere that you can easily access to, when you do lose Previous / Next buttons.

Conclusion:
Logitech becomes complicated and a pain the ass these days.
@Benjamininv
Thanks for this solution. It works for me, and it does allow the Logitech mouse to wake the Mac by moving and the Logitech MX Keys to wake it with a keystroke.
Importantly, I went through a very long exchange of many emails with a few tech support people at Logitech, and they said they've never heard of this problem. Likewise, although they tried to be helpful, they never came close to pinpointing the cause as you did. I give credit to Logitech support for trying diligently to get me an answer, but their complete and utter failure, lead me not to have any faith that any of them really know much about their own products.

Unlike you, I did not uninstall Logi Options because I didn't need to (at least so far"), but now, I'm wondering what functions might be lost by not allowing the Daemon to monitor keyboard input. Have you found any?
 

Flyview

macrumors member
Mar 20, 2018
68
20
Bringing this back from the dead to share my experience. I noticed my mid 2014 15" MBP was not sleeping while plugged in (iStat Menus graphs not going blank, staying warm, checking power usage at power source). This happened on MacOS Sonoma with OCLP.

I had a hunch it might have something to do with Bluetooth then found this thread. Tested while connected to either UTE-73BT (vehicle audio system) and Samsung Galaxy earbuds. If I disconnect from the device first, this doesn’t happen. The UTE-73BT keeps it awake indefinitely. With the buds it goes to sleep after the regular 30s, but you can wake it by tapping on the ear bud (and it doesn’t start any playback)! Took 01m:06s to go back to sleep.

Automated solution:

Disable BT when going to sleep, and re-enable when waking.

brew install sleepwatcher blueutil
echo "$(which blueutil) -p 0" > ~/.sleep
echo "$(which blueutil) -p 1" > ~/.wakeup
chmod 755 ~/.sleep ~/.wakeup
brew services restart sleepwatcher

After this it asks for access to keychain for github password!?
And then access to keystrokes from any application which I denied…
https://stackoverflow.com/questions...nts-to-access-key-github-com-in-your-keychain

It works… the only difference being you aren’t connected to the BT device upon waking back up like you would be without this.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.