Make connection failure behaviour more robust
thepoweroftwo opened this issue · 1 comments
thepoweroftwo commented
Right now, the TTGO-TBeams go into bluetooth sleep after a while.
If the library then tries to read/write from device, it is no longer available, so it fires the "disconnected" event and tries to reconnect three times (with an exponentially increasing wait time between tries).
This could lead to confusion, because the behaviour when using http is different, as there is no real connection state.
Proposed behaviour:
Make behaviour consistent so that it is clear when a device is finally disconnected and connect needs to be called again.
crossan007 commented
Related topic: I recently added onHTTPTransactionEvent: 3004c06