-
Notifications
You must be signed in to change notification settings - Fork 9
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
Allow duplicate entries to be discovered #6
Comments
I've never tried to do something like this myself. What's the current behaviour, and how is this stopping you from achieving your goal? |
Right now when starting discovery, a node that is broadcasting multiple advertisement frames with different data will only be discovered once. For using beacons as a means to transfer data, the user would need to see every advertisement frame. Furthermore, right now discovery always seems to be active, while processing beacon data would only require passive scans. The best interface in this case would probably be an event for every incoming raw (or parsed, but complete) advertisement frame. This way the user could process the advertisement data as appropriate. I'm not sure if I overlooked it, but right now there's no such interface, right? |
I believe you have to add the device using AddDevice with BackgroundScan action. Then you'll get a passive scan with multiple events. Afaict, the kernel mgmt interface does not allow for explicitly starting a passive scan in any other way. Please note that removing the device from the list is currently broken (#14). |
I'm looking for a way to continually discover beacons that use simple advertising packets to emit telemetry data (among others). Is there a way to run discovery in a way that would allow me to capture and process all these packets, even if multiple packets are sent from the same device?
The text was updated successfully, but these errors were encountered: