wake_on_lan (WOL) switch platform allows you to turn on a WOL enabled computer.
The WOL switch can only turn on your computer and monitor the state. There is no universal way to turn off a computer remotely. The
turn_off variable is there to help you call a script when you have figured out how to remotely turn off your computer.
See below for suggestions on how to do this.
To enable this switch in your installation, add the following to your
# Example configuration.yaml entry switch: - platform: wake_on_lan mac_address: "00-01-02-03-04-05"
(string)(Required)MAC address to send the wake up command to.
(string)(Optional)The name of the switch.
Default value: Wake on LAN
(string)(Optional)The IP address or hostname to check the state of the device (on/off).
(string)(Optional)Defines an action to run when the switch is turned off.
(string)(Optional)The IP address of the host to send the magic packet to.
Default value: 255.255.255.255
Here are some real-life examples of how to use the turn_off variable.
Suggested recipe for letting the
turn_off script suspend a Linux computer (the target)
from Home Assistant running on another Linux computer (the server).
- On the server, log in as the user account Home Assistant is running under. (I’m using
hassin this example)
- On the server, create ssh keys by running
ssh-keygen. Just press enter on all questions.
- On the target, create a new account that Home Assistant can ssh into:
sudo adduser hass. Just press enter on all questions except password. I recommend using the same user name as on the server. If you do, you can leave out
hass@in the ssh commands below.
- On the server, transfer your public ssh key by
ssh-copy-id hass@TARGETwhere TARGET is your target machine’s name or IP address. Enter the password you created in step 3.
- On the server, verify that you can reach your target machine without password by
- On the target, we need to let the hass user execute the program needed to suspend/shut down the target computer. I’m using
poweroffto turn off the computer. First, get the full path:
which pm-suspend. On my system, this is
- On the target, using an account with sudo access (typically your main account),
sudo visudo. Add this line last in the file:
hass ALL=NOPASSWD:/usr/sbin/pm-suspend, where you replace
hasswith the name of your user on the target, if different, and
/usr/sbin/pm-suspendwith the command of your choice, if different.
- On the server, add the following to your configuration, replacing TARGET with the target’s name:
switch: - platform: wake_on_lan name: "TARGET" ... turn_off: service: shell_command.turn_off_TARGET shell_command: turn_off_TARGET: 'ssh hass@TARGET sudo pm-suspend'