Hi,
I'm using a custom protocol for Micodus devices that worked flawlessly in Traccar version 6.6. When sending commands, the commandResult event was generated instantly—within the same second the device responded.
After upgrading to version 6.10 and using the exact same protocol files, I noticed a consistent delay of about 3 seconds between sending the command and receiving the commandResult event.
My question is: Has something changed in the event handling architecture between versions 6.6 and 6.10 that could explain this delay?
Thanks in advance
We delay data by a few seconds by default. That's to detect if device is uploading buffered data and process it in the chronological order. It's configurable.
Thanks. Solved in the configuration file <entry key='server.buffering.threshold'>0</entry>
Hi,
I'm using a custom protocol for Micodus devices that worked flawlessly in Traccar version 6.6. When sending commands, the commandResult event was generated instantly—within the same second the device responded.
After upgrading to version 6.10 and using the exact same protocol files, I noticed a consistent delay of about 3 seconds between sending the command and receiving the commandResult event.
My question is: Has something changed in the event handling architecture between versions 6.6 and 6.10 that could explain this delay?
Thanks in advance