raspberry pi Beacon not picked up.

sandeepmistry / node-bleacon

A Node.js library for creating, discovering, and configuring iBeacons

MIT License

498 stars 88 forks source link

raspberry pi Beacon not picked up. #14

Closed ronsmits closed 10 years ago

ronsmits commented 10 years ago

I am trying to use the bleacon libary to scan for beacons. I have three estimotes who are picked up without any problems.

The Raspberry pi uses a bluetooth dongle and has been setup as follows:

sudo hciconfig hci0 up
sudo hciconfig hci0 leadv

The example android application from google (BLE device scan) picks it up without problems and gives it the name CSR8510 A10. This is actually the name of the chip :)

Running sudo hcitool lescan does pick it up:

00:1A:7D:DA:71:12 CSR8510 A10
00:1A:7D:DA:71:12 (unknown)
C7:23:ED:6A:87:F3 (unknown)
C7:23:ED:6A:87:F3 estimote

sandeepmistry commented 10 years ago

@ronsmits How are you setting the iBeacon UUID/major/minor on the RPi?

If you're not, your options are:

Shell script: https://github.com/carsonmcdonald/bluez-ibeacon
Use bleaon: https://github.com/sandeepmistry/node-bleacon/blob/master/test.js#L3

ronsmits commented 10 years ago

Using both examples node-bleacon picks them up without any problems. The rssi of both systems is however very erratic.

sandeepmistry commented 10 years ago

A Broadcom based adapter and/or using a USB extension cable might be less erratic, see: https://github.com/sandeepmistry/noble/wiki/Compatible-devices#linux

ronsmits commented 10 years ago

Thanks for the reply. I have added the bluetooth adapter I am using to the wiki page. It might help more people. The bluetooth dongle identifies itself in linux as

Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

This is on a raspberry pi. No cables or extensions are used.