noble/bleno

Using Noble & Bleno, Noble's Peripheral Connection event emits Bleno's accept event.

Open

#303 opened on May 8, 2017

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

Description

Using Noble & Bleno, Noble's Peripheral Connection event emits Bleno's accept event.

I think this is quite wrong circumstance.

Cause Event with Central *connect* to Peripheral (Noble) and Peripheral *is Connected* to Peripheral (Bleno) might be quite different situation.

I'm not sure that I'm the only one having this problem.

Tested on Macbook 10.12 Sierra (early 2015) Broadcom 20703A1 with nRF51-dk.

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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
mostly clear
Prerequisites
Basic understanding of BLENode.js event systemFamiliarity with Noble and Bleno
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the connection event handling in Noble and Bleno source code, specifically the Noble 'Peripheral Connection' event and Bleno 'accept' event. Look for event name collisions or incorrect mapping in the way Noble emits events when connected to a peripheral. Review the comments in the issue for additional context. Test on the mentioned hardware setup if possible.