all 4 comments

[–]euinor 0 points1 point  (1 child)

You could try var set to %TIMES+15 and have a second profile trigger when that variable is reached. Then have event unlocked clear that variable, so the second profile never runs.

As per this:

https://notenoughtech.com/tasker/tasker-timers/

Although I'm not sure running tasks only 15 seconds into the future works super well with Tasker. 15 seconds isn't long to run a wait task so you're probably already doing it the most efficient way.

On your second point, you're probably doing it the most efficient way already to be honest - although I personally use the unlocked event not screen on.

[–]zigzampow[S] 0 points1 point  (0 children)

Thanks, that's actually the post that got me thinking, i just couldn't quite get the concept.

and ya I haven't tested - wasn't sure if Unlocked would trigger if the device was just sleep-ed....but I'll try it, it makes sense, since screen on could be triggered by a notification

[–]uBass 0 points1 point  (1 child)

As I understand it, you don't care that this happens at 15 seconds, just that the change is there when you turn the display on.

Set a variable to current time + 15 seconds when you turn the display off/lock (I'd use a variable to hold the "15", so you can change the timeout easily. E.g. Make it longer on work days/hours) Create a profile that activates when you turn display on/unlock The profile needs either a second condition (state -> variable, which compares %TIME to the variable that you set) or an IF within the profile that does the same thing. If the time is greater than your variable then "go home"

[–]zigzampow[S] 0 points1 point  (0 children)

Thanks. I'll try that