Skip to content
RemoteRelay
Your computer in your smart home ↗

Wake-on-LAN not working: troubleshoot your PC's wake setup

Separate three parts to find the failure: the computer must support wake, an active device must send the packet onto its network, and Alexa or another integration must target the correct computer. Test local wake first and the assistant afterwards.

RemoteRelay interface and smart-home integration
RemoteRelay · Interface and features vary by integration.

What you need

  • The MAC of the adapter connected to your test network.
  • Access to the computer's network and power settings; labels vary by manufacturer.
  • An active WoL sender, such as a compatible Echo or your Home Assistant host.

Getting started

  1. Keep the computer connected to power and check that its network adapter remains available in your intended power state.
  2. Review WoL in firmware and the operating system's network-wake settings. Record the original settings before changing them.
  3. Test a WoL packet on the same network with the correct MAC, first from sleep and then from shutdown if the hardware supports it.
  4. If local wake works, check the linked account, name and device discovered by Alexa. Distinguish old devices sharing the same name before repeating the command.
  5. Finally test your routine or access away from home. Keep the local sender available: the PC's agent cannot wake itself by sending its own packet.

What to check for each symptom

Change one condition at a time and record the result to distinguish hardware/network issues from integration settings.

Wake-on-LAN symptoms and next checks
SymptomNext check
Does not wake on the local networkMAC and interface, WoL support, adapter power and firmware/system settings.
Wakes from sleep but not from shutdownHardware support for shutdown wake and power configuration. On Windows, check the manufacturer's fast-startup guidance; on Mac, do not assume cold boot.
Works locally but Alexa cannot find itSkill account, discovery and endpoint name. Check for an old device with the same name.
Alexa accepts the command but the PC stays offCompatible Echo/sender, computer network and registered MAC. Command acceptance does not prove packet delivery.
Works at home but fails awayYour ecosystem's remote path and availability of the sender at home. Test from another network.
Wakes but does not open the appWait for the agent and user session. This is a control step after WoL; test the source while the computer is already running.

Compatibility and limits

Wake-on-LAN cannot work without power and does not guarantee wake over Wi-Fi or from every power state. Router port forwarding is not needed to diagnose a local test. Follow your manufacturer's documentation for firmware and power changes.

Test the action on your computer before including it in a routine. Available plans and features are detailed in the portal.

Common questions

Will reinstalling RemoteRelay fix Wake-on-LAN?

Not necessarily. If the hardware will not wake in a local test, check power, MAC, network and firmware before reinstalling or linking accounts again.

Does working remote shutdown prove wake works?

No. Shutdown uses a running agent; wake depends on hardware and an external sender that can transmit a WoL packet while the computer is stopped.

Put your computer to work with your home

Choose your integration and verify one action. Then add the apps, sensors and cameras you need.