Traccar: zone in "state" is wrongly set

[ildar170975]

The problem

Due to GPS/GLONASS issues, a mobile device may jump from one place to another.

Here is a path of some Traccar device_tracker:

Note a zone mark on the map.

According to logbook, the tracker was at this zone 10.11.23 22:50:40.

But it is clearly seen that the tracker was never been there. The tracker was "away" at ~22:50 (which seems to correspond to 22:49:40 in the Logbook). Coordinates are: 55.7367167, 37.9266267.

And due to unknown reasons the tracker set it's state to a zone which is rather far from this point. Coordinates of the zone are: 55.7521633641602, 37.88753271102906. The zone radius = 125 m.

Calculated distance between a point and the zone is: 3 km

What version of Home Assistant Core has the issue?

2023.11.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Traccar

Link to integration documentation on our website

https://www.home-assistant.io/integrations/traccar/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @ludeeus, mind taking a look at this issue as it has been labeled with an integration (traccar) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `traccar` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign traccar` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

traccar documentation traccar source _{^{(message by IssueLinks)}}

[ludeeus]

And what is reported on the traccar server?

[ildar170975]

Traccar server reports same coordinates. So my question is only about a zone assigned by HA.

But I think I found a reason. Check this data from a server:

The accuracy was 3490.6. Probably it covered the wrongly selected zone.

[ludeeus]

That would do it. You can change the integration configuration if you want to ignore this. https://www.home-assistant.io/integrations/traccar#max_accuracy

[ildar170975]

@ludeeus Thank you for helping!