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

Wrong friendly name discovered when using WIDCOMM BT stack #41

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment
Open

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

1. Perform an inquiry on a product with friendly name "FriendlyNameAlpha" and 
with a fixed address (using examples/simple/inquiry.py
2. Change the friendly name of the product to "FriendlyNameBeta", but leave its 
address intact
3. Perform an inquiry on the product with the same fixed address (using 
examples/simple/inquiry.py)

What is the expected output? What do you see instead?
You should now see "FriendlyNameBeta" instead of "FriendlyNameAlpha"

What version of the product are you using? On what operating system?
We are using PyBluez 0.18 on Windows -> Widcomm stack.

Using the Windows software provided by the manufacturer(Broadcomm) this does 
not happen.


Original issue reported on code.google.com by [email protected] on 2 Feb 2011 at 4:00

@GoogleCodeExporter
Copy link
Author

Actually, the error seems to lie in the fact that we receive both 
"FriendlyNameAlpha" (first) as well as "FriendlyNameBeta"...
So for the same inquiry we receive some erroneous information first from cache, 
and then real information!

Original comment by [email protected] on 2 Feb 2011 at 4:47

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

No branches or pull requests

1 participant