noble/bleno

Disconnect after read/write secure characteristic

Open

#221 创建于 2016年8月26日

在 GitHub 查看
 (4 评论) (0 反应) (0 负责人)JavaScript (2,083 star) (465 fork)batch import
help wanted

描述

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

贡献者指南

技术栈
javascriptnodejs
领域
backendsecurity
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Node.js basicsBLE conceptsBlueZ setup
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
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.