Describe the solution you'd like
Right now, when the gateway requestor calls gate.execHaloCmd(cmd) and the command fails with a HaLo error for any reason, the error will be displayed on the executor (smartphone) side only. The user would have an option to retry the command and the call to gate.execHaloCmd(cmd) on the requestor side will be just left hanging until the command is finally executed succesfully.
In some cases the command would never succeed for many possible reasons. The retry mechanism should be removed in favor of propagating HaLo errors straight to the requestor side on the first failure and failing the call fast.
Describe the solution you'd like Right now, when the gateway requestor calls
gate.execHaloCmd(cmd)and the command fails with a HaLo error for any reason, the error will be displayed on the executor (smartphone) side only. The user would have an option to retry the command and the call togate.execHaloCmd(cmd)on the requestor side will be just left hanging until the command is finally executed succesfully.In some cases the command would never succeed for many possible reasons. The retry mechanism should be removed in favor of propagating HaLo errors straight to the requestor side on the first failure and failing the call fast.