events that produce false alarms gt06

Hello dear colleagues, happy 2025.

I have several GT06 protocol devices implemented on my platform, but since the update to version 6.5, it generates panic alarms every time the herbeat is updated; this happens very frequently. I have analyzed the log and I do not see many differences in each packet sent by the device. I attach a piece of the verified frames so that you can give me your contributions and find a possible solution to the problem.

Also, if it is necessary to send additional data, I remain attentive. The alarms that they produce are the SOS of the wanwaytech gs10 device.

2025-01-02 19:33:18  INFO: [T78f8b1b9: gt06 < 190.130.105.112] 787811010865468051029307280100020012e0d70d0a
2025-01-02 19:33:19  INFO: Event id: 865468051029307, time: 2025-01-02 19:33:19, type: alarm, notifications: 1
2025-01-02 19:33:36  INFO: [Tae942121: gt06 < 190.130.106.224] 78781101086546805102930728010002001594680d0a
2025-01-02 19:33:36  INFO: Event id: 865468051029307, time: 2025-01-02 19:33:36, type: deviceOnline, notifications: 0
2025-01-02 19:33:37  INFO: Event id: 865468051029307, time: 2025-01-02 19:33:37, type: alarm, notifications: 1
2025-01-02 19:33:40  INFO: [Tae942121] id: 865468051029307, time: 2025-01-02 18:21:24, lat: 6.14156, lon: -75.26630, course: 144.0
2025-01-02 19:33:40  INFO: [Tae942121: gt06 < 190.130.106.224] 79790020940a08654680510293077321016286922400895710160220571021470017d6660d0a
2025-01-02 19:33:40  INFO: [Tae942121] id: 865468051029307, time: 2025-01-02 18:21:24, lat: 6.14156, lon: -75.26630, course: 144.0
2025-01-02 19:38:51  INFO: [Tae942121: gt06 < 190.130.106.224] 79790020940a086546805102930773210162869224008957101602205710214700182e910d0a
2025-01-02 19:38:51  INFO: Position filtered by Duplicate filters from device: 865468051029307
2025-01-02 19:44:07  INFO: [Tae942121: gt06 < 190.130.106.224] 79790020940a086546805102930773210162869224008957101602205710214700193f180d0a
2025-01-02 19:44:07  INFO: Position filtered by Duplicate filters from device: 865468051029307
2025-01-02 19:49:24  INFO: [Tae942121: gt06 < 190.130.106.224] 79790020940a0865468051029307732101628692240089571016022057102147001a0d830d0a
2025-01-02 19:49:24  INFO: Position filtered by Duplicate filters from device: 865468051029307
2025-01-02 19:54:44  INFO: [Tae942121: gt06 < 190.130.106.224] 79790020940a0865468051029307732101628692240089571016022057102147001b1c0a0d0a
2025-01-02 19:54:44  INFO: Position filtered by Duplicate filters from device: 865468051029307
2025-01-02 19:59:59  INFO: [Tae942121: gt06 < 190.130.106.224] 79790020940a0865468051029307732101628692240089571016022057102147001c68b50d0a
2025-01-02 19:59:59  INFO: Position filtered by Duplicate filters from device: 865468051029307
2025-01-02 20:07:00  INFO: [T232de863: gt06 < 190.130.103.72] 78781101086546805102930728010002001e2abb0d0a
2025-01-02 20:07:01  INFO: Event id: 865468051029307, time: 2025-01-02 20:07:01, type: alarm, notifications: 1

You can use computed attributes to remove it.

Hi Anto, Hi Anto, thank you for your answer, you know how the expression I must create to correct this error would be???

You need to return a null value.

HELLO ANTO,

Thanks for the contribution, I have made an alarm type expression to cancel the false alarms but I still receive false alarms:

SOS GS10G alarm type == 18 ? "sos" : null string

I use this type 18 expression because it is the only parameter that identifies the SOS alarms.

But they still continue to arrive, of course I have assigned the attribute to the device. I leave an image of what I receive when generating the alarms.

image popup status

I appreciate your valuable contribution to resolve this issue... Happy day.

And you're sure you're using the latest version of Traccar?

Hi Anto, I'm using the 6.5 preview version from 60 days ago. Is the bug fixed in version 6.6?

Not sure if it's a bug, but I would definitely recommend upgrading first.

Hi Anto,

I have updated to the official version 6.6 to see if we can fix the bug with the device's false notifications, but we still find that they keep coming. I also see that the device sends the heartbeat verification but on the web its status is offline.

Regards,