The way WakeOnLan works is that XBMC provides a WOL library (which I assume sends a magic packet) so all we do is call that, with the server's MAC address. We know the server's MAC address because ServerWMC tells us what it is when the client first connects. Once we have talked to ServerWMC we know the MAC address but we also persist it to disk in the XBMC addon_data area, since if the client started up cold and the server was not online, we wouldnt know the MAC address yet. So it is read from the addondata file at client startup, but once a server connection occurs we use the value obtained from the server (and write that to the addondata file for next cold startup).
You also have to have it enabled in AddOn settings which I assume you do since it is popping up saying it is waking the backend...
I didnt actually test the WOL part, since I just call XBMC->WakeOnLAN but I tested the handshake, providing of MAC address, storing it in the addondata storage and so on. It works on windows! I cant say for Android since I ont have an android device to test on
I believe our testers did test the actual WOL functioning however im not sure on what platforms
Things to check:
- Check ServerWMC log file when ServerWMC starts up to make sure it is using the correct interface MAC address (it grabs the first enabled NIC MAC). If it isnt correct you can set in the config.xml file which MAC address you want used
- Check XBMC debug log for what MAC address the client is using to send WOL to
- Check file system on XBMC client to locate the addon_data directory and see if the ServerMACAddress.txt file is there and contains the correct MAC address.
Check your ServerWMC log for the MAC address it says it is providing to clients