
* Update switch Wake on Lan configuration variable Update style of switch wake on lan documentation to follow new configuration variables description. Note: the numbered list, I assume that it should remain as the code is now? Related to #6385. * Update switch.wake_on_lan.markdown Added default for name * Adjustment to the name since the default is set * ✏️ Corrects two types * ✏️ Tweak
3.6 KiB
layout | title | description | date | sidebar | comments | sharing | footer | logo | ha_category | ha_release | ha_iot_class |
---|---|---|---|---|---|---|---|---|---|---|---|
page | Wake on LAN Switch | Instructions on how to integrate a wake on lan switch. | 2016-03-18 18:00 | true | false | true | true | ethernet.png | Network | 0.16 | Local Polling |
The wake_on_lan
(WOL) switch platform allows you to turn on a WOL enabled computer.
{% linkable_title Configuration %}
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 configuration.yaml
file:
# Example configuration.yaml entry
switch:
- platform: wake_on_lan
mac_address: "00-01-02-03-04-05"
{% configuration %} mac_address: description: MAC address to send the wake up command to. required: true type: string name: description: The name of the switch. required: false default: Wake on LAN type: string host: description: The IP address or hostname to check the state of the device (on/off). required: false type: string turn_off: description: Defines an action to run when the switch is turned off. required: false type: string broadcast_address: description: The IP address of the host to send the magic packet to. required: false default: 255.255.255.255 type: string {% endconfiguration %}
{% linkable_title Examples %}
Here are some real-life examples of how to use the turn_off variable.
{% linkable_title Suspending Linux %}
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
hass
in 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 outhass@
in the ssh commands below. - On the server, transfer your public ssh key by
ssh-copy-id hass@TARGET
where 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
ssh TARGET
. - On the target, we need to let the hass user execute the program needed to suspend/shut down the target computer. I'm using
pm-suspend
, usepoweroff
to turn off the computer. First, get the full path:which pm-suspend
. On my system, this is/usr/sbin/pm-suspend
. - 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 replacehass
with the name of your user on the target, if different, and/usr/sbin/pm-suspend
with 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'