All the commands of the client’s application are invoked by the Development Kit library and are processed asynchronously on a different thread. This means that the library returns either an ID of the invoked command or an error to the client’s application upon calling of the corresponding function.
In case the events queue is not allowed, the detailed result of the command execution is not available. However one can check whether the command is still in progress by calling FH_IsAsyncCommandWorking function.
Since the majority of commands change the computer’s and devices’ statuses to a certain extent, the info about the command execution is reflected in the corresponding data on the computer or device upon the successful command completion.
The info about computers and devices is received through the central server, that’s why certain pauses (splits of a second) are possible when getting the updated info.
Common for All Commands
The names of all asynchronous commands contain Async suffix.
All the asynchronous commands accepttimeoutMs parameter (timeout value in milliseconds) as the last argument. IftimeoutMs is set to –1, the command will use the internal timeout value.
All the asynchronous commands return the ID of the invoked command (integer digit not equal to zero) or 0, in case the command cannot be executed due to some reason (wrong arguments or the system status).
The command ID can be used for periodical polling to know whether the command is still being processed or whether it has already been completed. Use FH_IsAsyncCommandWorking function for polling.
The final result of the command execution is sent as an event through the events queue.
Refer to the “Result of Asynchronous Command Execution” chapter to read about JSON format of the object-event with the result of the command execution.
The possible error codes in the returned result are described in the context of each command.
Login computer into account:
Managing Computers in Account:
Managing Local Devices:
Managing Devices from Other Computers: