Hi Rodrigo, Can you access Models after following these steps ? Provisioning & Configuration of Models -> un-provisioning (using reset node option in #nRFMesh) -> re-provisioning & re-configuration of

+Sebastian, +Torsten Hi Patrick, I know there's been some discussion on the times you mention so I've copied a couple of people that might be able to explain why things are like they are and the

I solved it. I made a mistake while moving some of the function to the separated module. While preparing the example I noticed, that some of the functions in the USB CDC_ACM example, which I used as

Hi, first a disclaimer: I was not there yet when it was decided to go with CMake replacing what was there before in zephyr. I'm a big user of CMake. And with all my ignorance as to why things have

Hi Johan, Thanks for help! It seems the function " pairing_complete" in your proposal is enough to cover both failure and success cases, with the parameter "bool bonded", right? And I'm not sure

Yes, that is exactly it. In that case I am not sure about the issue. Perhaps Johan can bring some light into it. Carles From:"Li, Jun R" <jun.r.li@...> Date: Thursday, 14 June 2018 at

Yes, every time when I did the tests, I let iPhone “forget the device”, which I suppose to erase the bond info, right? Regards, Jun From: "Cufi, Carles" <Carles.Cufi@...> Date:

Hi there, Have you tried erasing the bond from iOS settings? I find that sometimes bonding fails if the device is already bonded, for whatever reason. Regards, Carles

Hi everyone, I’m trying to test the secured pairing with a NRF51 device by using an iPhone 6 and 7, and noticed different behaviors on different phones: iPhone 7: secured pairing is always

Hi, I am currently trying to map our current BLE GAP API to Zephyr BT API, but I find it a little bit unclear how the pairing/bonding flow is supposed to work on the slave side. From the

Thank you, however it is not ideal that one should read/understand the SMP to understand when a given CB is expected to occour. I have submitted the issue on GitHub. \Theis

Hi Theis, They map directly to the authentication methods from the Security Manager protocol. The lack of documentation for these is indeed an oversight. Could you open a github issue so we can

Hi, I am trying to understand the GAP API for Zephyr Bluetooth Stack, and came across bt_conn_auth_cb(…). This callback function seems to be completely undocumented. Anyone who know what the

As far as I am able to understand your description, this is expected to work. Perhaps you could share a minimal patch to an existing sample to demonstrate when the linker error

Thanks a lot for your help. I have tried your suggested solution with the CMakeList. Unfortunately, this did not work for me. I got the linker errors as described in my initial mail. Let me try to

Hi Rajat, This could be helpful https://devzone.nordicsemi.com/b/blog/posts/nrf-blinky-compatible-firmware-using-zephyr-blueto You've to make changes as per your Board design. regards, vikrant

Hi Jun, The second one is a bit ambiguous, since it'll also be called for subsequent connections when the connection gets encrypted, even though pairing is not in progress (it already happened over

Hi, I am getting this error. -- Selected BOARD nrf52840_pca10056 Zephyr version: 1.12.99 Parsing Kconfig tree in /home/vikrant/projects/zephyr/zephyr/Kconfig Using

Hi, In my BLE project, a passkey is required to access the NRF51 device; thus the callback functions of “struct bt_conn_auth_cb” were implemented to achieve secured paring. What I observed is

Hi Johan, Which app you used for testing ? Is it samples/boards/nrf52/mesh/onoff-app by adding persistent storage support ? Could you please test it for PR:8296 by removing NVS from it ? Thanks!!