Capture a readable time window
Run the command in Terminal after an unexpected wake or a suspected sleep-drain interval, then search the output for the dates and events you are investigating. The local pmset manual describes this log as a history of sleeps, wakes, and other power-management events for administrative and debugging use. Keep the original output if you may need to compare it later.
A sleep entry, a normal wake, and a dark wake are different states that can occur in the same broad period. A wake reason is a clue about what the system recorded, not proof that the named component consumed a specified amount of battery. Check the surrounding timing, battery state, schedules, and active assertions.
pmset -g logPair logs with other observations
Use pmset -g assertions to see current assertion state and pmset -g sched to see scheduled events. Apple recommends checking sleep settings, network access, sharing, connected devices, and Activity Monitor when a Mac wakes unexpectedly. That broader path reduces the chance of changing an unrelated setting based on one log line.
Do not post unredacted logs publicly. They may contain timestamps, device and service details, or other context you do not intend to share. Trim a report to the relevant window and remove personal information before sending it to support.
pmset -g assertions
pmset -g schedUse WattGuard for session comparison
WattGuard organizes pmset-derived sleep history into sessions and compares a session with a median of prior sessions. It can retain wake reasons, charge change, and completed blockers locally for a clearer timeline. It does not turn a wake reason into a causal allocation, and it cannot repair the underlying macOS behavior.