AlexGustafsson
commented
5 years ago This likely happens due to five consecutive pings failing to reach the computer during ten seconds (this is dependent on the configuration).
You can enable the pinger's logger by adding logPinger: true to the configuration. If you're feeling like doing a deep dive, there are tools such as Wireshark to monitor the network to see whether or not the pings are indeed not reaching the target device.
Some operating systems have the option to disable responses to pings, make sure that your computer responds to pings.
Backstory
Just playing a little bit with Homebridge and wanted to start my Win10 PC in the cellar via WOL.
Issue
If I press the button in the Apple home app, it turn on my PC and it is starting. The Homebridge Log shows the message
[Windows PC] NetworkDevice awake cycle started for "Windows PC" (192.168.178.33) [Windows PC] Attempting to wake up "Windows PC" (192.168.178.33) [Windows PC] NetworkDevice "Windows PC" (192.168.178.33) went from status "Offline" to "Waking Up"
After a while, the switch turn off again with the message (in home bridge log)
[Windows PC] NetworkDevice "Windows PC" (192.168.178.33) went from status "Waking Up" to "Offline"
The Windows PC stays turned on and I also can use Remote Desktop to connect to it.
Environment
Configuration
My configuration looks like this: { "accessory": "NetworkDevice", "name": "Windows PC", "mac": "",
"ip": "192.168.178.33",
"shutdownCommand": "net rpc shutdown --ipaddress 192.168.178.33 --user user&password"
}