-
Notifications
You must be signed in to change notification settings - Fork 14
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
issue in discovery #3
Comments
In my application it only makes sense to have one device with the specified UUIDs, so findObject in base.go returns an error. I don't have any need for this, but will consider a patch if you want to make it work. |
yes please consider a patch for this. Thank you. |
Sorry if I wasn't clear, but I don't have any plans to work on this. If you want to submit a patch, I'll consider it though. |
Unless you pass a non-zero timeout to Discover(), it will wait forever. You should also use GetDevice or GetDeviceByName before calling Discover, in case the device has already been found. |
i have 2-3 sensorTags when i am initiating the discovery process i am getting :-
2017/06/15 02:29:30 saurabhpi: starting discovery
2017/06/15 02:31:38 saurabhpi: discovered PSSENSBANKB
2017/06/15 02:31:38 saurabhpi: stopping discovery
2017/06/15 02:31:38 found 2 instances of interface org.bluez.Device1
exit status 1
i am using the sample code for discovery from cmd directory.
The text was updated successfully, but these errors were encountered: