The reason it does not work using the port forwarding hack is the ARP table entry will timeout in the router and it no longer know where to send the data. Way too much misinformation out there including from people that write the client applications that send the WoL packet. There is no concept of IP addresses or port or UDP or TCP. The problem is the WoL only uses mac addresses.
People "think" they can make it work with port forwarding but it only will work for a short time. Add this line last in the file: hass ALL=NOPASSWD:/usr/sbin/pm-suspend, where you replace hass with the name of your user on the target, if different, and /usr/sbin/pm-suspend with the command of your choice, if different.It will not work because you are attempting wake on WAN which does not exist. On the target, using an account with sudo access (typically your main account), sudo visudo.On my system, this is /usr/sbin/pm-suspend. First, get the full path: which pm-suspend. Here is it pm-suspend, use poweroff to turn off the computer. On the target, we need to let the hass user execute the program needed to suspend/shut down the target computer.On the server, verify that you can reach your target machine without password by ssh TARGET.Enter the password you created in step 3. On the server, transfer your public SSH key by ssh-copy-id where TARGET is your target machine’s name or IP address.If you do, you can leave out in the SSH commands below. It’s recommended using the same user name as on the server. Just press enter on all questions except password. On the target, create a new account that Home Assistant can ssh into: sudo adduser hass.On the server, create SSH keys by running ssh-keygen.On the server, log in as the user account Home Assistant is running under.Suggested recipe for letting the turn_off script suspend a Linux computer (the target)įrom Home Assistant running on another Linux computer (the server). Here are some real-life examples of how to use the turn_off variable.
0 kommentar(er)
