[BUG] Geofence distance not detected proper when saving fence

[Ltek]

avargaskun is 0.3 > 0.25 ?? ... I'm old, maybe things changed since I was in school? ;-)

It throws that error no matter decimal I put in, if its not exactly 0.25

Also, can you make the smallest entry 0.05? I have some locations I need to ensure tight distances. I'm using some Radius as .1 or even .5 with Margins usually at .1 or .2

[Ltek]

avargaskun just wanted to make sure you saw this

[avargaskun]

avargaskun just wanted to make sure you saw this

Hi! I will take a look this week. The error that shows when setting it to 0.3 definitely looks like a bug

The reason I made the lower limit 0.25mi is because in testing I found a lower value was unreliable when the location accuracy setting in the phone was set to 'medium'. A smaller radius could still be useful if you set the location accuracy to 'high' but it will consume more battery power because it will turn on the GPS more often.

I will make the change to lower the limit and add a warning. I will try to bundle it with another change I'm working on for dashboard management.

Thanks!

[RicardoG]

I think the problem Ltek reports is because his Radius is bigger than his Margin, which also happens to be the minimum value tolerated for the Radius.

Like Ltek, I also need tight distances. Otherwise, triggers will occur if I drive on major roads close to my house. I managed to do some troubleshooting (location accuracy set to medium) and was able to optimize false triggers by looking at the log and plotting the GPS coordinates on Google Maps to find out how far away the GPS thought I was. It was farther than I thought. So, I expanded the Margin significantly and reduced the Radius to below 0.25 and that fixed the accuracy issue for me. I hope you lower the Radius minimum value in a future version.

[acredding]

I have the same result with Margin set greater than Radius.

[acredding]

Message/error appears if increments are not equal or a multiple of 0.25