Stuck at connectAndSetup #12
Labels
Comments
|
@snowbreeze I don't see the disconnect command in that HCI dump. Could you run again with the |
|
@snowbreeze any updates? |
|
I will update you tomorrow. On Mon, Jan 4, 2016 at 12:50 AM, Sandeep Mistry notifications@github.com
|
|
|
Scenario: I have 5 devices connected Initially. Something like All the sensors connected back, but B0:B4:48:B8:BD:86 didnt. My observations : When I am switching on/off the sensor, It somehow immediately disconnects before getting discovered(inside connectAndSetup), thus another connectAndSetup is called. Solution 1: Have a way to clear a ongoing connectAndSetup |
|
@snowbreeze got it! There is an unpublished change in noble to report the connection already exists case: noble/noble@9a746e0 Would you mind trying out the latest noble master ( |
|
I had seen this changes on noble, and manually updated the lib folder long back. Let me uninstall the noble and run this command and try again. |
|
@snowbreeze noble v1.3.0 has been published with the change, so a fresh install should pick up the change. |
|
Okay. I will do a fresh npm and try to reproduce
|
|
connectAndSetup not getting stuck. |
|
Still I see some instances where connectAndSetup is stuck. Will reopen if i can reproduce properly. |
|
In case the connection is stuck at connectAndSetup, can there be a timeout after which it will hit back with error saying timedout. |
|
Stuck again at connectAndSetup |
|
Stuck Again |
|
I am trying to reconnect on disconnect. Please help out. |
|
The route cause of A workaround could be placed in noble-device to listen for a disconnect event after connect and bail on any operations, then call the callback. On a side note, I'm not sure why the " Connection Timeout" is occurring: |
|
Hi @sandeepmistry , are there any updates on this ticket? Thanks for all your hard work, I appreciate this library. I believe I am blocked on the same issue. Sometimes by device disconnects and I need to have the device reconnect when that occurs. Currently I have do a discover for devices on disconnect but it stalls on the connectAndSetup. I am not 100% certain I have the same problem as @snowbreeze but here is my HCI dump: |
|
@yowakita still dependant on noble/noble#111 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes, there is no callback from connectAndSetup.
Then If I try to disconnect() and call connectAndSetup() again, It will hit the callback twice.
If we could have something, that either cancels a connectAndSetup callback, or much cleaner, if we could have the callback hit at all times.
Hci dump when the connectAndSetup is stuck
The text was updated successfully, but these errors were encountered: