Add New Device Timeout

[benfrancis]

Currently the Add New Device dialog will appear to keep scanning for new devices forever.

We should add a timeout (at the adapter layer, the UI layer, or both) and close open websockets when we're done.

[benfrancis]

We didn't get around to implementing this in 0.2, it would be good to get it into 0.3 so the spinner doesn't just spin forever!

[mrstegeman]

Should be easy enough to add, but what timeout? 30s?

[benfrancis]

@dhylands Do you know how long it takes for Zigbee and Z-Wave adapters to time out? If we could surface the timeout to the UI through the WebSocket API rather than use a fixed timeout that would be a better solution because otherwise things could get paired added after the timeout.

[mrstegeman]

The problem is that each adapter can have a completely different timeout. For instance, the TP-Link adapter is pinned at 3 seconds, because that's all it really takes.

[dhylands]

Zwave has no timeout. With Zigbee the timeout can be anything between 1 and 254 seconds. It's currently set to 180 seconds in the config.

[benfrancis]

How about if we set the Zigbee timeout to say 60 seconds (or 120 seconds?) and turn of Z-Wave pairing after that same period of time?

[mrstegeman]

Seems reasonable to me.