I made the move and started using owntracks_http i was previously using cloudmqtt
I have been having a problem with my zones since making the swap, sometimes on my map the blue circle for my device can cover three zones in one, this then triggers all three automatons as the device is in three zones.
I have the below in my config
device_tracker:
platform: owntracks_http
max_gps_accuracy: 50
It is my understanding that the "max_gps_accuracy" will stop the false reports. I cannot find anything in the owntracks HTTP documentation to state that “max_gps_accuracy” can be used with the HTTP component but have seen serveral configurations where this is used in conjunction with owntracks_http
max_gps_accuracy (Optional): Sometimes Owntracks can report GPS location with a very low accuracy (few kilometers). That can trigger false zoning in your Home Assistant installation. With the parameter, you can filter these GPS reports. The number has to be in meter. For example, if you put 200 only GPS report with an accuracy under 200 will be take in account.
I am seeing GPS co ordinates with a larger accuracy than 50 as below, this covered all four of my zones and triggered all three automatons.
Am i miss understanding how the “max_gps_accuracy” works ? My device is reporting a GPS accuracy of “1000” this is the reason why all three zones have been triggered. I never had issues whilst using cloudmqtt and the only difference was my configuration was
device_tracker:
platform: owntracks
max_gps_accuracy: 60
waypoints: true