noble/bleno

Calling bleno.disconnect() disconnects device but blocks new connection for another 20secs

Open

#333 opened on Aug 18, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (2,083 stars) (465 forks)batch import
help wanted

Description

Hi, I want to diconnect an inactive device, therefore I am calling bleno.disconnect(). The device gets disconnected - this is the expected behaviour but the device is not able to reconnect for another 20secs.

I am running bleno on a Nano Pi Neo Air, Ubuntu 16.04.2 LTS 4.11.2

hcidump -t -x outputs after bleno.disconnect():

2017-08-18 23:23:05.764200 < HCI Command: Disconnect (0x01|0x0006) plen 3
    handle 64 reason 0x13
    Reason: Remote User Terminated Connection
2017-08-18 23:23:05.767576 > HCI Event: Command Status (0x0f) plen 4
    Disconnect (0x01|0x0006) status 0x00 ncmd 1
2017-08-18 23:23:25.708081 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 64 reason 0x22
    Reason: LMP Response Timeout
2017-08-18 23:23:25.796586 < HCI Command: LE Set Advertise Enable (0x08|0x000a) plen 1
  01
2017-08-18 23:23:25.800573 > HCI Event: Command Complete (0x0e) plen 4
    LE Set Advertise Enable (0x08|0x000a) ncmd 1
    status 0x00

hcidump -t -x outputs this using nRF Connect:

2017-08-18 23:27:54.794896 > HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 64 reason 0x13
    Reason: Remote User Terminated Connection
2017-08-18 23:27:54.866602 < HCI Command: LE Set Advertise Enable (0x08|0x000a) plen 1
  01
2017-08-18 23:27:54.869356 > HCI Event: Command Complete (0x0e) plen 4
    LE Set Advertise Enable (0x08|0x000a) ncmd 1
    status 0x00

Thanks for your feedback!

Contributor guide

Tech stack
javascriptnodejs
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.jsBuetooth Low Energy basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue reports a 20 second delay between calling bleno.disconnect() and the actual disconnect completion, during which new connections are blocked. The user provides hcidump logs showing that after the disconnect command, the Disconn Complete event arrives after 20 seconds with a timeout, whereas using nRF Connect shows immediate completion. This suggests that bleno's disconnect implementation may be waiting for a timeout or not handling the Disconn Complete event correctly. To investigate, examine the bleno source code, likely in the src/bleno.js file or related C++ native addon, to understand how the disconnect() function interacts with the underlying BLE stack. Look for any timers or conditions that delay the response. A potential fix would involve ensuring that the Disconn Complete event is processed immediately to allow advertising to restart without delay.