Connect uart_peripheral with Windows 11

[Neil Benn]

Hello,

  I've taken the peripheral_uart sample and ripped all of the uart stuff out so that it currently just connects and logs anything received to the console - the simplest example.  I can connect with my phone (Android), no problem.  However when I try to connect with windows 11 using either the system connection, Bluetooth LE Explorer, examples using Bleak (python library) and pyble I consistently get a loop of:

00> [00:06:58.461,090] <inf> brikwiz_base: Connected D4:D8:53:4C:5D:23 (public)
00> [00:06:58.792,205] <inf> brikwiz_base: Disconnected: D4:D8:53:4C:5D:23 (public) (reason 19)

  I understand that the reason 19 is that the client has disconnected but I cannot understand what is happening.  I've looked around the internet and there doesn't seem to be a solution.  Can you assist to provide any advice as to why you cannot connect to the peripheral_uart example with windows please?

Cheers,

Neil

[Neil Benn]

Hello,

  This would make sense and/or the windows pairing process trying to use the system bluetooth was not complete- however I've done too much to determine which it is.  I'll create the use cases to determine which it was and go from there as I'll obviously not want this to happen in the field as I'm making a B2C product.  For now I'll close this ticket and thanks very much for your help.

Cheers,

Neil

[Bernat]

Hi Neil!

Could you found the root cause of the problem? I'm facing the same problem and it's quite frustrating...

I also use Bluetooth LE Explorer, but only to pair the BLE device to the Windows 11. Once paired, I forget about this software and use C# with .NET 6 Core to communicate with the devices.

I've developed several projects, involving heart rate monitors (like the Polar, or the Coospo optical one), or even using the ESP32 as a BLE module and implementing the services and characteristics by hand. They all pair and connect fine to my PC. So, for the first time ever, I'm having trouble with a module from EByte (E104-BT5005A) which uses a nRF52805. If I try enough times, I get the Bluetooth LE Explorer to connect 1 out of about 20 times, but I still could never paired to it.

Is it a problem from the nRF stack? It seems clear it's not a problem from Bluetooth LE Explorer, since I could pair all kind of BLE devices UNTIL now...

Thank you!