noble/bleno

Complete Local Name vs Shortened Local Name

Open

#347 opened on Oct 27, 2017

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

Description

It looks like device names always end up in the Shortened Local Name field. I'd like to be able to specify that it be placed in the Complete Local Name field.

Filtering on device name using Web Bluetooth on a Mac does not seem to work with the Shortened Local Name field but it does work with the Complete Local Name field. Hence the need to have some control over how device name is advertised.

Thanks

device_names

Contributor guide

Tech stack
javascriptnodejs
Domain
backendapi
Issue type
feature
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 JavaScriptUnderstanding of BLE advertising
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the bleno library's advertising data handling, specifically the `setAdvertisingData` and `setScanResponseData` methods in the source code (likely in `lib/`). Understand how the device name is currently set to Shortened Local Name and explore how to add an option for Complete Local Name. Check the BLE specification for advertising data types.