Device shows up in NrfConnect app as "non-connectable" despite he advertisement parameters being set to connectable.

RE: Device shows up in NrfConnect app as "non-connectable" despite he advertisement parameters being set to connectable.

Vidar Berg — Fri, 15 Nov 2024 07:45:32 GMT

Hi,

Customer projects will often have external hardware dependencies, etc that prevent the code from being run on a development kit. So by "minimal," I meant a project without any additional dependencies that can easily be tested on a DK. Sorry for not being more clear on that.

After the connect button is not showing, have you tried closing the app, toggling Bluetooth off and on from Settings > Bluetooth (not from the control center), and then reopened the app again to see if the problem persists?

I will ask our mobile apps team if this is something they have seen before.

RE: Device shows up in NrfConnect app as "non-connectable" despite he advertisement parameters being set to connectable.

RHOOD — Thu, 14 Nov 2024 21:26:42 GMT

Hey,

Thanks for getting back to me. It might be at least partially the Nrf Connect app bc I downloaded BLE scanner 4.0 and was able to connect and send data to my device even while Nrf Connect was showing it at non-connectable. I don't understand why the central_peripheral_hr app would work perfectly with Nrf connect though if it is an issue on your end. I am using the iOS version. I have not tried this with the Android version but I could. I could potentially send you some more of my code but I am not sure what is meant by "minimal version".

EDIT: Code does work with the Andriod version of the Nrf Connect app.

RE: Device shows up in NrfConnect app as "non-connectable" despite he advertisement parameters being set to connectable.

Vidar Berg — Thu, 14 Nov 2024 18:02:33 GMT

Hello,

This seems a bit strange. The advertiser should be connectable as long as the BT_LE_ADV_OPT_CONNECTABLE option flag is set. Could you provide a minimal version of your project that would allow me to reproduce the issue on an nRF5340 DK (I understand if this is too much work)? It may be a bug in the nRF Connect app, but I haven’t encountered this behavior before.

Are you using nRF Connect on Android or iOS? Note that the phone is allowed to cache the services and characteristics from the previous connection so it does not have to repeat the service discovery on every connection. This may be an issue when re-program the FW on the device because it may still be using the same Bluetooth address and therefore continue to appear as the same device to the phone.

Thanks,

Vidar