It is frustrating that max_gps_accuracy is not available for all device trackers. This results in false triggers for zones when a tracker that doesn’t support the setting reports some highly inaccurate location that overlaps a zone.
Not all device trackers have GPS.
True. Let me clarify my WTH. iOS tracker uses max_accuracy. Owntracks uses max_gps_accuracy. These are the two GPS based trackers that I use. Not sure what others are using, but there is not standardization around the parameter name that is being used. For my use case, both integrations are running on the same device. I can’t think of any use case where I would need the accuracy setting to be different based on which integration is reporting the location. They both use the same GPS, so the accuracy should be the same and the setting should be at the device level.
Running HASS 0.112.5 and doing the same thing, Owntrack and iOS app device trackers for the same phone.
Both device tracker entities are using gps_accuracy, what version of HASS are you running?
If you are talking about configuration variables, Owntrack does have max_gps_accuracy, but I can not find any way to define GPS accuracy the Moble App integration.
You are correct. The gps_accuracy field I found was for manually setting a location via service. I don’t think the ios integration has that setting.