-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
magic packets sent not waking pc anymore #250
Comments
Confirming this plugin has also stopped working for me for a little while now. I'd say on the order of 2-3 weeks. (No change to the PC's static IP) |
that timeline sounds right for my experience as well I'm now working around this issue by using Home Assistant's WoL feature and passing it through to homekit as a switch |
Try deleting these two lines from your config, I had similar issues and this plugin worked again after removal.
|
Just tried this and restarted my Homebridge, still not working unfortunately. |
advice to change wake_on_lan to wakeonlan to fix this |
Same issue here, since about two week this stopped working suddendly, without any reason. |
My solution to this was to install etherwake on my Raspberry Pi, then set the |
So I tried diving into my PC's BIOS just to double check my settings, and it turns out there was a "Boot From Onboard LAN" setting that was set to "Disabled" for some reason. I enabled that and this switch is working for me again... Your mileage may vary, but I suggest double checking your BIOS and Windows settings to ensure they didn't get changed like mine did somehow. |
It's interesting that you have seen the issue pop up around the same time, a time around which this plugin hadn't been updated. Could it be that some BIOS or Windows update changed the settings for Wake On LAN? |
No, because within one day of this plugin no longer working, I set up a Home Assistant server and the built in WoL worked immediately with no changes to Windows. |
It's weird that something would break out of nowhere without changes anywhere. I'll keep the issue open for a while to see if anyone else has something to add. Otherwise I'll probably close this as there's been no related change made in a long time, so there's nothing that can be changed in the plugin to fix this. It's likely some external factor. |
I suspect that an update to HomeBridge or Raspbian caused the issue. What I observe is that it might get stuck in the shutting down state, and does not move to offline. The pc does get successfully shutdown and stops responding to pings. [25/01/2024, 09:13:58] [Home PC] [NetworkDevice] Shutdown cycle started When it works correctly the following two log entries are recorded: This issue could be related to or caused by #255 |
My issue #255 is mainly focus on the "detecting" part of online PC (whether the PC is on or off, it only shows the PC is turning off), the turn on feature for PC is working as expect. |
In my case was fault of Homebridge (installed on Synology NAS) that, after an update, was unable to ping my computer. To solve, I connected via SSH to the NAS as root user and executed the following command:
Then everything went back working as before. |
Backstory
i hadn't updated or restarted Homebridge or my plugins in a while. after restarting Homebridge recently after disabling another plugin, this plugin stopped waking my PC.
Issue
i did take steps to update Homebridge and this WoL plugin to the most recent version, but the problem persists.
i recently set up a Home Assistant server and i was able to confirm my PC's WoL settings are right by testing it with Home Assistants developer service wake_on_lan.send_magic_packet, when i tested this with my mac address the PC woke up immediately
Environment
Configuration
Logs
When I follow these steps:
logLevel
is set toDebug
on allNetworkDevice
accessorieshomebridge
I get the following log:
after one minute
The text was updated successfully, but these errors were encountered: