Remote PC power-on with Tasker and Wake on LAN

Android Guides » Android Apps » Remote PC power-on with Tasker and Wake on LAN

If you've ever thought, "I wish I could turn on my PC from my phone or while I'm away from home ," this article is for you. With a good combination of Wake on LAN (WoL) and Tasker, you can do just that: check if your computer is on and, if it isn't, wake it up automatically, both on your local network and over the internet.

We'll take a step-by-step look at how all this works internally, what hardware you need, how to configure it in BIOS/UEFI, Windows 10 and Windows 11, your router and network , and how to integrate it with Tasker and Android plugins (like Wake on LAN WAN or even voice assistants like Alexa and Google Assistant). You'll get a very comprehensive guide to building a solid and secure system, leaving no stone unturned.

What is Wake on LAN and how does the “magic pack” work?

Wake on LAN (WoL) is a network standard that allows a computer to be remotely started or woken up when it is logically powered off, in sleep mode, or in hibernation. The key lies in a special message called a Magic Packet , which is sent over the network and contains the MAC address of the target computer repeated several times.

This Magic Packet is simply a network frame with a very specific format: it includes 6 bytes with a value of 255 (0xFF) followed by 16 repetitions of the target MAC address . The packet is usually sent to the local network's broadcast address, so all devices "listen" to it, but only the one with that specific MAC address reacts.

Even though the PC is "off," the network card actually maintains a low-power mode to continue listening for the Magic Packet. When it detects it, it sends a signal to the motherboard or power supply, and the power-up process begins just as if you had pressed the power button.

For WoL to work, several hardware and network conditions must be met: the motherboard, network card, and ATX power supply must support it, the computer must continue to receive minimum power, and the network infrastructure (router, switches, etc.) must allow WoL packets to pass to the appropriate interface.

Hardware requirements for using Wake on LAN

Before you start configuring Tasker and sending packets like there's no tomorrow, it's a good idea to check that your computer meets the minimum hardware requirements for WoL. The good news is that virtually any relatively modern PC already meets them.

First, you need an ATX power supply , which is the current standard. Older AT power supplies (with a large physical switch connected directly to the unit) are incompatible because when you turn off the computer, they completely cut off the power, leaving nothing "alive" to respond to a network signal.

ATX power supplies, on the other hand, always keep certain lines active, such as the +5V standby and the 3,3V CPU supply , and the power button is simply a push button connected to the motherboard. This allows the motherboard to receive a power-on command via software, including Wake-on-LAN.

A network card compatible with Wake-on-LAN (WoL) is also essential . In modern systems, this is usually the Ethernet adapter integrated into the motherboard, which communicates via PCIe and already includes WoL support without additional cables. Older PCI cards may have a 3-pin connector to physically connect the network interface card (NIC) to the motherboard for wake-up functionality.

The motherboard, of course, must be an ATX board or similar with ACPI power management support and Wake on LAN or Wake on PCI/PCIe options that can be enabled in the BIOS/UEFI. Most modern motherboards include this; if you have any doubts, you can check the manual or the manufacturer's website.

Finally, with laptops you need to be aware of some limitations: many laptops reduce or disable Wake-on-LAN when running on battery power alone , and some models don't support Wake-on-LAN from a powered-off state at all. In these cases, it's usually necessary to have the laptop plugged into a power outlet for Wake-on-LAN to work from sleep or hibernation.

ACPI power states and which mode to leave the PC in

The ACPI standard defines several power states (S0 to S5) that determine what remains active when the computer is "powered off." Understanding these states helps in correctly configuring the BIOS for Wake-on-LAN (WoL).

• S0: equipment powered on and 100% operational.
• S1: light low power mode; CPU stopped but RAM and other components continue to be powered.
• S2: similar to S1, but the CPU is completely off.
• S3: suspend mode (STR, Suspend To RAM); only the RAM and a few circuits remain active.
• S4Hibernation; the contents of RAM are saved to disk and the system appears to be off.
• S5: complete logical shutdown; the system is off, but the ATX power supply maintains the standby line.

For WoL, it is common to work with the S3 (suspension) state or, in many modern computers, even with S5 (logical shutdown) , provided that the BIOS and network card are configured to accept Magic Packets in those states.

Enable Wake on LAN in BIOS or UEFI

The first serious step is to enable WoL in the motherboard's BIOS/UEFI . Without that, even if you activate it in Windows and send packets from your phone, the PC won't recognize it.

