I am not really sure how to interpret the logs, but there are a lot of entries that look like
9/12/17 4:27:35.014 AM WindowServer[121]: WSSetTrackingAreaEnabled : Invalid tracking area 0x7fc3e7aa68e0
I also just tried putting it to sleep and it woke up again, and here are all the lines that were generated in that period of time:
9/12/17 4:32:47.927 AM WindowServer[121]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7fafd1d11cc0(2001)
9/12/17 4:32:47.943 AM WindowServer[121]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x7fafd1d11cc0(2001)
9/12/17 4:33:17.000 AM kernel[0]: PM notification timeout (pid 2972, iStatMenusDaemon)
9/12/17 4:33:18.858 AM apsd[63]: Unrecognized leaf certificate
9/12/17 4:33:22.000 AM kernel[0]: AirPort_Brcm43xx:
owerChange: System Sleep
9/12/17 4:33:23.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x7800 ****
9/12/17 4:33:23.000 AM kernel[0]: 0x1face000, 0x00000000 Intel82574L::setLinkStatus - not active
9/12/17 4:33:23.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
9/12/17 4:33:23.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x7800 ****
9/12/17 4:33:24.000 AM kernel[0]: Wake reason: EHC1
9/12/17 4:33:25.000 AM kernel[0]: AirPort_Brcm43xx:
owerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
9/12/17 4:33:25.000 AM kernel[0]: AirPort_Brcm43xx::checkInterfacePowerState: Check _pwrOffThreadCall!
9/12/17 4:33:25.000 AM kernel[0]: RTC: PowerByCalendarDate setting ignored
9/12/17 4:33:25.000 AM kernel[0]: Previous Sleep Cause: 5
9/12/17 4:33:25.000 AM kernel[0]: The USB device USB2.0 Hub (Port 5 of Hub at 0xfd000000) may have caused a wake by issuing a remote wakeup (2)
9/12/17 4:33:25.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
9/12/17 4:33:25.000 AM kernel[0]: 0x1face000, 0x00000000 Intel82574L::setLinkStatus - not active
9/12/17 4:33:25.000 AM kernel[0]: The USB device Keyboard Hub (Port 1 of Hub at 0xfd500000) may have caused a wake by issuing a remote wakeup (3)
9/12/17 4:33:25.000 AM kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0xfd510000) may have caused a wake by issuing a remote wakeup (3)
9/12/17 4:33:25.000 AM kernel[0]: full wake (reason 1) 211 ms
9/12/17 4:33:25.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Resume -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x7800 ****
9/12/17 4:33:25.398 AM WindowServer[121]: CGXDisplayDidWakeNotification [106498959503551]: posting kCGSDisplayDidWake
9/12/17 4:33:25.399 AM WindowServer[121]: handle_will_sleep_auth_and_shield_windows: Ordering out authw 0x0(0), shield 0x7fafd1d11cc0(2001) (lock state: 1)
9/12/17 4:33:25.399 AM WindowServer[121]: handle_will_sleep_auth_and_shield_windows: errs 0x0, 0x0, 0x0
9/12/17 4:33:25.000 AM kernel[0]: 0x1face000, 0x00000000 Intel82574L::setLinkStatus - not active
9/12/17 4:33:25.000 AM kernel[0]: 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
9/12/17 4:33:29.000 AM kernel[0]: Ethernet [Intel82574L]: Link up on en1, 100-Megabit, Full-duplex, Symmetric flow-control, Debug [796d,6f48,0de1,0200,45e1,4000]
9/12/17 4:33:29.000 AM kernel[0]: 0x1face001, 0x00000008 Intel82574L::setLinkStatus - active
9/12/17 4:33:29.430 AM configd[17]: LINKLOCAL en1: parent has no IP
9/12/17 4:33:29.438 AM configd[17]: network changed: v4(en1-:192.168.1.54) DNS- Proxy-
9/12/17 4:33:29.448 AM configd[17]: network changed: v4(en1+:192.168.1.54) DNS+ Proxy+ SMB
9/12/17 4:33:29.842 AM apsd[63]: Unrecognized leaf certificate
9/12/17 4:33:29.000 AM kernel[0]: Google Chrome He (map: 0xffffff806242cf00) triggered DYLD shared region unnest for map: 0xffffff806242cf00, region 0x7fff8fe00000->0x7fff90000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
9/12/17 4:33:34.000 AM kernel[0]: 0x1face000, 0x00000000 Intel82574L::timeoutOccurred - no link - reset the chipset once
9/12/17 4:33:34.000 AM kernel[0]: 0x1face000, 0x00000000 Intel82574L::setLinkStatus - not active
9/12/17 4:33:34.000 AM kernel[0]: 0x1face000, 0x00000000 Intel82574L::setLinkStatus - not active
9/12/17 4:33:35.000 AM kernel[0]: 0x1face000, 0x00000000 Intel82574L::setLinkStatus - not active
9/12/17 4:33:39.514 AM AirPlayUIAgent[233]: 2017-09-12 04:33:39.513727 AM [AirPlayUIAgent] Changed PIN pairing: no
9/12/17 4:33:39.528 AM AirPlayUIAgent[233]: 2017-09-12 04:33:39.527559 AM [AirPlayUIAgent] Changed PIN pairing: no
9/12/17 4:33:55.000 AM kernel[0]: PRT5::setPowerState(0xc169ac7ee923c88d, 0 -> 2) timed out after 30276 ms
9/12/17 4:33:57.158 AM ntpd[141]: ntpd: wake time set +0.822382 s
9/12/17 4:33:57.165 AM com.apple.time[184]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
I also installed iStat and here are the temperature readings. This is basically at idle (Chrome is all that's running).
[doublepost=1505206020][/doublepost]Ok, I have figured out that the waking up is strangely a result of one of my peripherals (a Korg Nanopad2 controller device). I'm not sure why this is all of a sudden causing a problem - I usually leave it plugged in and it's never done this before, but when I unplug that, the computer goes to sleep as it should, and it won't go to sleep with that plugged in...
Strangely, the computer itself also seems quieter when it wakes up, as though the fans aren't cranking as hard as they were. I have no idea why this device would cause the fans to work harder as it doesn't really DO anything except transmit MIDI data...