Page 1 of 1

Location Condition Failure

Posted: 09 Nov 2015 08:47
by Zeench
Hello Guys,

i have a condition where i locate my mobile to turn wifi on/off.
Since a few weeks/month it wont work anymore.
Automagic says im at home so it turns wifi on.
But im at work and this is about 5km away from my home.

when I open the map in Automagic its all correct, i have the location Im at and the point for me home with the radius (30m)

Dunno what to do. I already deleted the condition and made a new one but that wont work either...


Can u guys plz help me.
I didnt changed anything, it just broke.

Re: Location Condition Failure

Posted: 09 Nov 2015 11:42
by StrayCat
I can confirm this strange behavior. In my location based flows, when untill some weeks everything worked as spected, now I get some errors now and then and sometimes no errors but flows just doesn't work properly.

Re: Location Condition Failure

Posted: 09 Nov 2015 19:08
by Martin
Hi,

Did you initialize the location before the condition is executed (for example using action Init Variable Location) or are you using a trigger that get's a fresh location?
The condition alone uses the last known location of the device when no trigger or action provides a current location. Maybe your device properly updated the last known location some weeks ago but does not do this anymore for some reason.

Regards,
Martin

Re: Location Condition Failure

Posted: 10 Nov 2015 07:32
by Zeench
I use the Trigger "Standort Update" (german), and it doesnt work.

BUT the Hint with the Init Variable Location solved the Problem.
Dunno y, i think it shud work with jsut the Location Trigger.

Regards Chriz

Re: Location Condition Failure

Posted: 10 Nov 2015 18:59
by Martin
It should definitely work with trigger 'Periodic Location Update' since it uses similar mechanisms to get a fresh location from time to time. What device, Android version and location provider are you using? Doe it work when you switch to a different location provider in the trigger? What are the device settings for location, 'High accuracy'?

Regards,
Martin

Re: Location Condition Failure

Posted: 11 Nov 2015 07:42
by Zeench
Device: Samsung Galaxy Note 4
Android Version: 5.1.1

What do u mean with location provider? Maybe u mean Network / GPS / etc.?
I use Network because GPS wont work when Im in a Building.
The rest of the options are marked as experimental so i wouldnt use it.

Device setting to get location is high accuracy, as u mentioned.

The question is, y does it work with the action u mentioned a post earlier and not with the trigger....


When I switch to a different location provider would that influence my batterie up time?
I cant afford to discharge it any faster than now.

Re: Location Condition Failure

Posted: 12 Nov 2015 19:08
by Martin
Android provides different location providers (Standort Lieferanten) to determine the location (Network, GPS, High Accuracy etc.). Network and GPS are built-in providers of the device. The experimental location providers 'High accuracy', 'Balanced Power/Accuracy' etc. are the new location providers offered by Google Play services. The experimental providers nowadays work better on many devices so I would recommend to try to use one of the experimental ones for a few days to see if you get good results. Maybe I will remove the experimental label in one of the next versions of Automagic since it's working mostly stable. Theoretically the experimental providers should use less battery power.

It's really strange that the trigger does not work when action Init Variable Location does since both are similar internally. Maybe the device uses some kind of battery optimization that prevents the trigger from getting new locations after some time. The action would not be affected since it only runs for a very short period of time.
Could you please turn on Debug Log and Log to SD card in the preferences of Automagic and send me the log after the trigger failed?

Regards,
Martin

Re: Location Condition Failure

Posted: 13 Nov 2015 07:17
by Zeench
Hey Martin, thx for the provided informations.

Ill turn debug mode on, but i dont think it will happen again thx to the action i put in ;)
But if it happens again ill sennd u the log.

Thx so far.