Notification-triggered commands work on one device but not another – is this device-dependent? How to check for errors?
Have you checked logs?
Yes, and the logs look correct. But in the event report search, it doesn't show sent either. And the command doesn't reach the device. Is there a security lock or something?
What event are you expecting? If you see the command I'm logs, it means it was sent to the device.
When sending the lock manually, “lock sent” appears in the reports, when sending systemically, especially for this device, it appears in the log but does not display this message in the event reports. Is there a simpler way to debug this?
If it's in the logs, it means it was sent, as I said earlier.
Make sure you're not using UDP. Since there is no session teardown notification on UDP for traccar if the teardown is performed by a CGNAT gateway, Traccar assumes the packets made it.
Always use TCP, that way Traccar should never say the command made it if it actually didn't make it.
UDP is great for basic GPS tracking, but not recommended if you are sending commands via the IP connection.
In this case, the tracker works on the TCP protocol. The difference between a direct block submission and automatic submission when triggering an event is the result below.
Hello,
I'm experiencing an issue where event-triggered notifications that execute commands work correctly on one device but fail on another. Could this functionality be device-dependent?
Additionally, is there a way to check logs or debug information to identify potential errors causing this inconsistency? Any guidance would be appreciated.
Thanks in advance!