Wake your PC remotely with Alexa (away from home)

"Pure" Wake-on-LAN has a historical limit: it only works inside the local network. Magic packets are UDP broadcasts that the router doesn't forward to the WAN without specific configuration. To wake your PC from outside the home, traditional solutions require port-forwarding, a static public IP, and often DynDNS — a fragile setup that with many ISPs isn't even possible (CG-NAT, double NAT).

SayBoot solves this natively with a cloud relay: a permanent channel between the Alexa cloud and your network segment that doesn't require opening ports on the router.

The problem with "pure" remote WoL

Wake-on-LAN is designed to send the magic packet as a UDP broadcast on the subnet where the powered-off PC sits. To make it work from the internet:

1. Your router needs a static public IP (or DynDNS). Many ISPs assign dynamic IPs and some use CG-NAT, where even this doesn't work.
2. On the router you have to open a UDP port (typically 9) in port-forwarding towards the broadcast address of your LAN. Consumer routers often don't allow broadcast forwarding.
3. You need a tool that sends the magic packet to your DynDNS domain from outside.

Typical result: you spend an hour configuring this only to find your ISP doesn't allow this operation.

How SayBoot solves it

SayBoot flips the approach: instead of opening the router from the outside, it keeps a persistent connection from the inside out to the cloud.

You (away from home) -> remote Echo -> Alexa cloud -> SayBoot skill ->
    SayBoot server (relay) -> SayBoot agent on the home PC ->
        local UDP magic packet -> target PC powers on

The SayBoot agent, installed on a home PC that stays on (or in sleep with WoL enabled), acts as a dispatcher: it receives the command from the cloud relay and itself sends the magic packet on your LAN. The magic packet never has to cross the router from the outside — it always originates from the inside.

What you actually need:

• A target PC with Ethernet and WoL enabled (exactly as for classic Wake-on-LAN — see the complete guide)
• At least one PC on the local network with SayBoot installed and Online in the dashboard, acting as the dispatcher
• A normal SayBoot install (Alexa skill linked to your Amazon account)

What you do NOT need:

• Router port-forwarding
• A static public IP or DynDNS
• Home firewall configuration
• VPN subscriptions

The "single PC" scenario: what happens

If you have only one PC and it is the wake target, there's no dispatcher available when you're away. In this case the command leaves Alexa, reaches the SayBoot relay, but finds no one to forward the magic packet to on your local LAN.

Realistic options:

• Add a mini-PC / Raspberry Pi running SayBoot as a dedicated dispatcher (consumption <5W). Your old spare laptop with SayBoot installed and left in sleep is perfectly fine.
• Accept the limit: keep the PC on and use SayBoot to shut it down / restart it when needed (shutdown doesn't need a dispatcher, the PC's own agent receives the command).

This is a physical limit of WoL, not a SayBoot design choice: to power on a device that is off via the network, someone inside the network has to send the packet.

Scenario: "home PC + Echo at the second house"

Typical setup: desktop at home, Echo at the office or vacation house, you want to wake the desktop from the second location.

It works automatically if the remote Echo is linked to your same Amazon account (and not to a different one). The voice command leaves the remote Echo, reaches the Alexa cloud, gets routed to the SayBoot relay, and arrives at the dispatcher on your home LAN — exactly as if you were in the living room.

No special configuration. The only requirement is a single Amazon account with multiple registered Echoes (which is already normal if you have Echoes in multiple rooms at home).

Why it isn't a VPN

Someone might ask: "Why not use a VPN from the phone to the home LAN and then send the magic packet?"

It would technically work, but:

• Requires a VPN server at home (complexity)
• Requires a VPN app on the phone, always on
• Not integrated with Alexa — needs a separate app, defeating the "voice-only control" point
• Many ISPs block or throttle custom VPNs

The SayBoot relay runs on the same cloud infrastructure as the Alexa skill, so it adds no significant latency and is transparent to the user.

Timing and reliability

From voice command away from home to local magic packet: typically 1-3 seconds, the same as when you're home. Relay latency is in the 100-200ms range, invisible compared to the Alexa Cloud's own timings.

Reliability: if the dispatcher PC is online, failure probability is minimal (SayBoot servers run >99.9% uptime). The main risk is the dispatcher state: if it gets shut down for maintenance, the relay has nobody to forward to. That's why some users add a Raspberry Pi as a dedicated dispatcher — low power, 24/7 uptime.

---

All clear? Start from the main guide to wake your PC with Alexa or set up the dispatcher right away: open the SayBoot webapp.

If the remote setup doesn't work, first try the 7 points in Wake-on-LAN not working with Alexa: 2026 fixes — many "remote" issues are actually basic ones.