-
Notifications
You must be signed in to change notification settings - Fork 289
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
Echo Buttons (and possibly other Alexa Gadgets) showing on Sources list #166
Comments
We are pulling information from this link. Can you use your appropriate region and provide us info for what Echo Buttons look like? Please mask any sensitive info like serial #s. |
Here are three devices from the pairedDeviceList collection for my Echo Dot: Paired phone:
Bluetooth speaker
Echo Button
It looks like Echo Buttons and other Alexa Gadgets can be identified by their devcie class being GADGET. The phone and speaker both have a class of OTHER. Edit: Also, it seems that Bluetooth speakers have a Bluetooth profile of A2DP-SINK while the phone has a profile of A2DP-SOURCE if it is necessary to distinguish between these. |
I think the solution is to actually check for A2DP-Source in Profiles. |
@gadgetchnnel can you please test #170? |
@alandtse I've tested that and it appears to work well, excluding the Echo Buttons and showing my phone which was paired with the Echo Dot. |
The Sources list appears to pick up all Bluetooth devices connected to the Alexa device, and not just speakers or devices (such as mobile phones) using the Echo as a Bluetooth speaker.
Since Alexa Gadgets (such as the Echo Buttons and the Echo Wall Clock) connect over Bluetooth, these are also being included in the list. For me that means that I have several Echo Buttons showing in the list.
Is it possible to filter this list so it only has speakers are included?
If the type isn't returned it may be possible to do it by name. I know Echo Buttons all have names starting with EchoBtn. I don't know about the Echo Wall Clock as this hasn't yet launched in the UK.
The text was updated successfully, but these errors were encountered: