Profile Activation Cooldown

[Danny Baromen]

Hi there,

Is there an option/way to prevent a profile from becoming active again for a short while after being de-activated.

The cooldown option seems to apply to the profile becoming active, not inactive...

[Rich D]

> Is there an option/way to prevent a profile from becoming active again for a short while after being de-activated.
>
> The cooldown option seems to apply to the profile becoming active, not inactive...

Correct.  What exactly are you trying to do?

One way to do this is to add a  'variable time context' to the profile.  You would set the next activation time for the profile in the exit task.   Check the user guide for proper implantation.

If the profile is bouncing you can do this.

You can search this group for other approaches but this is the one I use. It will stop both the enter task and exit task from running when the context bounces.  

Profile: Cell on
Context: cell near
Enter Task: Start
1. Enter task stuff

<put the following actions as the first actions in you exit task>

Exit task:stop
1. Wait 5 sec <whatever time you need>
2. Stop  <enter task> ;Start
3 Stop if %PACTIVE ~ *,Cell on,*
4. Rest of exit task

[Danny Baromen]

It appears that my Galaxy S6 edge's power chip is a lot more sensitive than the previous S4's was and when I turn the car off, it re-triggers the car profile when I turn the car off... and since the car is already off then, it never exits that profile.

So I was looking for a way to prevent the profile from being re-triggered for like 3-5 seconds after going in-active so that this doesn't happen.

[Rich D]

> So I was looking for a way to prevent the profile from being re-triggered for like 3-5 seconds after going in-active so that this doesn't happen.

On this site that is referred to as bouncing. Unfortunately there is no way  to keep the profile from activating. The sample profile I posted will fix this issue. However this will not work  if you are relying on taskers 'restore setting'  option.  then you will have 2 options.

1. Just use the exit task to restore your settings.

2. You can De- bounce the profile instead of just the tasks.   Here is a example of that. 

Tasker de-bounce profile

Below is a example.  For the profile 'quick toggle' you should replace the prox sensor context with your  context (I use the prox sensor just for testing). In the quick toggle profile no matter how many times the profile toggles within the 5 seconds the enter task will only run once and the exit will not set the variable until the context has been inactive for more then 5 seconds. 

Profile: Quick Toggle (344)
State: Proximity Sensor
Enter: Entertest (345)
A1: Variable Set [ Name:%Bluetooth To:on Do Maths:Off Append:Off ]

Exit: Exittest (348)

A1: Wait [ MS:0 Seconds:5 Minutes:0 Hours:0 Days:0 ]
A2: If [ %PACTIVE ~ ,*Quick Toggle,* ]
A3: Stop [ With Error:Off Task:Entertest ]
A4: Stop [ With Error:Off Task: ]
A5: End If
A6: Variable Set [ Name:%Bluetooth To:off Do Maths:Off Append:Off ]

Profile: Bluetooth (493)
State: Variable Value [ %Bluetooth ~ on ]
Enter: Set Settings (494)
A1: Ringer Volume [ Level:10 Display:Off Sound:Off ]

[Danny Baromen]

Thanks Rich!

I'll give it a try this weekend :-D