We are experiencing abnormal battery drain during sleep on several machines that installed our product. The affected devices appear to enter and exit sleep repeatedly every few seconds, even though the system logs show no new wake request reasons or changes in wake timers.
Symptoms:
Battery drops ~1% every ~15–20 minutes overnight.
pmset -g log shows repeated "Entering Sleep" and "Wake Requests" events every few seconds.
Wake requests remain unchanged between cycles and are scheduled far into the future (i.e. 20+ minutes later), yet the log lines keep repeating.
On healthy machines, the same wake request entries appear only once every 20–30 minutes as expected, with minimal battery drop during sleep (~1% in 9 hours).
What we've checked:
No user activity (system lid closed, device idle).
No significant pmset -g assertions; only powerd and bluetoothd are holding expected PreventUserIdleSystemSleep.
pmset -g on affected machines shows sleep set to 0, likely due to sleep prevented by powerd, bluetoothd.
No third-party daemons are holding assertions or logging excessive activity.
Sample Logs from Affected Machine:
2025-06-28 21:57:29 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using Batt (Charge:76%) 3 secs
2025-06-28 21:57:31 Wake Requests [process=mDNSResponder request=Maintenance deltaSecs=7198 wakeAt=2025-06-28 23:57:29 ...]
2025-06-28 21:57:38 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using Batt (Charge:76%) 3 secs
2025-06-28 21:57:40 Wake Requests [process=mDNSResponder request=Maintenance deltaSecs=7198 wakeAt=2025-06-28 23:57:38 ...]
2025-06-28 21:57:47 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using Batt (Charge:75%) 3 secs
2025-06-28 21:57:49 Wake Requests [process=mDNSResponder request=Maintenance deltaSecs=7198 wakeAt=2025-06-28 23:57:47 ...]
The only change in logs is the wakeAt timestamp being slightly updated . The wake requests themselves (process, type, deltaSecs) remain identical. Yet, the system keeps entering/exiting sleep every few seconds, which leads to power drain.
We would appreciate your help in identifying:
Why the sleep/wake cycles are repeating every few seconds on these machines.
Whether this behavior is expected under certain conditions or indicates a regression or misbehavior in power management.
How we can trace what exactly is triggering the repeated wake (e.g., a subsystem, implicit assertion, etc.).
Whether there are unified log predicates or private logging options to further trace the root cause (e.g., process holding IO or waking CPU without explicit assertion).
We can provide access to full logs, configuration profiles, and system diagnostics if needed.