To enter BIOS/UEFI, you must restart your computer and press the corresponding key immediately after startup, usually Delete, F1, or F2 depending on the manufacturer. Once inside, you need to locate the power options section, which is often called something like Power Management, Power Options , or similar.

Within that menu, you should see an option that refers to WoL, such as Wake on LAN, Wake Up On LAN/Ring, Resume by LAN, Power On by PCI-E , or something similar. The name varies from BIOS to BIOS, but the idea is the same: to allow a network device to wake the system.

You just need to change that option from Disabled to Enabled , make sure that ACPI power management mode is active (on many boards it is recommended to leave it on S3 (STR) ) and save the changes before exiting so that the configuration is applied.

Configure Wake on LAN in Windows 10 and Windows 11

With the BIOS now configured, it's time to prepare the operating system. The process is very similar in both Windows 10 and Windows 11 , and there are two main areas to consider: configuring the network card and the power options.

Enable WoL and Magic Packet on the network adapter

In Windows 10, you can open Device Manager from the Start menu (by searching for its name) or from Control Panel > System > Device Manager. Once there, expand the Network adapters section and locate the interface you will use for WoL, ideally the wired Ethernet port , which is where WoL has the best support.

Right-click on the adapter and select Properties . Then go to the Advanced tab and look for parameters related to Wake-on-LAN (WoL), such as Wake on Magic Packet, Wake on LAN, Wake Up on ARP Ping, and Wake Up on Link Change , depending on your network card driver.

At the very least, you should ensure that Wake on Magic Packet is enabled. If your card offers more specific WoL settings, you can enable or adjust them to your needs; in some cases, it's advisable to disable options like "Wake Up on Link Change" if you're experiencing too many false wake-ups.

Next, switch to the Power Management tab for the same adapter. There, it's important to check the boxes for "Allow this device to wake the computer" and, highly recommended, " Allow only one Magic Packet to wake the computer " to minimize accidental wake-ups from normal network traffic.

For some Realtek cards or other manufacturers, it may be necessary to update the drivers by downloading them from the official website, since the ones that come with Windows by default do not always show all the advanced WoL options.

Enable WoL in Windows 11

In Windows 11, the procedure is virtually identical . From the Start menu, search for "Device Manager," open it, go to Network adapters, and repeat the steps exactly: Ethernet adapter properties, Advanced options to enable Wake on Magic Packet , and Power Management tab with the wake-up boxes checked.

The main difference between Windows 10 and 11 isn't so much in Wake-on-LAN (WoL) as it is in the Network Settings interface , but at the driver and adapter options level, the menus are the same. If you do it correctly, you'll be able to use the same network card to wake the PC in either version.

Configure the network: static IP, ARP, and router

For Wake on LAN to work properly on a local network and, above all, to be able to do Wake on WAN (from the Internet) , it is essential to organize the network part: IP addresses, router ARP table and port openings, paying close attention to security.

Assign a static IP address or use static DHCP

Wake-on-LAN (WoL) relies on sending a packet to a specific IP address and MAC address, so it's best if the computer being woken up always has the same private IP address . You can do this in two ways: manually assigning an IP address in Windows or using Static DHCP on your router to always "reserve" the same IP address for your PC's MAC address.

The second option is usually the most convenient and straightforward. By accessing your router's settings, in the DHCP server section , you can typically add a reservation where you enter your network card's MAC address and the IP address you want to assign (for example, 192.168.1.130). From then on, the router will always assign that IP address to your computer.

Wake on LAN on local network

Within your own network (home WiFi/Ethernet), it's very easy: all you need is a stable connection between the device sending the Magic Packet and the PC receiving it . Many Wake-on-LAN (WoL) apps on Android allow you to scan the network to detect PCs, save their MAC and IP addresses, and wake them up whenever you want.

Some advanced routers (such as the recent AVM FRITZ!Box or ASUS models ) even have dedicated menus for sending Magic Packets directly from the router's web interface, without needing external apps. On the FRITZ!Box, for example, you can access the local network section, select the device, and use the "Activate computer" button.

Wake on WAN: turn on your PC from the Internet

The interesting (and delicate) part is waking up the PC via the internet . This involves port forwarding, the router's ARP table, and, above all, security.

What actually happens is that when you send a Magic Packet from outside, your router receives it first and then has to forward it across the local network to the PC's IP address. If the router doesn't know which MAC address corresponds to that IP address (because the computer is turned off and no longer responds to ARP requests), the packet can get lost along the way.

