Hello @DClyn ,
Thanks for your post.
We saw your emails and answered you.
There were no issues on the side of our software or servers.
There is a an issues with timestamp in the messages coming from your device.
This is a common issue with some older devices. For various technical reasons, their internal clocks can “roll over” and reset to a default starting date (an epoch date), which might be many years in the past.
When a tracker sends data with an incorrect timestamp (e.g., a date from the year 2006), our system cannot process it correctly, which is why the notifications stopped, even though the trackers themselves seem to be working.
There are three common ways to solve this problem:
Firmware Update (Reflashing): The most reliable solution is to update the firmware on your devices. Manufacturers often release updates to fix these time-related bugs. Please check the manufacturer’s website for your specific tracker models for the latest firmware and update instructions.
Configuration: It might be possible to fix this through the device’s configuration settings, for example, by manually setting the correct date and time or adjusting the time synchronization parameters.
Restart the tracker in the open air. Usually, it is enough to turn it off for a while and then turn it on again. This must be done in the open air so that the tracker “sees” the satellites and records the correct time. This step is not the most effective, but it works with some tracker models.
We recommend starting by restarting the tracker and checking the configuration.
