Wake on LAN false positives

117 views
Skip to first unread message

Cjsnet

unread,
Aug 8, 2011, 1:21:13 AM8/8/11
to Tasker
Hi

I am using the Wake On LAN instructions from your site.

Say I am home for 3 hours, and go to sleep. I also put my computer to
sleep. During the night, the Wi-Fi signal trips up for a second
(disconnects then reconnects - common for phones, unreliable signals,
ISPs dropping connections for maintenance etc.). Tasker then sends
the WOL to my computer, which wakes up - and obviously I don't want it
to as I am already at home, already connected to the defined Wi-Fi,
and I put it to sleep.

I only want the computer to wake up when I FIRST arrive at home.
After then, it should be my decision, until I leave the home Wi-Fi
zone again.

Is there any way to make it so that Tasker will only send the WOL
packet if the phone is away from the home Wi-Fi network (disconnected)
for say 10 minutes before it reconnects? Some sort of timeout?

Basically any way to stop these 'false positives' when the Wi-Fi
connection just 'trips up' occasionally?

Thanks!

Pent

unread,
Aug 8, 2011, 3:53:28 AM8/8/11
to Tasker
> I am using the Wake On LAN instructions from your site.

It's a wiki, the contents are mostly created by Tasker users so I
don't know the details necessarily.

> Say I am home for 3 hours, and go to sleep.  I also put my computer to
> sleep.  During the night, the Wi-Fi signal trips up for a second
> (disconnects then reconnects - common for phones, unreliable signals,
> ISPs dropping connections for maintenance etc.).  Tasker then sends
> the WOL to my computer, which wakes up - and obviously I don't want it
> to as I am already at home, already connected to the defined Wi-Fi,
> and I put it to sleep.
>
> I only want the computer to wake up when I FIRST arrive at home.
> After then, it should be my decision, until I leave the home Wi-Fi
> zone again.

Are you using Wifi Near or Wifi Connected ?

Pent

Christian J Simpson

unread,
Aug 8, 2011, 12:05:03 PM8/8/11
to tas...@googlegroups.com
I'm using Connected.

Pent

unread,
Aug 9, 2011, 4:40:36 AM8/9/11
to Tasker
> I'm using Connected.

Then I would try a 'delayed' exit task:

Wifi Connected: blah

Enter Task:
Variable Set, %HAVEWIFI
DOENTERSTUFF

Exit Task:
Variable Clear, %HAVEWIFI
Wait 5 Minutes
DOEXITSTUFF If Isn't Set %HAVEWIFI

In task properties of the exit task, set collision handling to
'replace existing'
(or whatever the wording is).

Basically, don't do anything unless it's still disconnected after 5
minutes. You
could put in a shorter time and a counter loop if you want to get
advanced :-)

Pent

henrik

unread,
Jan 9, 2012, 4:10:37 AM1/9/12
to tas...@googlegroups.com
Thanks Pent! This was just what I was looking for!

I'm using cell towers to verify that I'm home or not.  Sometimes cell towers switch to a tower unknown to me, and my Home task would quit.  Now this is handled properly :)
Reply all
Reply to author
Forward
0 new messages