That's why many tutorials recommend configuring a static ARP entry on the router , associating the PC's static IP address (for example, 192.168.1.130) with its MAC address (for example, 00:4F:4F:4F:4F:4F) on the router's LAN interface. On some models (like certain Zyxel routers), this is done via Telnet or the command-line interface (CLI) with commands like ` ip arp add 192.168.1.130 ether 00:4F:4F:4F:4F:4F enif0 .`

The problem is that many ARP tables are volatile and are cleared when the router restarts. To avoid this, some firmware allows you to edit a boot configuration file (for example, autoexec.net on Zyxel routers ) and add the ARP command and any other necessary commands there, so that they are executed automatically every time the router is powered on.

Ports, DynDNS and security

Traditionally, opening UDP port 7 or 9 on the router has been used, redirecting that traffic to the PC's internal IP address to allow Magic Packets to enter from outside. This is usually combined with a dynamic DNS service (DynDNS, No-IP, etc.) that gives you a static domain name (like mydomain.no-ip.biz) pointing to your changing public IP address.

However, directly opening these ports to the outside world is a bad security practice . It leaves your network vulnerable to scans and potential attacks, and while a Magic Packet attack alone doesn't grant system access, it can become a gateway for abuse and brute-force attacks when combined with other services.

The truly secure way to implement Wake-on-WAN is to use a VPN as an intermediary layer. You configure a VPN server (WireGuard, OpenVPN, etc.) on your router or a device within the network (Raspberry Pi, for example), first connect to that VPN from your mobile device or laptop, and then, within the VPN tunnel, send the Magic Packet to your PC's private IP address. This way, you avoid exposing WoL ports to the internet.

Integrate WoL with Tasker and Android

Once your PC is working well with Wake-on-LAN (WoL) over a local network, the fun begins: automating everything with Tasker from your Android phone. Thanks to Tasker and certain plugins, you can create profiles that check the computer's status and turn it on only when needed, or even provide a custom tile in the quick settings panel.

Check if the PC is turned on with Tasker

A very simple way to find out if a device on your network is powered on is to use a ping from Tasker and process the result. You can create a task with a "Run Shell" action that launches, for example:

ping -c 3 192.168.1.2

By storing the output in a variable (for example , %pingresult ) and allowing it to continue even if there is an error. Then, with an If condition, you check if the output text contains something like “100% packet loss” . If so, you assume the PC is off; if not, that it is on.

For example, you can do something as simple as displaying a "It's Off" flash if there's 100% packet loss, or "It's On" otherwise. From there, you know the state of the device and can decide whether or not to initiate Wake-on-LAN.

Wake up your PC with WoL plugins for Tasker

To send Magic Packets from Android, there are several apps and plugins. One of the most popular is Wol Wake on Lan Wan , available for free on the Play Store and with direct Tasker support. The general workflow would be:

• Install the WoL app and add a new server with the PC you want to turn on.
• Set a name for it, enter the MAC address, internal IP (or external IP with DynDNS) and leave port 9 as the default if you have no reason to change it.
• In Tasker, create a task with an action Plugin > WoL Wake on Lan Wan > Configure by selecting the server/PC you created.

When you perform that task, the mobile phone sends the Magic Packet and, if everything is configured correctly in BIOS, Windows and router, the PC should boot or wake from sleep in a few seconds.

The interesting thing is that you can combine the ping and Wake-on-LAN (WoL) functions into a single logic: if the ping fails, then send a WoL command ; if the ping is successful, do nothing. This prevents you from sending unnecessary packets and ensures you don't force a startup if everything is already working.

Tiles, notifications, and voice assistants

Tasker takes usability a step further. You can create a Quick Settings Tile on Android 11+ to turn on your PC with a single tap, without even opening the app. If your Android version doesn't fully support custom tile creation, you can use AutoNotification to create a persistent button in the notification bar that triggers the Wake-on-LAN (WoL) task.

Furthermore, if you combine Tasker with plugins like AutoVoice or integrations with Alexa and Google Assistant, you can even turn on your PC by saying a phrase like " Alexa, turn on the computer " or "OK ​​Google, wake up the PC." The voice command would trigger the associated Tasker profile, and Tasker would handle pinging and sending the Magic Packet.

If that weren't enough, you can also expose a simple web interface or remote access with solutions like Splashtop, AnyDesk, TeamViewer or Windows Remote Desktop, combined with WoL: first you turn on the PC with Tasker or the WoL app and, when it is already active, you connect via remote desktop.

Wake on LAN with Splashtop, TeamViewer, and other remote software

