Near cell exit false exit

[Robert Koza]

I use near cell to alert my team I am almost there and use the exit portion to tell my family I am on my way home.  My problem is I get a false exit as several areas in my building are dead zones.  Any ideas on a way to tell it to "recheck" the cell near after 1 minute and only then if I am not near the cell send the message.  I have to use near cell because I do not have open wifi and do not want to use location.  Thanks

[Rich D]

I use near cell to alert my team I am almost there and use the exit portion to tell my family I am on my way home.  My problem is I get a false exit as several areas in my building are dead zones.  Any ideas on a way to tell it to "recheck" the cell near after 1 minute and only then if I am not near the cell send the message.  I have to use near cell because I do not have open wifi and do not want to use location.  Thanks

This is sometimes referred to as bouncing, 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. This example uses a context : state: Cell near.  This will work with any state context. 

Profile: Cell on

Context: cell near

Enter Task: Start

1. Enter task stuff

<put the following actions as the first actions in your 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 !

[Pak]

Another idea is to simply break it into two Cell Near profiles. The first is getting to work. Add a Cooldown time property so that once you team has been sent an email, have it not do it again for 8 hours or whatever is appropriate. Then another for your family where instead of using leaving work cell location, instead pick a cell location sufficiently far from your work (a few miles) where when you get there you clearly are on your way home.

[John W.]

Neat idea....just add a null cell id to the ignore list. Assuming you have GSM service, add "GSM:0.0" to your ignore list and the profile will not deactivate in those dead spots.

[John W.]

If by "open wifi" you mean that there is WiFi but you cannot or are not allowed to connect to it, you can still use the WiFi near context which will not deactivate until two scan periods have elapsed.

[John W.]

Neat idea....just add a null cell id to the ignore list. If you have GSM service, add "GSM:0.0" to your ignore list and the profile will not deactivate in those dead spots. If you have some other network topology, next time you're in a dead spot launch tasker and look at the recent cell id's. Add whichever one that is 0 to your ignore list.

[Robert Koza]

Thanks for the help.  Ended up using a combination of GSM;0.0, a time delay on entrance and exit and variable the changes with in work area and out of work area.

On Thu, Nov 23, 2017 at 12:15 AM, John W. <johnwood...@gmail.com> wrote:

Neat idea....just add a null cell id to the ignore list. If you have GSM service, add "GSM:0.0" to your ignore list and the profile will not deactivate in those dead spots. If you have some other network topology, next time you're in a dead spot launch tasker and look at the recent cell id's. Add whichever one that is 0 to your ignore list.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/E7i8-jR-9_E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--

R W Koza

r.w....@gmail.com

[John W.]

I recently had to play around with my own cell near context and ended up with something that would likely help you out.

In addition to ignoring dead spots and airplane mode, occasionally a tower ID is mis-received and will cause the condition to fail. Incorporating a short RegEx will fix that as well. Put this in your ignore list:

GSM:0.*
~R^[^.]*$

You'll find that you wont need the delay any more. If you do want the delay consider adding an if condition so that the delay only happens when you're at a specific location:

if %LOC%LOCN ~R ##.###,-##.###

Replace the hashes with your ogfuce coordinates, but only use 2 or 3 decimal places so that it will have a sufficient radius. It will still evaluate correctly even in a dead spot because the location coordinates will be retained from the last system location check.