Search Device timeout

Does anybody know what is the timeout value for the Add Device (SDK) search? I'm having some problems adding some custom IP devices and I believe the issue is a timeout on the search given my devices take around 6 seconds to return the object.

Reply
7replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Can you clarify what you mean by the Add Device search? Do you mean the discovery or the initial device search?

    The device search (first step for adding a device) queries the SDK instance for the devices registered at startup so that would only be limited by the network speed between the Brain and the device running the SDK, the timeout should be 4 seconds.

    The discovery (second step, after a driver/device is selected) can take some time and waits on your reply from the SDK. The timeout there should be around 30 seconds on the Brain.

    Reply Like
      • Lucas
      • Lucas
      • 2 mths ago
      • Reported - view

      Thanks Patrick Fiaux 

      I'm talking about the initial Device Search. My RP3 takes around 6 seconds to reply back to NEEOs query string, so it looks like the brain is giving up on the SDK reply after 4 seconds. 

      Reply Like
  • OK so then the timeout is 4 seconds.

    It's strange because I've heard of lots of people using a RPi to run the SDK and usually there's no issues with the device search.

    Do you run other software on the raspberry pi that would limit the resources available to the SDK at the time a request comes in? Or do you have a lot of devices running on that 1 SDK instance (like more than a dozen)? Since the response for the query string is mostly handled by SDK code based on in memory information of the registered devices it shouldn't take long to respond. It definitely seems like 6 seconds is too long, I wonder what could cause it to take that long.

    Reply Like
      • Lucas
      • Lucas
      • 1 mth ago
      • Reported - view

      Patrick Fiaux Michael Kohler thanks guys!

      I don't think it's an SDK issue. I'm actually using an OpenHAB implementation, and I think 4 seconds is a fair amount of compromise in the name of UI responsiveness. But I think it would be a good practice for the brain to perform a backup round of requests with a less constricted timeout (before going idle). So you get both responsiveness and tolerance.

      Reply Like
    • Lucas maybe Tim Roberts knows why it takes more than 4 seconds, he wrote the OpenHab integration. To me it looks like you might stress the pi to much.

      Reply Like
      • Lucas
      • Lucas
      • 1 mth ago
      • Reported - view

      Niels de Klerk Yes, already asked him, I know he is working on a new version. Thx

      Reply Like
  • Additionally to Patrick's questions, have you tried running the driver on your laptop/desktop to see if it's a problem with the RPi or generally? If you want to send me the code to michael.kohler@neeo.com I'd be happy to test it out here as well.

    Reply Like
reply to topic
Like Follow