-
-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Movement faster that 50km/h seems not to be recognized #791
Comments
Have the same issue. |
We don't typically have trouble with speeds over 50 km/h. Can you please provide more details? Device type, OS version, HTTP server OS/sw/version. Logs would be useful as well, both from the device during a time when you say reports aren't frequent enough as well as servers logs of your HTTP endpoints. You might want to send logs to support@owntracks.org; please mention this issue number in the subject. |
@wombart you'll also need to explain to us what "going to the Main street" is supposed to mean. |
I apologise for the unclear statement. I meant after I drove my car onto a main road where you can drive faster. I have just tested it with my bike, when I went faster than about 30kmh the tracking stopped and it didn't start again. mode was Move |
@wombart and @thefaxe would you share your configuration / logs with us via support@owntracks.org |
After the last update on my iOS device running iOS 17.4.1 it appears that owntracks version 17.2.5. does not recognize movements faster than 50km/h in movement mode.
I use owntracks to report my data to a nextcloud instance in http mode. Since the last update tracking points when driving in my car are not sent to nextcloud when driving faster than approx. 50 km/h. When driving slower more datapoints are generated and sent to my nextcloud instance.
Is there anyone else who has this issue?
The text was updated successfully, but these errors were encountered: