same here. i have a X-NUCLEO-IDB05A1 mounted on a nucleo 64, and the base Sensor demo FW running on the nucleo board (stm32F0, made some adaptation to the code).
nRF Connect works very well with it with no problem.
Windows 10 however is a different story. I have a CSR4.0 dongle connected to my pc, with the CSR harmony SW stack installed. I can catch the advertisement (i.e. the showing of the device as bluetooth, NOT the BLE advertisement), but when i click "Next" to add the device, i immediately get an error message saying "connection failed because an incorrect code was entered"... very good MS, telling my that the code THAT I NEVER PROVIDED is bad...
Also, NOT ONE (!) of the many choices of BLE scanners/readers for windows (including the C# BLE client samples), will not catch the BLE advertisement of my setup (again, nRF Connect works well with it).
Also, strangely enough, when i scan (with any ble scan app), i get two dummy BLE devices which i am 100% sure does not exist physically. i could not trace the reason why i see those records.
One of the records name is "BlueNRG". it is NOT my device because i changed its advertise name to "BlueNRG_TEST"
I must say, i am extremely disappointed from the BlueNRG product line. especially from the SW stack which was at least at the beggining very lean and non inclusive.
The support was also lacking to say the least.
I think that the BlueNRG is already a discontinued product by now.
shame they went so far with it, just to dismiss it for something new and shining
