Hello, DiegoConejeros ,
In this case, it is important to understand that TCP commands are responsible for this. The problem may be that the device is turning off or going into standby/sleep mode. Therefore, when a command is sent, the device may take time to turn on the timer or wake up from sleep.
The bottom line is that if the device is turned off (and the device turns off during sleep), then the TCP commands need the device to be connected. Most likely, in this case, the devices of your clients are disconnected at the time the command is sent, and therefore it takes time until the device gets back online.
From our side, the commands leave instantly if the device is connected. If the device is offline, the system waits until the device comes online.
In this case, you can speed up the sending of the command only if you increase the frequency of the device sending data to the system, so the device will go online more often.
Also, the device often has a heartbeat interval setting, this is a mode where the device sends heartbeat packets (lightweight data packets) to stay online, if your device has such a setting, try using it.
It is also better to check such cases on a real example.
Write us an email to firstname.lastname@example.org with your login, unit ID and the time when you sent commands and they did not work right away, then we can check and show what the problem was with an example.