-
Notifications
You must be signed in to change notification settings - Fork 303
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
Bluetooth device missing in source list #316
Comments
@danielmihalache1983 please test the latest fix |
It shouldn't be private. You can't access it? |
Source list still does not contains bluetooth device.
|
Are you able to select the device in the mobile app? We support a2dp-source devices. It's possible there may be other profiles we're missing so I want to confirm you can actually select it as a music source with the app. |
Also, to the extent the source lists the paired device as a source, that's actually a bug since we're not verifying it's a music source. |
Within the app, selecting one of the bluetooth sources will trigger the pairing process. |
So as I see it, you should list in Source List every bluetooth device that alexa was previously paired, but necessarily connected to it. |
Also, "Source" and "Source list" is not really the best name for something that is actually an output device. But I thought that this is just the best fit from media_player property list for this purpose |
Actually it's a source of the music that is playing for the media_player. That is an HA convention. We're not saying what is paired to the device. To be honest, the "local speaker" name is actually wrong, it should say something like "Amazon" so it's clear the source of any audio is from Amazon. If you're looking for a bluetooth pairing option, that is something we could add as a feature, but the goal would be to match how HA does it for other devices to the extent possible. The Source list isn't the right way. |
Ok, I get your point and if you put it like that than the bluetooth device should never show on that source property whatsoever. As you say it should be a new feature. btw, if you fix this bug without adding the new feature, my usecase will break :) |
Haha, ok, let me spawn a new ticket for the feature and I promise I won't push this fix until the feature is up. ;) Can you let me know if you find any other HA components that allow bluetooth pairing? I want to try to use the same mechanism. Please respond in the new thread. |
Just to clarify, all the fixes I'm proposing are for the UI and attributes; I am not putting any checks on the service so that will continue to work as planned. |
Yes, I kinda figured out from the comments on #322 |
fix(bluetooth): resolve bluetooth update issues
Yep. Issue is fixed. Thanks for the fix.
There is one more thing about the bluetooth...it does not show in the source list.
yet, when I catch the state change in node-red and verify the json object, I can see the bluetooth as source...yet not in the source list.
can we fix this to?
Originally posted by @danielmihalache1983 in https://github.com/keatontaylor/alexa_media_player/issues/309#issuecomment-526648169
The text was updated successfully, but these errors were encountered: