-
Notifications
You must be signed in to change notification settings - Fork 304
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
Device Name Inaccurate #95
Comments
I was about to open a similar issue: |
I got the same thing except when I use the discover_service.py it did find the right name in a really weird area, therefore i am not sure where is the issue. Maybe it's when I set up the name for my Bluetooth. I use the wrong variable or maybe bleak just does not have the ability to read the correct name? |
During the What your iPhone does in its API has no bearing on how Windows does it in its API, so there is no guarantee that bleak using the Windows UWP Bluetooth API will return the same information. See #73 for more information as well. |
macOS support added (thanks to @kevincar) Merged #80: macOS development Merged #90 which fixed #89: Leaking callbacks in BlueZ Merged #92 which fixed #91, Prevent leaking of DBus connections on discovery Merged #96: Regex patterns Merged #86 which fixed #83 and #82 Recovered old .NET discovery method to try for #95
@DavidYauUGA @arasan90 In the version 0.5.0 which has just been release to PyPI, there is a "new" method to use for discovery:
Use it the same as the It is the old method I had in versions <0.3.0. It uses older Windows namespaces and does not reveal Service UUIDs and manufacturer data, but I remember it as better at extracting names of devices. Give it a try. |
Let me try that one first. Thanks anyway !!! |
Description
I was trying to use to discover.py, but they all print out company's name of the bluetooth not the actual setup name for the device. For example, instead of showing "Micheal's Beats3", it will show "Microsoft".
What I Did
The text was updated successfully, but these errors were encountered: