MacBook Pro 2018 Draining Battery with closed lid

Hi everyone,

my Macbook Pro 2018 (15", 1TB, 16GB, Mac OS High Sierra 10.13.6) drains battery massively when the lid is closed.

When I turn down my Mac at night closing the lid with around 80+% battery and return in the morning to open the Mac, my battery is always almost empty with below 15% battery left.

I don't know what is causing this. I tried closing the different programs before going to bed first thinking it was Safari or some tab in it, but it doesn't seem to be.

In the Energy Settings I disabled everything but putting the hard drive into sleep mode and reduce brightness in battery mode.

I also disabled to receive notifications in notification center while display is in sleep mode.

Terminal gives me the following result

pmset -g assertions

2018-08-31 09:58:42 +0200
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 691(sharingd): [0x000004100001888a] 00:00:08 PreventUserIdleSystemSleep named: "Handoff"
   pid 119(hidd): [0x000000bf00098258] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294968600.3"
  Timeout will fire in 300 secs Action=TimeoutActionRelease
No kernel assertions.
Idle sleep preventers: IODisplayWrangler

This doesn't help me at all.

I found this thread here: https://forums.macrumors.com/threads/psa-if-your-2015-or-2016-mbp-has-some-batte ry-drain-while-sleeping-here-is-the-fix.2026702/

Then I ran the following command and noticed that in the past days my MacBook has been busy all night long... unfortunately I can't make anything out of it to fix it. I just posted part of it as these keep repeating.

log show --style syslog | fgrep "Wake reason"


2018-08-31 05:15:23.889857+0200  localhost corespeechd[872]: [com.apple.corespeech:Framework] -[CSHostDaemon _getPowerAssertionIfWakenByVoiceTriggerNotFromS3Sleep] Wake reason is not VoiceTrigger or it wake from S0i
2018-08-31 05:15:25.098432+0200  localhost kernel[0]: (AppleTopCaseHIDEventDriver) [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)
2018-08-31 05:15:36.646633+0200  localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.RTC (Alarm)
2018-08-31 05:15:36.646634+0200  localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.RTC (Alarm)
2018-08-31 05:16:40.729360+0200  localhost corespeechd[872]: [com.apple.corespeech:Framework] -[CSHostDaemon _isWakeReasonVoiceTrigger] Wake reason: <private>
2018-08-31 05:16:40.729388+0200  localhost corespeechd[872]: [com.apple.corespeech:Framework] -[CSHostDaemon _getPowerAssertionIfWakenByVoiceTriggerNotFromS3Sleep] Wake reason is not VoiceTrigger or it wake from S0i
2018-08-31 05:16:42.020873+0200  localhost kernel[0]: (AppleTopCaseHIDEventDriver) [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)
2018-08-31 05:16:58.179516+0200  localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.RTC (Alarm)
2018-08-31 05:16:58.179518+0200  localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.RTC (Alarm)
2018-08-31 05:18:01.985476+0200  localhost corespeechd[872]: [com.apple.corespeech:Framework] -[CSHostDaemon _isWakeReasonVoiceTrigger] Wake reason: <private>

I also tried to reset the System Managing Controller (SMC) as described here: How to reset the System Management Controller (SMC) on your Mac - Apple Support

A Hardware Diagnosis, Restarting and pressing D, has not found any issues.

Has anyone experienced something similar or has a clue on how to fix this?

I never had this issue on my previous 13" MacBook Pro (late 2013) with pretty much the same software setup. When I closed the lid here at night and came back in the morning my Mac usually only lost like 2-3% of its charge, not more than 60%.

Would be great if there is a solution.

Many thanks, M