I am facing a similar problem where the device is showing online but position on map is frozen in one place despite the device moving, but doesn't update the position on map.
The same device when configured to report to the manufacturer's server it works fine, it's online and update positions in realtime as it moves.
Anyone with a solution.
I think the issue might have been indeed related to the new config setup required for the firebase push notifications. I haven't seen any more positions "freeze" after I entered the new firebase config. However, I still cannot explain the random position update on the map if we assume the firebase config was to blame for.
Try updating the config and then monitor the server. Note, that after you do the update, the device has to report at least one new position to get it reflected on the map. If the device is offline, the position will not be automatically updated to the last one (from the database).
Hi Victor, I am having the same problem, I handle close to 1000 devices and for a number of them I am having the problem that you mention, in some cases the devices show an erroneous location and date of days or even months before, despite the fact that in route reports everything seems normal and with current and real positions. I wanted to ask you how you solved this inconvenience and if you can guide me on this please, I would be very grateful.
Hello,
No the issue is still not resolved, I just experienced the same problem once again. Searching on the forum I saw this old post and remembered I had the problem before.
We thought it might be the firebase config back then but now with server version 6.1. the issue still persists.
The problem is still in force until now, it has not been solved the devices freeze randomly. Completely ruled out device problem as testing in DEMO if they work.
Urdanegui Castillo, are you using TCP or UDP protocol for the devices that are freezing?
Victor, did you figure this out?
I am having the same issue. Device is stuck in same position on map for 3 days. But a report shows correct locations. No errors anyplace I can find.