Trouble connection multiple times : Bonding, error: 133

RE: Trouble connection multiple times : Bonding, error: 133

Simonr — Mon, 03 Jan 2022 08:43:17 GMT

Yes, you might want to use bonding in your application, the easiest way to implement a working solution would be not to use bonding, which is why I suggested that.

You can do bonding and I'd recommend doing so for security purposes, but if doing so, make sure that your application does not delete bonding information upon a disconnect, and make sure you don't forget the device when you disconnect on the central side either.

I think the ble_app_gls example project is well suited as reference for a peripheral project like this.

Best regards,

Simon

RE: Trouble connection multiple times : Bonding, error: 133

c.tessierpiart — Thu, 23 Dec 2021 13:15:01 GMT

But don't I want to be bonded for using CTS and Apple devices ?

RE: Trouble connection multiple times : Bonding, error: 133

Simonr — Thu, 23 Dec 2021 12:29:06 GMT

Hi again,

If you do advertising and connection like the ble_app_uart example project does, the device shouldn't pair to the application at all.

Best regards,

SImon

RE: Trouble connection multiple times : Bonding, error: 133

c.tessierpiart — Thu, 23 Dec 2021 08:49:56 GMT

Hi,

Thanks, as the application would be used regularly, what is the way of using the bond information ? So that it is not necessary to delete the bonds on both devices ?

RE: Trouble connection multiple times : Bonding, error: 133

Simonr — Thu, 23 Dec 2021 08:37:01 GMT

Thank you for the explanation.

Is the nRFConnect app you're seeing this 133 error message in the iOS, Android, or Desktop version of nRFConnect?

Since you're using the peer manager and connect/disconnect multiple times, I think what's happening is that you either start or complete pairing, then disconnect and one of the devices thinks they're paired while the other does not. Try making sure you delete bonding information on both devices before reconnecting. On the nRF side, you can do something like calling the following delete_bonds() function as part of your disconnect procedure, and then make sure you delete bond info manually in the nRFConnect app (top right dropdown folder has an option to do so).

/**@brief Clear bond information from persistent storage.
 */
static void delete_bonds(void)
{
    ret_code_t err_code;

    NRF_LOG_INFO("Erase bonds.");
    err_code = pm_peers_delete();
    APP_ERROR_CHECK(err_code);
}

Best regards,

Simon

RE: Trouble connection multiple times : Bonding, error: 133

c.tessierpiart — Wed, 22 Dec 2021 08:45:31 GMT

Hi,

I may have been unclear with my issue.

I have two issues that will hopefully be solve by one thing. The major issue is when I connect and diconnect multiple times using an NRF52840 Dongle and NRF Connect. In that case I receive the 133 error message.

The minor issue is when I test things with an Apple Device. When the Application rties to read a characteristic, it return a "Reading not permitted" message. As the Application is still very young, we did not test the same issue.

What makes me hope that the two issues might be solved at once is that I botched a bit the merge part of the CTS and UART exemple. The former using Peer manager and the latter only doing a basic Advertising.

RE: Trouble connection multiple times : Bonding, error: 133

Simonr — Wed, 22 Dec 2021 07:32:37 GMT

Hi Charles

We will be short on staff during the Holiday period, and delayed replies must be expected. We will be back to full staff on January 3rd. Happy holidays and happy new year!

When you say you're connecting multiple times, can you explain what you mean about that? Are you trying to connect to multiple devices, or do you connect, disconnect, and connect again to the same device and so on?

Are you only testing with an Apple iPhone as a central? I'm asking because the 133 error generally is seen on Android devices. Can you provide a detailed explanation of how you cause this error to occur. You can also try using the nRFConnect application for iOS/Android to see if you can recreate the issue there, where you also can get debug information from the phone side.

Best regards,

Simon