3

Sub-trigger or trigger within task

As of now, trigger (event, state, app, time etc) can be defined only as start event of any profile. Once any task is running with this trigger, there is no way to pause running task and wait till another event occur. This brings limitation to define complex task/profiles.

We can use workaround of activating another profile with that task, but that's workaround only and not best solution.

I am not software person, but my guess, we have all trigger elements readily available to do this. It's about putting these trigger element within task and defining algorithm to use this. 

I believe, this will lead tasker capability to next level.

Follow

2 replies

Votes Newest Oldest
R

I suppose the alternative is to create a profile of multiple events with AND condition between them, with or w/o order

Comment

Can you please give me an example of a use case for this?

Wouldn't you be able to achieve what you want with the "Perform Task" action?

Comment
R

Perform task doesn't wait for any further trigger and it executes straight forward it gets command.

I am struggling to make profile for Auto speakerphone based on proximity. If I use two trigger condition simultaneously, i.e. Call state any + any sensor event (proximity) -> Speakerphone On if proximity near else off.

It is expected when I pick up call, speakerphone should On until I put it near my ear. But it never happens as when phone is received, call state is active but no proximity event until I put my hand to proximity sensor.

So, I was thinking to stagger two triggers, first call state any -> check proximity and accordingly speakerphone on/off -> continue checking sensor event, i.e. another trigger.

Hope, I could explain the scenario.

Z 
exactly what I want, a trigger within a task. I was trying to do this to wait for a specific notification, but I ended up having to make a query in the notifications. it would be of great help to bring this system to the tasker
Ícone "Verificada pela comunidade"
 
 
 
 
 

To do that you could create a profile that triggers on that condition and in the task set a variable to some value, and then in the task where you want to wait use the Wait Until action to wait for that variable value to be what you want :)

Z 
it ends up resulting in many profiles, 
it would make life a lot easier for many people, 
having a wait for an event or state or day or application, 
I thank you very much if you can bless me with that.
Reply