noble/bleno

Disconnect after read/write secure characteristic

Open

#221 opened on Aug 26, 2016

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

Description

Hi, I'm facing the same issue as in Issue 71 and tried all the mentioned solutions. Currently I am working withe BlueZ 5.41 (via Homepage), node v4.5.0 and noble/bleno v1.6. I am able to read and write to my on application (peripheral on Linux Mint 17.2) with my smartphone (Android, nRF Connect app) but as soon as I add the "secure" filed in the characteristic the devices disconnect on write/read request. The also disconnect on bonding. Any Solutions?

Thanks for any help, TheClown

Contributor guide

Tech stack
javascriptnodejs
Domain
backendsecurity
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
needs investigation
Prerequisites
Node.js basicsBLE conceptsBlueZ setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the disconnection issue when adding 'secure' flag to BLE characteristics. Review linked issue #71 and comments for potential solutions. Test with different BlueZ versions (e.g., 5.41) and Node.js versions. Check the bleno library's handling of secure characteristics and bonding. Provide a minimal reproducible example and logs from both peripheral and central sides. Consider whether the issue is related to BlueZ compatibility or bleno's implementation.