Connection doesn't happen about bluepy HOT 5 CLOSED

Hi,

It may sometimes take a while (up to a minute) to make a connection, depending on the device - I assume you've tried just waiting?

I'm writing a wiki page on Bluetooth LE on the Pi - http://www.elinux.org/RPi_Bluetooth_LE - which has got instructions on how to build the BlueZ stack and test the hardware using command-line tools. I've found a number of devices which don't appear to connect properly using these tools, but haven't sorted out why yet; the TI SensorTag seems reliable though.

Thanks,
Ian

On 11 Apr 2014, at 14:20, Matija Urh [email protected] wrote:

Hi,

I'm trying to run your lib on RPi. I removed everything and just put
conn = Peripheral("72:64:9D:DB:0A:11")

and I get

Running /home/pi/BT/LE/sandbox/bluepy-helper
Sent: conn 72:64:9D:DB:0A:11

Got: '# bluepy-helper.c built at 12:26:47 on Apr 11 2014\n'
Got: "rsp=$stat state=$tryconn dst='72:64:9D:DB:0A:11 mtu=h0 sec='low\n"
Any idea why?
Is there any example code other than included btle.py?

—
Reply to this email directly or view it on GitHub.

from bluepy.

Just as a side answer for the records; it probably does not apply here since it's a very specific line:
this happened to me because I wrote the wrong address for the Peripheral. This make the helper try to connect until giving up (I suppose it was on purpose).

from bluepy.

@ajitam - is this still a problem? I'd like to close this issue if we can't establish that there's a problem with the bluepy code itself.

Thanks,
Ian

from bluepy.

Hi,
I think (I'm not certain) that I switch to another library, but it was a long time ago, so yeah you can close the issue.

from bluepy.

OK, thanks, closing it now.

from bluepy.