Beyond Tasker, many professional remote access solutions incorporate direct support for WoL, allowing you to manage computers without having to leave them powered on 24/7.

For example, Splashtop integrates Wake on LAN into several of its plans for Windows and Mac. It allows you to wake a computer that is turned off, in sleep mode, or in hibernation (in the case of Windows), or a Mac that is asleep, provided the BIOS, network, and power conditions we've discussed are met.

From the Splashtop app or web console, you can view a list of your registered devices and, if one appears as offline, use the "Activate" option to send the WoL command. The idea is exactly the same: a Magic Packet directed to the device's MAC address, but managed transparently by the software.

TeamViewer, AnyDesk, and other remote desktop programs also include built-in Wake-on-LAN options , sometimes relying on other PCs powered on within the same network or on compatible routers. This greatly simplifies remote work, remote technical support, or managing fleets of PCs without leaving everything powered on permanently.

Practical uses of WoL at home and in business

The beauty of WoL is not only the convenience of not having to get up from the sofa, but also the practical applications it has in everyday life , both in domestic and professional environments.

At home, you could have your desktop PC with shared drives and various services , and use Wake-on-LAN (WoL) to turn it on only when you need to access a file , a movie, or a virtual machine. By combining this with Tasker or your router, you could turn it on from your mobile device just before arriving home, or when you're in another room.

In businesses or educational institutions, IT teams can schedule maintenance, updates, and patches outside of business hours by waking PCs via Wake-on-LAN, applying the tasks, and shutting them down again when finished. This reduces energy consumption and avoids having dozens or hundreds of computers running all night.

It is also very useful for ensuring business continuity in situations where physical access to the office is unavailable (disasters, restrictions, etc.). As long as there is power and connectivity, a critical server or workstation can be remotely powered on and accessed via remote desktop.

Another interesting point is the environmental and economic impact : by not having to leave equipment switched on "just in case", both the electricity bill and the wear and tear of components are reduced, prolonging the life of the devices and reducing the carbon footprint.

Security risks and best practices with Wake on LAN

WoL itself does not open a session or give you direct access to the system, but a bad configuration can create security holes , especially when you try to use it carelessly over the Internet.

The main problem is opening UDP ports 7 or 9 directly on the router so that anyone outside can send packets to your network. Although these ports are only intended for Magic Packets, in practice you're exposing your network to scans and potential abuse , and combined with other poorly configured services, this can be a bad idea.

Best practices for protecting WoL involve several measures: enabling it only when you really need it, restricting it to secure internal networks or VPN tunnels , using network segmentation (VLANs) if it is a corporate environment, applying MAC address filtering on the router when possible, and monitoring network logs for suspicious activation attempts.

In routers and solutions like the FRITZ!Box or certain ASUS models that integrate WoL, the Magic Packet is typically sent from the router's secure interface or its official app, without opening WoL ports to the outside world. This approach is much more advisable than the classic uncontrolled port forwarding.

Alternatives and complements to Wake on LAN

Your network card or motherboard might not support Wake-on-LAN (WoL), or you might simply not want to deal with BIOS, ARP, ports, and the like. In those cases, you have some interesting alternatives that allow you to turn on your PC remotely or without physically accessing the power button.

One option is to replace the network card with a modern one that supports Wake-on-LAN (WoL) , which is relatively inexpensive if it's an internal PCIe NIC. Alternatively, you could use a USB network adapter with WoL if you only need it occasionally and don't want to open your PC. Many current network cards offer improved performance and include full driver-level WoL support.

Another option is small WiFi-enabled physical actuators that attach to a button and press it for you (the typical "push-button robots"). They are controlled via an app or voice assistants like Alexa, Siri, or Google Home and act, literally, as if you were pressing the power button on the tower.

You can also complement all of this with a smart plug to control the power to your PC or other equipment. It's not equivalent to Wake-on-LAN (if you abruptly cut the power, you risk improperly shutting down the system), but it can be useful for restarting a frozen router or cutting power to certain devices when they're not in use. As long as you use it responsibly and not as a substitute for a controlled shutdown, it can be a valuable addition.

By properly combining Wake on LAN, a solid BIOS/Windows configuration, a well-tuned router, and the power of Tasker , you can set up a very convenient system for remotely powering on your PC securely, reliably, and almost seamlessly: from an Android tile, a voice command, a remote desktop app, or even a corporate VPN portal, your computer will go from sleep to ready to work without you having to touch a single physical button. Share this information so more users can learn about it.