You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I didn't find this in the docs, so posting here so that I might immediately find it in the docs and facepalm.
Is there a way to filter location results with a "maximum speed?"
My spouse and I each have apple devices tracked by icloud3 and vehicles which also report location. Each of us have both trackers assigned to our Home Assistant "person" - this works mostly as I would expect, though occasionally icloud3 "snaps" the person's location back to a previous point even though our car has a more recent and more accurate update. This results in straight lines from the vehicle's location radiating back to the icloud3 location origin as shown in this screenshot
is there a way to avoid this? I was thinking maybe a way to set a maximum reasonable speed since we obviously can't travel 60 miles in 5 seconds for instance. There's likely to be a simpler/more clever way to handle this, so I'm all ears for suggestions. Thanks for all your work on the integration!
The text was updated successfully, but these errors were encountered:
I didn't find this in the docs, so posting here so that I might immediately find it in the docs and facepalm.
Is there a way to filter location results with a "maximum speed?"
My spouse and I each have apple devices tracked by icloud3 and vehicles which also report location. Each of us have both trackers assigned to our Home Assistant "person" - this works mostly as I would expect, though occasionally icloud3 "snaps" the person's location back to a previous point even though our car has a more recent and more accurate update. This results in straight lines from the vehicle's location radiating back to the icloud3 location origin as shown in this screenshot
is there a way to avoid this? I was thinking maybe a way to set a maximum reasonable speed since we obviously can't travel 60 miles in 5 seconds for instance. There's likely to be a simpler/more clever way to handle this, so I'm all ears for suggestions. Thanks for all your work on the integration!
The text was updated successfully, but these errors were encountered: