What to do when WOL works in app, but not in Tasker
Ibrahim Jadoon 10
Hello! WOL is working perfectly from the Unified Remote (Full) app. I can tap "Wake on LAN" inside the Power remote and my PC starts up instantly.
However, it's not working at all when I use Tasker. It just says "Connecting" for a few seconds and then "Disconnected". The PC doesn't turn on. I tested UR + Tasker with a "shutdown" task: no problems. It's just this WOL task that is failing.
I set it like so: Task -> Plugin -> Unified Remote Full -> Edit Configuration -> Remote Action -> Power -> @wol (Wake On Lan) -> select my PC -> Done. This is what the Tasker task looks like.
I test the Task. Good, Tasker begins the task.
What have I done wrong? It works perfectly from the UR Power remote: one tap and the PC is instantly started. Why doesn't the action do the same thing? I'm on a OnePlus One (Android 5.1.1) on Cyanogen OS 12.1; the PC is a Windows 8.1 Pro x64 on a Gigabyte GA-Z87X-UD5H motherboard with an Intel I217-V NIC.
I don't think the issue is with the hardware because the UR app + WOL works and Tasker + Shutdown works, but Tasker + WOL doesn't work. But, I'm open to any ideas.
Ibrahim Jadoon 10
I figured it out! This post by scuba65 clued me in. He said WOL was one of the few actions that didn't require the server app.
That made me think...the power remote's actions ("Connecting...Disconnected") sounds like it was trying to connect to the server. But the server is offline (obviously...). So, in the Action setup, you can pick "Remote Action" (which I picked because WOL is definitely an action on the power remote) OR "Device Action".
I checked out "Device Action" and, lo behold, a second WOL option. I tried this one and, bam wham shabam, it works perfectly: now Tasker instantly turns on the PC.
tl;dr: For whatever reason, "Remote Action" -> "Power" has a WOL that doesn't work. Instead, use "Device Action" -> "WOL" and that works.