Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] iBeacon/Eddystone Support #46

Closed
regeland opened this issue Apr 1, 2018 · 2 comments
Closed

[Question] iBeacon/Eddystone Support #46

regeland opened this issue Apr 1, 2018 · 2 comments
Labels
documentation Something to update in documentation question Further information is requested

Comments

@regeland
Copy link

regeland commented Apr 1, 2018

Has anyone tried to fiddle with capturing BT Low Energy packets with this code? Where would I look to start hacking this in? I have a Raspberry Pi Zero W and it sniffs the packets great with hcitool, so seems like it could be a nice addition for near real-time proximity detection. No latency/overhead associated with the regular BT or AP polling.

@schollz
Copy link
Owner

schollz commented Apr 1, 2018

@regeland This code is compatible with sniffing Bluetooth. There is a CLI utility (https://github.com/schollz/find3-cli-scanner) that allows you to do that and send the results to FIND3.

@schollz schollz added the question Further information is requested label Apr 1, 2018
@Thomas499
Copy link

The raspberry pi in this case would be stationary, so you are basically wanting ble to have same functionality as wifi does in promiscuous mode or monitor mode (depending on which documentation on the find3 you are looking at). Is this correct? - Great idea by the way. I myself was wondering how to implement that.

The biggest question is if the A.I. code is smart enough to identify which BLE signals are from devices that move and to disregard signals from those devices. Most WiFi routers do not move often though smart phones acting as a wifi hub do. Many devices the broadcast BLE signals move often, and many do not move. Can the A.I. figure out which ones are likely to stay in the same place and disregard the others?

@schollz schollz added the documentation Something to update in documentation label Apr 20, 2018
@schollz schollz closed this as completed Apr 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Something to update in documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants