Hi,
I am testing the following device from Mictrack MT821/MT825. So far the platform and the devices seem to perform beyond expectation. For some reason I couldn't get the devices working on TCP even though HEX information that comes through is properly formed.
I am trying to test the delayed command features and because the devices are UDP the devices go from status:Online to status:Unknown after the configured timeout variable on the config file.
<entry key='status.timeout'>80</entry>
<entry key='server.timeout'>120</entry>
The problem that I am trying to solve is to be able to queue commands when the device status is unknown. If the device status is unknown and I try to push a saved command it will try to send it right away. The only way to push them to the queue is when the device is offline and if I am forced to use UDP that is something that never happens unless I restart the service.
I have already reviewed the whole forum and I've seen past post that thoroughly explain this issue and I was able to test it simulating a TCP connection. With a TCP connection it works fantastically well as soon as you close the connection the device is reported offline.
https://www.traccar.org/forums/topic/from-unknown-to-off-line/
traccar/traccar: Issue #3970
I am using traccar version 4.8.
Has anyone ran into the same problem by any chance and managed to sort it out?
Is there any straight forward way to force those devices offline without restarting the service?
Or is there any way to queue the commands when the device status is unkown?
Regards
Unfortunately it's not possible for UDP because there's no concept of connection. We never know if device is connected or not.
Hi,
I am testing the following device from Mictrack MT821/MT825. So far the platform and the devices seem to perform beyond expectation. For some reason I couldn't get the devices working on TCP even though HEX information that comes through is properly formed.
I am trying to test the delayed command features and because the devices are UDP the devices go from status:Online to status:Unknown after the configured timeout variable on the config file.
<entry key='status.timeout'>80</entry> <entry key='server.timeout'>120</entry>The problem that I am trying to solve is to be able to queue commands when the device status is unknown. If the device status is unknown and I try to push a saved command it will try to send it right away. The only way to push them to the queue is when the device is offline and if I am forced to use UDP that is something that never happens unless I restart the service.
I have already reviewed the whole forum and I've seen past post that thoroughly explain this issue and I was able to test it simulating a TCP connection. With a TCP connection it works fantastically well as soon as you close the connection the device is reported offline.
https://www.traccar.org/forums/topic/from-unknown-to-off-line/
traccar/traccar: Issue #3970
I am using traccar version 4.8.
Has anyone ran into the same problem by any chance and managed to sort it out?
Is there any straight forward way to force those devices offline without restarting the service?
Or is there any way to queue the commands when the device status is unkown?
Regards