Why dont you look at the log?
I have already checked the logs.
The device connects normally, the protocol is identified correctly, and there are no errors in the logs (no checksum errors, no rejected positions, no unknown device messages).
The strange behavior is that when I create a new device entry for the same tracker, it starts updating positions immediately, but the original device entry never updates, even though it shows as online.
You still don't want to share logs? You provided very little real information for us to help you.
are the reported positions to traccar always the same?
or is that the device is not sending positions?
Just confirmed the issue is on server side.
I redirected devices to testing server and they work fine, redirected again to produyction server and server insists he's receiving the same coordinates over and over.
Testing server is arm64 runing Linux using openjdk since provided java don't work at all.
Production server is x86-64 running linux with provided java.
Both 6.11.1
Clearly traccar went bonkers, not recovering even after a restart.
Device issue discarded because device sends correct data to another server.
Domain issue discarded because symptom is the same even when sending data to server IP instead of URL.
Man in the middle discarded because creating a new device with the SAME identifier and keeping the same data connection traccar starts to accept incoming data correctly. (changing old device identifier to bonkers)
I guess this must be some limitation on traccar side, or some miscalculation, or even it's own cache.
It happened to my own bike but after 24 hours started to work correctly on it's 24 hours later.
On other 3 vehicles I worked it out by creating new devices and changing the old device ID to something else.
Now everything is working fine.
This already happened to me in the past, I can't remember when, but was only once and this was the way I have done it also.
Since it was only one device I never took anything from it, but now, 4 devices, not the same model, not the same brand, not the same time, not the same place.
It sounds like only one thing is bonkers here.
Yea, traccar is.
The only time I've ever had this happen to us, it was caused by timestamp/timezone issues that we caused. Essentially the position data was being received but was in the past.
The very first thing to do is monitor the traccar logs and look at the raw position data being received, then decode it yourself to see what traccar is seeing. We use Teltonika trackers, so I just get ChatGPT to decode it by telling it that the string of data is Teltonika "Codec 8" format.
I have a vehicle tracker that shows as online and working properly, but it does not update its location on the platform.
When I register the same tracker on another device or another platform, it updates the location correctly, which suggests the hardware is not faulty.
Has anyone experienced this before?
What could cause this issue (protocol configuration, port/IP settings, device registration, server logs, etc.)?