Scheduling Multiple Different Power States

Windows Power State Scheduling

The most robust method for scheduling power events in Windows is using the powercfg utility from the Command Prompt or PowerShell. This tool allows you to configure a timer-based wake event or a shutdown schedule directly through the OS power settings database.

Setting a Wake Timer

To schedule your computer to wake from sleep at a specific time, such as 06:00 AM every day, you must first enable wake timers globally and then set the specific timer. Open an elevated Command Prompt (Run as Administrator) and execute the following commands:

powercfg -waketimer enable
powercfg -setdcvalueindex SCHEME_CURRENT SUB_NONE SUB_SLEEP WAKEALARM 1
powercfg -setacvalueindex SCHEME_CURRENT SUB_NONE SUB_SLEEP WAKEALARM 1
powercfg -setactive SCHEME_CURRENT

These commands modify the active power scheme to allow wake alarms when running on battery or AC power. If you need to schedule a specific one-time wake event, you can use the -systimer flag with a timestamp, though the global enable approach is more common for recurring tasks. Note that modern standby features in newer Windows versions may override these traditional timers; if your machine does not wake, check the "System Settings" within the Power Options GUI to ensure "Allow wake timers" is checked.

Scheduling Shutdown

If your goal is to shut down the system automatically, you can use the standard Windows Task Scheduler combined with the shutdown command. Create a new task, set the trigger to your desired time, and use the action shutdown /s /t 0. This bypasses the need for complex power scheme manipulation and is often more reliable for simple shutdown schedules.

macOS Sleep and Wake Scheduling

macOS provides the pmset command-line utility to manage power management settings. While the graphical Energy Saver preferences offer basic sleep intervals, pmset allows for precise scheduling of sleep, wake, and restart events.

Configuring Daily Sleep and Wake

To set your Mac to sleep at 11:00 PM and wake at 7:00 AM every day, open Terminal and run the following command:

sudo pmset repeat wakeorsleep MTWRFSU 23:00:00 07:00:00

The repeat keyword defines a recurring schedule. The string MTWRFSU stands for Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday, effectively enabling this schedule for all days of the week. You can customize this string to exclude weekends by using MTWRF for weekdays only. After running the command, verify the configuration by typing pmset -g, which will display the current power management settings including the repeat schedule.

Disabling Scheduled Power Events

If you need to stop scheduled wake or sleep events, you can clear them using:

sudo pmset repeat cancel

This ensures that no background daemons are interfering with manual power actions. Remember that macOS may prevent waking from sleep if the lid is closed on a laptop unless "Wake on LAN" or similar network access options are explicitly enabled in System Preferences, which can sometimes conflict with strict scheduling scripts.

Linux Systemd and Cron Automation

Linux offers two primary approaches for scheduling power states: using the traditional cron daemon or the modern systemd timer units. Both methods require root privileges to execute power management commands like systemctl suspend.

Using Cron for Simple Schedules

Cron is widely available and easy to configure for simple daily tasks. To edit the crontab for the root user, run sudo crontab -e. Add a line to suspend the system at midnight:

0 0 * * * /usr/bin/systemctl suspend

This entry tells cron to execute the systemctl command at minute 0 of hour 0 every day. Ensure that the path to systemctl is correct for your distribution; you can find it using the which systemctl command. Cron jobs run with the environment of the root user, so they do not require interactive authentication, making them suitable for unattended server or desktop automation.

Using Systemd Timers

For a more integrated approach, you can create a systemd service unit and a corresponding timer unit. First, create a file /etc/systemd/system/suspend.service:

[Unit]
Description=Suspend System
[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl suspend

Then, create /etc/systemd/system/suspend.timer:

[Unit]
Description=Daily Suspend Timer
[Timer]
OnCalendar=*-*-* 00:00:00
Persistent=true
[Install]
WantedBy=timers.target

Enable and start the timer with sudo systemctl enable --now suspend.timer. Systemd timers are generally preferred over cron for system-level tasks because they handle missed runs gracefully (via Persistent=true) and integrate better with the system's logging and dependency management.

Compatibility and Cross-Platform Considerations

When implementing these schedules, consider the physical hardware constraints. For instance, if you are managing a KVM switch scenario where monitors change inputs, ensure that the power state change does not leave a ghost frame on the display, which can confuse input switching logic. Additionally, always test your configurations during non-critical hours to avoid data loss from unexpected suspensions.

While the tools described above are standard, some enterprise environments may enforce group policies that override local power settings. In Windows, check the Local Group Policy Editor under Computer Configuration > Administrative Templates > System > Power Management. In Linux, check if logind is configured to ignore certain idle timeouts. These overrides can render your scheduled tasks ineffective if not accounted for in your deployment strategy.

Frequently Asked Questions

Why does my Windows PC not wake up at the scheduled time?

This usually happens because wake timers are disabled in the power plan settings or due to Fast Startup interference. Ensure that "Allow wake timers" is enabled in both Battery and Plugged-in settings within the Control Panel. Additionally, disable Fast Startup in the Power Options to ensure a clean boot cycle upon waking.

Can I schedule different power states for weekdays and weekends on macOS?

Yes, by modifying the day string in the pmset repeat command. Use MTWRF for Monday through Friday and SAT or SUN for weekend-specific schedules. You can define multiple repeat entries with different times by running the command again with a new schedule, as each call adds to the list of repeat events.

Is it safe to use sudo systemctl suspend in a cron job?

It is safe provided that any unsaved work is handled beforehand, as the command immediately suspends the system. Ensure that your cron job runs with sufficient privileges and that no other processes prevent suspension. It is recommended to log out users or notify them before the scheduled time to prevent data loss.

How do I verify that my Linux systemd timer is active?

You can check the status of the timer by running systemctl status suspend.timer. This will show whether the timer is enabled, when it last fired, and when it is next scheduled to fire. If it is not working, check the journal logs using journalctl -u suspend.service to see if the underlying service encountered errors during execution.

Do these power schedules affect battery life on laptops?

Properly scheduled sleep and wake cycles can improve battery life by ensuring the device sleeps during periods of inactivity. However, frequent wake-sleep cycles can increase wear on the battery compared to staying fully asleep. On macOS, the pmset defaults include smart sleep features that optimize this balance, while on Linux, you may need to tune logind idle delays to achieve optimal efficiency.