Without a good documentation it is hard to figure out whether there is a error, bug or this is by design.
I do not see dist_to_zone attribute. There are: unit_of_measurement, friendly_name, nearest and dir_of_travel.
dir_of_travel is confusing. I have a large zone, and when I’m in the zone, I am expecting “arrived” value. But it could be unknown or towards. The Map shows the correct location.
How ignored_zones affects dir_of_travel “arrived”, when zones intersect? Can I use ignored_zones to subtract one area from another? I want to have an ability to detect that I am in a zone, but not in overlapping zones. Can ignored_zones help?
ignored_zones: “proximity is not calculated for a device” - what does that mean? I see all the updated proximity attributes, when I am in the ignored zone. If proximity is not calculated, then what are the defaults?
If GPS Logger sends updates only when location is changed, or the update interval is long, then after which amount of time dir_of_travel becomes “stationary” without new updates? I saw “stationary” when I was at work with such GPS Logger settings.