How to avoid Location trigged when start Automagic service?

[natong]

When start Automagic service or reboot the phone, it trigged "Location Trigger" every time.
Is there a way to avoid these behavior?

Screenshot_2015-08-31-11-49-25-700.jpeg (108.67 KiB) Viewed 12079 times

11.jpeg (109.79 KiB) Viewed 12079 times

12.jpeg (63.01 KiB) Viewed 12079 times

[natong]

I tried to check the restart behavior by use some expression.
And use "Shutdown Trigger" but it no time to run and can't store the value into the global var.

[natong]

Very sorry I post in a wrong forum. Please move these topic to the User Help/Bug Reports.

[ferda-mravenec]

Hi.

Just set some global boolean flag when Automagic is about to start (wait a few seconds and set the flag to opposite value) and use the Expression in your home flow to check whether the flag is true or not.

[natong]

Just set some global boolean flag when Automagic is about to start (wait a few seconds and set the flag to opposite value) and use the Expression in your home flow to check whether the flag is true or not.

Good trick! Thanks!



I just move to AM and just known the truth of geofence. These are my investigations about location trigger:

1. Location triggering repeatedly

Since geofence can be report 3m - 3km (up to google and surrounding). Sometime Google use only cell tower. Sometime use wifi scanning. Sometime lost of internet. Sometime get GPS fixed.

Solution 1: We should set radius as width as we can accept. The best value is equal to cell tower's radius (~500m-1km). That why Llama use only cell tower method and stable.

11.jpeg (108.9 KiB) Viewed 12064 times

Solution 2: Add an addition condition. If home/work WiFi connected then disable the location trigger flow. Maybe it will save a little power too. The WiFi connection make sure that you never goes outside or inside.

Screenshot_2015-09-01-11-18-40-586.png (83.27 KiB) Viewed 12064 times

2. Location trigged when reboot or start AM service

It look like AM doesn't ignore the null value, compare and trigged as enter/exit. Many times trigged as a wrong direction.

Solution 1: Nothing to do and wait admin to investigation.

Solution 2: Since AM trigged location very fast (before the other flow can store the global var), Add some small delay and use expression to check the restart behavior (as ferda-mravenec mention).

Screenshot_2015-09-01-11-22-47-857.jpeg (95.23 KiB) Viewed 12064 times