Time delay - Service status "ON" - probably an enhancement request
On Android you can use any third party scheduling apps like Tasker, Llama and other similar apps. Unfortunately there is no such option on iOS at the moment.
Thank you. I assume that you have not interest in adding such a feature - true?
On a slightly different topic. I have repeated some testing with the latest release of the client that I have run a number of times with the previous release using 30 second sampling while driving down the highway with the same phone is the same place - on the seat of my car. The only change is the new release of the Client. I have tried both medium and high location accuracy with the same results.
I find that with the new release the position will not change for 10 to 20 samples even when i am driving down the highway at 70MPH.
- Could this be an issue with the newest client release?
- Where can I get a copy of the previous release so I can do side by side comparisons?
Depends on the number of people interested in feature we might consider implementing it.
Traccar Client never changes frequency based on speed. You can find previous releases on GitHub.
Thank you. I was not clear on the sampling issue. While driving the position reported the Client do not change - lat and lon remain the same. Here is a sample:
2018-01-15_13:25:13_37.740508_-122.399182
2018-01-15_13:25:50_37.740508_-122.399183
2018-01-15_13:26:34_37.740508_-122.399183
2018-01-15_13:27:04_37.740508_-122.399183
2018-01-15_13:27:34_37.740508_-122.399183
2018-01-15_13:28:04_37.740508_-122.399183
2018-01-15_13:28:34_37.740459_-122.399193
2018-01-15_13:29:10_37.740516_-122.399181
2018-01-15_13:29:49_37.740507_-122.399183
2018-01-15_13:30:19_37.740508_-122.399183
2018-01-15_13:30:49_37.740508_-122.399183
2018-01-15_13:31:19_37.740508_-122.399183
2018-01-15_13:31:49_37.740508_-122.399183
2018-01-15_13:32:19_37.740508_-122.399183
2018-01-15_13:32:55_37.740508_-122.399183
2018-01-15_13:33:25_37.740508_-122.399183
2018-01-15_13:33:56_37.740508_-122.399183
2018-01-15_13:34:38_37.586686_-122.333626
2018-01-15_13:35:10_37.586686_-122.333626
2018-01-15_13:35:46_37.586686_-122.333626
2018-01-15_13:36:22_37.586686_-122.333626
2018-01-15_13:36:52_37.586686_-122.333626
2018-01-15_13:37:22_37.586686_-122.333626
2018-01-15_13:37:52_37.586686_-122.333626
2018-01-15_13:38:30_37.586686_-122.333626
2018-01-15_13:39:00_37.586686_-122.333626
2018-01-15_13:39:41_37.586686_-122.333626
2018-01-15_13:40:11_37.586686_-122.333626
2018-01-15_13:40:49_37.586686_-122.333626
2018-01-15_13:41:27_37.586686_-122.333626
2018-01-15_13:41:57_37.586686_-122.333626
2018-01-15_13:42:54_37.586686_-122.333626
2018-01-15_13:44:17_37.494416_-122.225848What accuracy are you using?
At that time - high. I ran the test in High and Medium with the same type of results. I truncate the lat and lon to 6 decimal places on input. At times during my test run it worked as one might expect.
Note that if your phone doesn't have a GPS signal the app might use network location, which can be very inaccurate. Have you checked accuracy?
Yes, the first occurrence of a location is correct - on the highway I was driving along. That location (lat and Lon) is then repeated for a number of samples - some time as few as five samples but at other time as many as 34 samples (=17 minutes = 18 miles) for example - sample time advances by 30 seconds but the lat and lon are unchanged. As I said before, I have done this test before with the previous release of the client - same 5se phone and trip.
You haven't answered my question.
Sorry, maybe I do not understand the question? I assumed that you were asking were the positions in the correct place? Here is an example of the data coming from the client
/?id=408398????×tamp=1516052764&lat=37.473072&lon=-122.162064&speed=0&bearing=0&altitude=5.840746879577637&batt=60.00000381469727when the lat and lon are repeated, they look like this:
/?id=408398????×tamp=1516052574&lat=37.586686&lon=-122.333626&speed=0&bearing=0&altitude=-1&batt=61The speed and bearing values are always zero
Looks like you are not using some ancient version of Traccar Client, or you are not using official version at all.
Interesting - I down loaded it from the apple apps store. I just deleted the version on my iPhone and downloaded it again from the Apps Store. I did it two times to make sure. The app store say it is version 5.4? I get the same type of message from the client.
I get the same type of message from the client.
?id=408398????×tamp=1516080600&lat=37.272616&lon=-122.034712&speed=0&bearing=0&altitude=121.8214721679688&batt=47Looks like accuracy attribute is not supported on iOS side yet. For some reason I thought you are using Android. On iOS location data comes directly from the system. We don't use any extra libraries, so if location is not correct it means your phone reports it that way.
OK - That is easy to test:- I can run the client and another App on the phone at the same time - if the phone's location is not being updated both should get the same error.
I am successfully using the client to track racing sail boats on San Francisco Bay. I have an issue with people not remembering to set the Service Status to "ON" before the start of the race - about 30% forget. If there was an option to set the Service Status to come "ON' at a user enter local time - just an hour would be sufficient e.g at 11 = 11AM. This enhancement would allow the client to come "ON" at an hour set up well before the race starts - like over morning coffee. Hopefully this would drive the 30% number down.
Thank you