Search found 57 matches
- Tue Oct 28, 2025 4:28 pm
- Forum: ESP-IDF
- Topic: ESP32 Nimble passkey feature issue
- Replies: 3
- Views: 2447
- Sat Oct 25, 2025 7:15 am
- Forum: ESP-IDF
- Topic: ESP32 Nimble passkey feature issue
- Replies: 3
- Views: 2447
Re: ESP32 Nimble passkey feature issue
I would request you to check and confirm the io capability that are being set by you in the application . If it is being set to NoInputNoOutput, then pairing will not use passkey entry mechanism.
- Sat Oct 25, 2025 4:52 am
- Forum: ESP-IDF
- Topic: ESP32 Nimble passkey feature issue
- Replies: 3
- Views: 2447
Re: ESP32 Nimble passkey feature issue
I would check and confirm the io capability being set. If it is being set to NoInputNoOutput, then pairing will not use passkey entry mechanism.
- Wed Sep 17, 2025 10:09 am
- Forum: ESP-IDF
- Topic: Generating Random Private Resolvable Address using NimBLE
- Replies: 1
- Views: 361
Re: Generating Random Private Resolvable Address using NimBLE
Does setting own_addr_type as BLE_OWN_ADDR_RPA_RANDOM_DEFAULT in bleprph example here helps ?
- Tue Sep 16, 2025 6:11 am
- Forum: ESP-IDF
- Topic: linker error to unknown references in NimBLE source code
- Replies: 4
- Views: 864
Re: linker error to unknown references in NimBLE source code
When I use the jump to symbol tool in the menuconfig editor, it returns "no results" for BLE_STORE_MAX_CSFCS, BLE_STORE_CONFIG_PERSIST, or BLE_STORE_MAX_BONDS.
BLE_STORE_MAX_CSFCS and BLE_STORE_MAX_BONDS : Both are driven by menu config macro: BT_NIMBLE_MAX_BONDS
BLE_STORE_CONFIG_PERSIST ...
BLE_STORE_MAX_CSFCS and BLE_STORE_MAX_BONDS : Both are driven by menu config macro: BT_NIMBLE_MAX_BONDS
BLE_STORE_CONFIG_PERSIST ...
- Fri Aug 29, 2025 6:13 am
- Forum: ESP-IDF
- Topic: linker error to unknown references in NimBLE source code
- Replies: 4
- Views: 864
Re: linker error to unknown references in NimBLE source code
These are configurable from menuconfig. They have some default predefined values ( i.e. it is not 0 )
- Wed Jul 02, 2025 5:07 am
- Forum: ESP-IDF
- Topic: NimBLE_GATT_Server example characteristic descriptor
- Replies: 3
- Views: 887
Re: NimBLE_GATT_Server example characteristic descriptor
Hi,
.att_flags = BLE_GATT_CHR_F_READ
This is incorrect in descriptor.
Plesae instead use .att_flags = BLE_ATT_F_READ , and try
.att_flags = BLE_GATT_CHR_F_READ
This is incorrect in descriptor.
Plesae instead use .att_flags = BLE_ATT_F_READ , and try
- Thu May 29, 2025 9:45 am
- Forum: ESP-IDF
- Topic: OTA BLE and BLE SCAN at the same time, is it possible?
- Replies: 3
- Views: 222
Re: OTA BLE and BLE SCAN at the same time, is it possible?
> My issue is that I can't make them to work side by side.
Can you elaborate on what is working or not working in more detail , so someone may have inputs .
There is a BT_NIMBLE_HOST_ALLOW_CONNECT_WITH_SCAN configuration, which allows scanning and connection happen at same time. May be you can try ...
Can you elaborate on what is working or not working in more detail , so someone may have inputs .
There is a BT_NIMBLE_HOST_ALLOW_CONNECT_WITH_SCAN configuration, which allows scanning and connection happen at same time. May be you can try ...
- Tue May 20, 2025 7:26 am
- Forum: ESP-IDF
- Topic: Nimble BLE ESP32 not visible to Iphone 6s Plus
- Replies: 4
- Views: 355
Re: Nimble BLE ESP32 not visible to Iphone 6s Plus
> At this point, the question is: is it normal on Iphone that an ESP32 BLE device is not seen when I activate the discovery function?
Yes, this is specific to iphone where it searches certain specific adv pattern to show up device in the bluetooth settings screen.
You can try the hid device ...
Yes, this is specific to iphone where it searches certain specific adv pattern to show up device in the bluetooth settings screen.
You can try the hid device ...
- Tue May 20, 2025 7:23 am
- Forum: ESP-IDF
- Topic: Can't get BLE Pairing to work on ESP32-S3
- Replies: 2
- Views: 248
Re: Can't get BLE Pairing to work on ESP32-S3
Hi,
CONFIG_BLE_SM_IO_CAP_NO_IO=y
As seen in sdkconfig, the setting is to use No Input No Output. This will lead to "Just Works" method to be used, where pairing will happen with no user intervention.
If you want to not use JustWorks, you can change the IO Capability to some other form and then ...
CONFIG_BLE_SM_IO_CAP_NO_IO=y
As seen in sdkconfig, the setting is to use No Input No Output. This will lead to "Just Works" method to be used, where pairing will happen with no user intervention.
If you want to not use JustWorks, you can change the IO Capability to some other form and then ...