Replies: 2 comments
-
I think I can close this one myself with a quick re-test. If I don't specify a name in setadvertising, the default bangle name shows in NRF Connect but the device is still missing from the list in the (legacy) central app. So the name is not a factor in this case of the app not showing the device |
Beta Was this translation helpful? Give feedback.
0 replies
-
your device name is quite long, maybe updating softdevice to 6.1.1 would help with showing the name in the first case, default bangle.js name is shorter and fits into the limit of S140 6.0.0 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Creating a BLE service advertising through setadvertising on Bangle js2 shows no name when scanned. Could this prevent central devices from offering users the option to connect to the peripheral?
Advertising:
NRF.setAdvertising({}, {
: name: "Umpire Ball Counter",
: showName: true,
: discoverable: true , // general discoverable, or limited - default is limited
: connectable: true, // whether device is connectable - default is true
: scannable : true , // whether device can be scanned for scan response packets - default is true
: whenConnected : true ,// keep advertising when connected (nRF52 only)
: interval: 1000, //});
: phy: "1mbps,coded"});
Gives:
WARNING: Extended/coded advertisements can only be used with scannable:false. Disabling scan response.
Scanning in NRF Connect, Google Pixel 6, Android 15
Can connect on LE Coded successfully in NRF connect, but not shown in another app:
Beta Was this translation helpful? Give feedback.
All reactions