Simply the auto discovery feature is slow and not robust enough to find the target device without manually input their IP and Mac address. From couple utilities I’ve tried, they are not as easy to use as Mac’s WakeOnLan. There are more tools to choose from to send WOL magic packets on Windows than Mac, but it doesn’t mean they are better than the Mac. Once you find the target Windows device with matching IP address and Mac address, hit “Wake Up!” will send the WOL magic packet to that device and if your Windows machine is configured properly, it will start up. But this isn’t a required step to make it work. It will try its best to associate and discover the device type, in the case when it couldn’t tell what kind device they are you can manually configure and set their device type. After you download the app, run the app, it will auto scan all the available devices from your local network. The best GUI tool I found is called WakeOnLan. It’s pretty straightforward, we just need to grab a GUI tool for Mac that will send the magic WOL packets through your local networks. If WOL concept is new to you, you should check out what it means to wake up a computer from a local network. In today’s post, we are going to cover how to wake up a Windows machine from a Mac and vice versa, waking up a Mac machine from Windows. I would appreciate you help and/or feedback on that.We’ve covered quite a few post related to Wake-On-Lan. I’ve configured the server as a networkdevice, and selected port 9 inside the networkdevice binding settings to make sure the packet will send on the right port.ĭo you have any idea or recommended settings for the binding i could try? I’ve already tryed to send the magic packets multiple times with a delay in between, but no success. I’ve implemmented the IP and MAC magic packet option inside the same rule to try both at the same time, but nothing changed. ![]() I don’t have any error messages inside the logs. If i send the WOL package from my pfSense firewall or straight from the router 30minutess later or more, the server respond straight ahead and start booting. If i wait for example for more then 30 minutes and send the WOL packet from openhab, the server does not wake up any more. When i shut it down and send the “magic Packet” via Openhab within a few Minutes after the shutdown, the WOL works perfectly fine and the server start booting. Actually i updated to 3.3 but the Problem seems to stay. I have a Openhab 3 Instance (3.2.0) running at a windows server VM on Ubuntu 18.04, installed via openhabian, which is running fine and without any problems so far. With my Openhab3 i would like to start it, which is working under some circumstances as followed. ![]() I have a Ubuntu server which is not necessary to run 24/7. I have one problem and i’m stuck with it. Thank you very much for this binding, thats very cool and helpfull. Message0: send a Wake-on-LAN packet via %1 to wake %2 Watch out for log messages if the operation doesn’t seem to work, for instance: : Cannot send WoL packet because the 'macAddress' is not configured for network:servicedevice:mycomputer Only choose a Network device when picking the thing. This block will send a Wake-on-LAN packet to the specified network device, which you can select in a popup by clicking inside the thing block. If you wish to use the MAC method, you should also provide the MAC address in the thing configuration. You need the Network binding installed and a configured device Thing. This library adds a block to wake a Network device with a Wake-on-LAN packet.
0 Comments
Leave a Reply. |