Dear all,
when I use the Trigger "Standort" (German, English: "location"?) and then check location_accuracy, it is always "0.0". The documentation says it would be set.
If I use the action "initialize location variables", it is set, but that takes again some time, so I want to avoid this workaround.
Is this a bug or my fault?
cheers
location_accuracy not set
Moderator: Martin
Re: location_accuracy not set
Hi,
This is a bug in the documentation and a bug in the location trigger since Android does not even provide an accuracy when a location alert is triggered. The location trigger in Automagic by mistake uses the default value of zero to set the accuracy in this case. I will remove the accuracy variable from the location trigger documentation in the next update.
You have to use an action Init Variable Location to properly set up all location variables. I will extend the action to fetch the last known location from Android which is available immediately and should be up to date in such cases.
Regards,
Martin
This is a bug in the documentation and a bug in the location trigger since Android does not even provide an accuracy when a location alert is triggered. The location trigger in Automagic by mistake uses the default value of zero to set the accuracy in this case. I will remove the accuracy variable from the location trigger documentation in the next update.
You have to use an action Init Variable Location to properly set up all location variables. I will extend the action to fetch the last known location from Android which is available immediately and should be up to date in such cases.
Regards,
Martin