GT06 device does not block through notification.

[jeovajireh]

When sending the engine stop command through the map popup, the engine is turned off. When creating a geofence, placing it on the device, creating a notification to execute the stop command and adding this notification to the device, blocking does not occur. The name of the command appears in the logs, "engineStop sent", but the line responsible for the blocking is not sent.

To Reproduce

1 - Click on the device and create a geofence.
2 - Click on "Commands" and create a command named "Stop" that will execute Turn off engine.
3 - In "Notifications" create a notification, Type: Virtual fence exit. Channel: Command. Saved command: Stop.
4 - In devices, click on the device for which the geofence was created and in the "Connections" section, select "Notifications" Exiting the virtual fence.

Expected behavior
The expected behavior would be the same as sending the command through the map popup, which is:

Command sent by map popup:

2023-12-15 10:33:23  INFO: [T5d46b75e] id: 35951008305****, command type: **engineStop sent**
2023-12-15 10:33:23  INFO: [T5d46b75e: gt06 > 54.207.**.**] 787815800f000000004459442c303030303030230000e6c40d0a
2023-12-15 10:33:24  INFO: [T5d46b75e: gt06 < 54.207.**.**] 7878661500000000004459443d537563636573732100000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2023-12-15 10:33:24  INFO: [T5d46b75e: gt06 < 54.207.**.**] 0000000000000000000000000000000000000000000000000000000000000000000000000100a85ca80d0a
2023-12-15 10:33:24  INFO: [T5d46b75e] id: 35951008305****, time: 2023-12-15 10:33:11, lat: -8.44736, lon: -37.05403, speed: 2.2, course: 146.0

But the result in the log is this:

Command sent to the vehicle to leave the geofence:

2023-12-15 08:22:46  INFO: [T5d46b75e] id: 35951008305****, command type: **engineStop sent**
2023-12-15 08:22:46  INFO: [T5d46b75e] id: 35951008305****, time: 2023-12-15 08:22:43, lat: -8.43251, lon: -37.06834, speed: 7.0, course: 68.0

Application version: 5.8
Server version: 5.9

Thanks

[tananaev]

It's interesting that in the first example you included several lines after as a good practice, but in the second you did not and it's not possible to tell if the command was actually sent.

[jeovajireh]

It's interesting that in the first example you included several lines after as a good practice, but in the second you did not and it's not possible to tell if the command was actually sent.

Thanks for the quick response. It's because in the second example only these two lines appear in the log, nothing else, the next line is already routine for the GPS, sending the location.

[jeovajireh]

This "engineStop" message is only present in the src/main/java/org/traccar/model/Command.java file. In other words, theoretically it was supposed to execute the complete command.

[juniormelo26]

@jeovajireh This here solved my problem, which was the same as yours, J16 protocol GT06 did not block when leaving the fence. Anton advised us to insert this and it resolved it.
<entry key='server.instantAcknowledgement'>true</entry>

[jeovajireh]

@jeovajireh This here solved my problem, which was the same as yours, J16 protocol GT06 did not block when leaving the fence. Anton advised us to insert this and it resolved it. <entry key='server.instantAcknowledgement'>true</entry>

Thank you, I'll do more tests on Monday and get back to you and let you know if it's resolved.

[jeovajireh]

@jeovajireh This here solved my problem, which was the same as yours, J16 protocol GT06 did not block when leaving the fence. Anton advised us to insert this and it resolved it. <entry key='server.instantAcknowledgement'>true</entry>

Hello! Today I managed to finish the tests. Adding this line to the configuration file, the geofence started to work as it should.

Thanks