Sometimes some commands fail with ERROR_COMMAND_TIMEOUT

Hi @bropat ,

Do you think, we can add a simple or exponential retrial mechanism into eufy-security-client? I have seen many warnings in docker output as below and retrial might help us to resolve this.

2021-10-12 14:09:22.993  WARN Station T8010NXXX - Result data for command not received 
{
  message: {
    sequence: 43,
    command_type: 1145,
    nested_command_type: undefined,
    channel: 1,
    data: <Buffer d1 00 00 2b 58 5a 59 48 79 04 88 00 00 00 01 00 01 00 00 00 01 00 00 00 00 00 00 00 64 30 64 61 38 35 64 35 62 61 31 38 33 66 32 37 37 63 33 64 37 65 ... 106 more bytes>,
    retries: 1,
    acknowledged: true,
    return_code: -133,
    timeout: Timeout {
      _idleTimeout: 20000,
      _idlePrev: null,
      _idleNext: null,
      _idleStart: 584022,
      _onTimeout: [Function (anonymous)],
      _timerArgs: undefined,
      _repeat: null,
      _destroyed: false,
      [Symbol(refed)]: true,
      [Symbol(kHasPrimitive)]: false,
      [Symbol(asyncId)]: 11886,
      [Symbol(triggerId)]: 112
    }
  }
}

[rpitera]

Thanks for taking the time to explain it; also thanks so much for the support and fix!

I guess I have to wait for @fuatakgun to implement the new code downstream, but as soon as he does I will test it and report back to you one way or the other. Again, my thanks.

[bropat]

@rpitera

And btw, welcome back - hope you enjoyed your holiday!

I enjoyed it very much. Maybe a little short, but better than nothing 😉

With the next version (1.2.0) that I would like to release today, I should have this problem under control 😃