J16 (GT06) Device Creates Database Entries During Heartbeat in Sleep Mode
Have you tried the duplicate filter?
Yes, I tried using the duplicate filter, but it didn't work as expected.
I'm still receiving heartbeats from the device, and it's recording the information in the database instead of just pinging the device to keeps it online.
The outdated filter worked correctly, but when the ignition is turned on or off, the event is not generated in real time. It only comes with the next position update from the device, which includes the ignition status and the event.
I believe this happens because the device is in sleep mode and has no GPS signal at the moment the ignition is turned on. Because of that, I think the outdated filter discards the information.
This filter works, but it causes a delay in receiving the ignition ON and OFF events. I haven’t tested the alarms yet to see if there’s also a delay, but even so, it’s not viable.
Yeah, it probably won't work if you want to filter the data, but then also keep some.
Is there any other way...?
One option I can think of is enable filtering but set skip limit. That way you can basically control reporting interval on the server side and make it much higher than what you can on the device.
SZCS#SLPDISCONNECT=1 disconnects the device from the platform, wakes up if there are events such as power on, vibration, power failure, etc.
No more ping every 3 minutes
Yes, I use this command on the devices as an alternative, but it disconnects from the plataform and if I want to send a command, I need it connect, that's the problem.
I use these 2 commands and the sms, it works normally
SZCS#SLPDISCONNECT=1
SZCS#GPS_DISSLP=1
Good evening, everyone.
I would like to ask for support regarding the Traccar platform. I have many tracking devices, most of them are J16 models using the GT06 protocol.
The issue I'm facing is that on the Traccar platform, when the device is in sleep mode (ignition off), it sends a heartbeat every 300 seconds, which is the configured interval. These heartbeat messages generate entries in the database. This doesn't happen with other devices — they don't generate database entries during sleep mode, and the device keeps online.
However, with the J16 devices, these times (deviceTime and serverTime) are updated every time a heartbeat is sent, but the fixTime remains the same as the last valid GPS signal. I would like the device to stay online via heartbeat only, without creating these repeated position entries in the database.
I’ve tried using the filter.outdated configuration, and although it works to some extent, it causes a delay of about 2 to 3 minutes for the platform to recognize when the ignition is turned on or off (i.e., when it receives "IgnitionOn" or "IgnitionOff" events). It seems like these events are also being filtered out by the outdated filter.
I’ve also tried increasing the heartbeat interval to at least 10 minutes to reduce database entries, but according to the device supplier, the maximum interval allowed is 300 seconds.
Does anyone have any advice or suggestions on how to handle this?
https://i.ibb.co/pBccw0SD/Captura-de-tela-2025-04-07-182333.jpg
Thank you in advance!