I want to reliably know if a BT device is actually within range and available. I am testing with 2 XP systems, one MS stack, one WidComm stack, both on .NET 3.5. A BlackBerry Bold is the device which is coming and going. I am using NetworkScanner.exe provided with the SDK.
On WidComm XP: NetworkScanner can see the phone coming and going whether it is paired/bonded or not.
On MS stack XP: NetworkScanner can see the phone coming and going if the PC and the phone are NOT paired/bonded. However, when they are bonded, it always discovers the phone even when it is not turned on. Since I want to reliably know that it is not nearby or turned on, this is a problem.
Q1: Is the above the expected operation?
Q2: What is the recommended approach for ensuring the phone is not close and discoverable?
I could do this but have not yet tried it: See if it is bonded and on MS Stack, then unbond first and then scan again. Seems kind of ugly and hoping something better would work. Would scanning for services reliably tell me this?