AlexGustafsson / homebridge-wol

A Wake on Lan plugin for Homebridge
MIT License
295 stars 30 forks source link

Wake on Lan is no longer working #260

Open KeirAnsell opened 7 months ago

KeirAnsell commented 7 months ago

Backstory

A while ago I had set this up and everything was working perfectly but recently I had to reinstall Raspberry Pi OS and therefore Homebridge and set it all up again.

I've gone through and set everything up as I believe that it should be setup and tried a bunch of troubleshooting and research but I just can't seem to get Wake on Lan working again.

Any help is appreciated and thank you for creating and maintaining this plugin! <3

Issue

At this point I'm pretty stumped!

I've checked the following;

Interestingly, Home.app does report the status of the PC correctly, so I assume the ping's are going through successfully.

Another point of note (and honestly, maybe I'm misremembering) but while it doesn't wake from a full shutdown, it does wake the PC if the PC is sleeping. This could well be how its always worked (maybe WoL can't wake a machine that's fully shutdown - i can't remember but think its worth highlighting before you spend too much time delving into the logs and such!)

Environment

- os and os version: Windows 11 (10.0.22635 Build 22635)
- node version: 20.11.0
- homebridge version: 1.7.0
- homebridge-wol version: 6.0.1

Configuration

{ "bridge": { "name": "Homebridge 3908", "username": "0E:4B:C2:9E:39:08", "port": 51202, "pin": "190-72-451", "advertiser": "avahi" }, "accessories": [ { "name": "Moon", "manufacturer": "homebridge-wol", "model": "NetworkDevice", "host": "10.0.0.222", "pingInterval": 2, "pingsToChange": 5, "pingTimeout": 1, "pingCommandTimeout": 0, "startCommandTimeout": 0, "wakeGraceTime": 45, "wakeCommandTimeout": 0, "shutdownGraceTime": 15, "shutdownCommandTimeout": 0, "logLevel": "Debug", "returnEarly": false, "accessory": "NetworkDevice" }, { "name": "Jupiter", "manufacturer": "homebridge-wol", "model": "NetworkDevice", "host": "10.0.0.155", "pingInterval": 2, "pingsToChange": 5, "pingTimeout": 1, "pingCommandTimeout": 0, "mac": "a8:a1:59:8d:8e:20", "startCommandTimeout": 0, "wakeGraceTime": 45, "wakeCommandTimeout": 0, "shutdownCommand": "shutdown -s", "shutdownGraceTime": 5, "shutdownCommandTimeout": 0, "logLevel": "Debug", "returnEarly": false, "accessory": "NetworkDevice" } ], "platforms": [ { "name": "Config", "port": 8581, "platform": "config" }, { "name": "Tuya", "options": { "projectType": "2", "accessId": "MYACCESSID", "accessKey": "MYACCESSKEY", "countryCode": 44, "username": "MYEMAIL", "password": "MYPASSWORD", "appSchema": "tuyaSmart", "deviceOverrides": [ { "id": "20753605840d8ebc64b2" } ], "debug": false }, "platform": "TuyaPlatform" }, { "name": "Govee", "username": "MYEMAIL", "password": "MYPASSWORD", "lightDevices": [ { "label": "Long Desk", "deviceId": "B1:14:D4:AD:FC:AD:5F:FE" } ], "platform": "Govee" }, { "devices": [ { "host": "10.0.0.142", "port": 8189, "name": "Under Desk", "chip": "WS2811", "colorOrder": "GRB", "segments": 10, "ledsPerSegment": 60, "debug": false } ], "name": "SP108EPlatform", "platform": "SP108EPlatform" } ], "disabledPlugins": [] }

Logs

When I follow these steps:
1. Make sure `logLevel` is set to `Debug` on all `NetworkDevice` accessories
2. Run `homebridge`
3. Let it run for a couple of minutes
4. Try to turn a device on or off using the plugin
5. Wait one minute
6. Repeat step 4

I get the following log:

It was too long to paste here so I've uploaded it to Google Drive and you can find it here: https://docs.google.com/document/d/13krUQnlJHWrbx9gddwiOnDvlyIRPv3QBFsV7cNMpuys/edit?usp=drive_link

You likely just need the beginning and end (this log was downloaded after a Homebridge reboot, waiting a minute or two and then trying the WoL).



### Notes

_No response_
costispavlou commented 6 months ago

I think I've found the problem. When adding a device through homebridge plugin settings it f*cks up the json file. I copied the settings from one to the other and remade everything.. see below:

    "name": "PC",
    "manufacturer": "homebridge-wol",
    "model": "NetworkDevice",
    "host": "redacted",
    "pingInterval": 60,
    "pingsToChange": 3,
    "pingTimeout": 2,
    "pingCommandTimeout": 0,
    "mac": "reductred",
    "broadcastAddress": "reducted",
    "startCommandTimeout": 0,
    "wakeGraceTime": 15,
    "wakeCommandTimeout": 0,
    "shutdownGraceTime": 15,
    "shutdownCommandTimeout": 0,
    "logLevel": "Info",
    "returnEarly": true,
    "_bridge": {
        "username": "reducted",
        "port": reducted
    },
    "accessory": "NetworkDevice"

the above worked fine and still is working fine. However the two new devices added have all sorts of issues:

{ "name": "KWS EVO", "manufacturer": "homebridge-wol", "model": "NetworkDevice", "host": "redacted", "pingInterval": 60, "pingsToChange": 3, "pingTimeout": 2, "pingCommandTimeout": 0, "mac": "xxxxxxxxxx", <--- had : instead of no spaces "broadcastAddress": "XXXXXXX.255", "startCommandTimeout": 0, "wakeGraceTime": 15, "wakeCommandTimeout": 0, "shutdownGraceTime": 15, "shutdownCommandTimeout": 0, "logLevel": "Info", "returnEarly": true, "accessory": "NetworkDevice" }

notice no bridge and no port settings

and this one:

{ "name": "Synology", "manufacturer": "homebridge-wol", "model": "NetworkDevice", "host": "192.168.x.xx", "pingInterval": 2, "pingsToChange": 5, "pingTimeout": 1, "pingCommandTimeout": 0, "mac": "00:xx:xx:xx:xx:00\t", <------- t? "broadcastAddress": "192.168.0.255", "startCommandTimeout": 0, "wakeGraceTime": 60, "wakeCommandTimeout": 0, "shutdownCommand": "shutdown /s", "shutdownGraceTime": 15, "shutdownCommandTimeout": 0, "logLevel": "Info", "returnEarly": true, "_bridge": { "username": "xx:xx:xx:xx:xx", "port": xxx }, "accessory": "NetworkDevice" }

hopefully I've helped

costispavlou commented 6 months ago

changing the one that works with the device mac address, still doesn't do anything either. please help ;s

Berk-Kaya commented 3 months ago

Try disabling fast startup