I am having the a similar issue. Setting the device mode as “Master”, sending +INQ=1, setting my PC or phone to ‘discover’ mode, get an address command (+RTINQ=aa,bb,cc,dd,ee,ff;name), use the address received to run +CONN=aa,bb,cc,dd,ee,ff, the PC or phone prompts for PIN and after entry:
[code]CONNECT:FAIL
+BTSTATE:1[/code]
The connection seems to fail (according to the Bee’s output), but the PC and phone both recognize the Bee’s attempt and allow connection to the address. My phone displays ‘Paired’ and my PC allows me to access the device and asks me if I’d like to set up a Serial connection on a COM port. Opening the COM port with PuTTY leads to the Bee’s state changing to
[code]+BTSTATE:3
CONNECT:OK
+BTSTATE:4[/code]
Using “PuTTY” I can send characters and they are received by the Bee.
Alternatively, using my Android phone, if I start the “BlueTerm” app the device is recognized, but not connected. I can connect without PIN as though it is a previously connected device and send characters there also.
I tried “Slave” mode too, but despite being in “+INQ=1” mode with both of the LEDs flashing the device isn’t discovered by either PC or phone.
I feel like I’m missing something here.
Must it be the “Slave” device that initiates connection to a known address?
