About commands
We have a queue. You can either enable or disable it. We don't have a timeout.
I have searched the configuration file documentation, but it does not show how to activate or deactivate.
There a plenty topics about it, but Try
<entry key='commands.queueing'>false</entry>in the configuration file and restart the server.
Thanks you
Important to update this part Mr. Anton.
https://www.traccar.org/configuration-file/
Sorry, I actually provided you outdated information earlier. We don't support disabling queue. We did in the past, but not anymore. The configuration file doc is always correct for the latest official release.
Anton, What actually made you decide to not support disabling command queue anymore?
In the past i often had devices that where switched of directly when they where turned on (and then received the queued poweroff command once it came online).
To support commands for some devices we have to queue them. For example, OsmAnd protocol. So it's not as simple to have it completely disabled.
I see, on the other hand when a user only uses their own server for instance with devices which use the watch protocol then the other protocols are not relevant and it would still be a great option to have disable queued commands. Would it be and option to implement it, while other users which for instant use osmand just do not disable it since it was configurable.
I think a better option would be a timeout. And that's I think what we wanted to implement.
In that case a timeout means ?
Means that command will be queued for the timeout period of time. Zero means no queue.
Ok, that sounds as a great option to
Does Traccar have a built-in command queue or timeout mechanism for handling cases where a device does not immediately respond to a sent command? If so, is it configurable per protocol or globally?