MacBook Air M4 immediately wakes after going to sleep in clamshell mode – USB/HID/Bluetooth?
Hi,
I’m trying to find the cause of a very strange sleep/wake problem with my MacBook Air M4.
Setup
- MacBook Air M4 15.3"
- macOS 26.6
- Lenovo ThinkVision T27QD-4v external monitor
- MacBook connected to the monitor with one USB-C cable
- Monitor’s USB hub is used for Logitech peripherals
- Logitech MX Master 3S
- Logitech MX Keys S
- Both Logitech devices are currently connected through one Logitech Bolt receiver plugged into the monitor’s USB-A hub
- No external USB audio adapter currently connected
Problem
When the MacBook is in clamshell mode and I choose Apple menu → Sleep, it sometimes goes black for about one second and then immediately wakes again.
It is intermittent: sometimes it sleeps normally, sometimes it wakes immediately.
I have already ruled out some simple causes:
- With the Logitech Bolt receiver completely disconnected, the MacBook reliably went to sleep several times when opened and using the built-in trackpad.
- Bluetooth-only operation also worked when the MacBook was open.
- However, in clamshell mode, using the Bluetooth MX Master to initiate sleep could again result in an immediate wake.
- I therefore disabled the Bluetooth wake setting experimentally, but the problem did not disappear completely.
- I then connected both Logitech devices back to the same Bolt receiver. The problem is still intermittent.
- The USB audio adapter has also been removed for the current tests.
I also created a keyboard shortcut (Option + Command + R) to trigger sleep, so the mouse itself is not necessarily involved in initiating sleep.
Relevant system information
pmset -g custom shows normal sleep settings (sleep 1, hibernatemode 3, etc.).
pmset -g assertions previously showed Bluetooth/HID activity and the monitor's USB hub.
Most interestingly, the wake logs show two different wake paths:
Bluetooth:
Wake from Deep Idle ... due to ... bluetooth-pcie/HID Activity
and, after switching back to the Bolt receiver:
USB:
Wake from Deep Idle ... due to ... USB2_wake ... /UserActivity Assertion
There are also repeated entries such as:
DarkWake to FullWake ... due to HID Activity
So it appears that both Bluetooth HID and USB HID activity can be involved, although I cannot determine which physical device is actually generating the wake event.
Question
Does anyone know how to identify the exact device or subsystem responsible for these wake events?
Could this be a macOS 26.x / Apple Silicon / clamshell issue involving HID devices, a USB-C monitor hub, or external input devices?
I am particularly interested in a way to identify the actual wake source from the macOS logs, rather than doing dozens of trial-and-error tests.
Thanks!
MacBook Air 15″, macOS 26.6