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

Listen for data changes in already detected beacons #18

Open
hughbris opened this issue Apr 11, 2017 · 1 comment
Open

Listen for data changes in already detected beacons #18

hughbris opened this issue Apr 11, 2017 · 1 comment

Comments

@hughbris
Copy link

The current API (evothings.eddystone.startScan) listens for new beacons and exposes their data.

My use case (which I think this is common if not normal) is to listen for changes in the data broadcast by beacons once I have found them. Specifically the 'url' field in my case.

Without continually running a loop scanning, checking values, then stopping, I can't see a way to do this using the plugin. I am pretty sure the loop approach is going to miss some changes to values, and I'd expect it to crash eventually.

The sort of interface that I would like to see is in the eddystone-beacon-scanner node module. There you have events for 'found', 'updated', and 'lost', as well as a flag on the scan method to report duplicates. The 'updated' event would nicely address the use case I'm describing above. Unfortunately, I don't have enough JS packaging-foo to port this to a Cordova plugin (happy to be advised on that!).

So I guess this is a feature request. Would you consider extending the interface to this plugin to listen for changes to the data advertised by the beacon once it has been found? That would make it much more useful.

@hughbris
Copy link
Author

Oh, I've raised this in gitter, but been told you are all busy restructuring the company, so I expect it will get buried by the time you are all back on board. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant