I tried to use the Wake on LAN Binding in order to Power On my Synology.I want to specify that from other device that is in the same private network is possible to use WOL and wake up the Synology device.
the Item file that I’m using looks like:
Switch WOL_Synology “Synology NAS” { wol=“192.168.1.255#00:11:32:4B:4A:71”}
192.168.1.255 - broadcast address of my private network
Wow, I totally misread the binding page so deleted my own comment. If you haven’t solved yours maybe append ', nh=“ip of NAS” '. Have you verified WoL works outside of OpenHAB?
Be aware that there are two different bindings, wake on lan and network health, the latter would be {nh=“computer.ip.or.fqdn”}, the former {wol=“ip and#mac-address”} in configuration.
Having a basic docker container and a perl “wake-on-lan” script does work.
Having an openhab docker container with the openhab wake-on-lan binding does not work. I really don’t see why. Moreover my openhab docker container is even running with the “–net=host” parameter.
I’ve tryed upper- or lower-case, in openhab configuration, and “:” or “-”, nothing works.
All my IPs are 192.168.8.x, so i tryed : 192.168.8.255, or 192.168.255.255, and even 255.255.255.255 (the default used by the wake-on-lan perl script), nothing works.
Then i added the wake-on-lan perl script inside the docker container running openhab, and it works like a charm. So i’m pretty sure that i have a trouble not with the dockerisation of openhab but with this java binding (but i don’t see where).
Any ideas ?
Moreover i don’t see any logs about the wake-on-lan commands (just the the fact that i clicked on my “wake” switch in the sitemap), is that normal ?
Don’t know what first post you’re talking about, it’s my first post here (and i’m not the original poster) (and yes i have everything under 192.168.8.x).
I’m not sure if it’s required or not but make sure you have the wakeonlan package installed in your OH instance. Honestly don’t know if the binding is sending the WoL magic packet or calling ‘wakeonlan’ to do it.
wol=“192.168.10.255#ab:cd:ef:12:34:56” works on my LAN although my research indicated a possible kexec bug so my shutdowns end up in reboots and the network health binding isn’t refreshing in a timely manner even though it is supposedly 60 seconds. That’s another topic though
Well, you posted the exact same thing within few minutes in 5+ topics. Let me help you to find the one sentence I was trying to point you to with the link from above:
Don’t cross-post the same thing in multiple topics.