"Location At" block weird behavior

[Alex]

I noticed that sometimes goes "No" route even though the location is within the radius I determined. 

The "Get Location" block  that I put right before finds the location very accurately so it's the issue with "Location At". Is there any reason that would cause it to fail 1-2 out of 10 times?

[Alex]

And it happens with both Google Play API on and off(gps and fused)

[Alex]

Also, not sure if that is related to this problem but when this issue happens the altitude shows -16

[Henrik "The Developer" Lindqvist]

Try using a larger radius.

Enable the Debug logging option in Automate settings to see what if/when is being told by the system.

The the Location at doesn't output altitude. Don't expect the Location get block to report the same location as the Location at block should be at, they use different systems.

[Alex]

So the "Location At" doesn't have to go right after "Location Get" block? In my case I put one after another cause I thought "Location At" gets the coordinates from "Location Get"... Maybe I should play a bit with it then. But anyway the accuracy is always about 5-20 meters and I have radius of 800 meters and it still goes to "No" path ~1 of 7 times

[Alex]

Just to clarify - I am using "Is At Location" with Proceed Immediately

[Henrik "The Developer" Lindqvist]

Mixing Location at and Location get block may not give an expected result since they use different systems that rely on different data, at different update rates, etc., e.g. the Location at API/block always use near by Wi-Fi, Bluetooth device, Cell towers, whatever, while for the Location get block you choose what to use GPS, etc..