-
Notifications
You must be signed in to change notification settings - Fork 302
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
Attempt to install Alexa media_player appeared to be successful, but no integration is found #2710
Comments
You sequence of events doesn't make sense to me.
There is no entry of 2FA when installing the HACS integration. Unless you mean you successfully created/added the Amazon 2SV Authenticator App, obtained the key and verified it.
There shouldn't have been a message to just ignore any error messages. The installation should just say Successful followed by the list of discovered devices where you can configure the area.
This is and always has been an absolutely benign WARNING and has absolutely zero effect of the execution of the code. |
A full and complete set of DEBUG logs for |
Can you please give me the step-by-step on how to generate/set-up such a log? |
Maybe this is the answer. I had the other issue where the devices weren't found, so I re-installed Alexa Media Player and had a similar experience to the above. I searched in HACS for Alexa Media Player, installed it, configured the 2FA, and it all looked like success. Now I go to Settings > Devices > and there's no Alexa Media Player there. I reinstalled twice and was scratching my head. Since I disabled it before re-installing, I had to un-disable it. In the top right corner of the Devices list, look for "1 Device Disabled" and enable it. |
You're right. That took me one step further. Now I can at least see the integration. But with no devices found! So, it's unable to find my Alexa Echo Dot. I chose "add entry" and fed all the correct data and got a final "success" message, but to no avail - still nothing found. |
Hello!! I had the same problem as you, I followed the last steps, the same thing happened to me as you, but I restarted HA and the integration now works for me. |
No, I've updated the Alexa Integration to 5.0.1 and restarted HA, but still it isn't able to find my Echo Dot., but the integration as such now runs without errors. |
The same here, but was my fault |
Either that or your devices are registered in a different domain. |
k, so how do I find out which domain my Echo Dot is registered in? |
No, that doesn't work for me. I bought my Echo Dots second hand, and I don't live in the US and we don't have access to Amazon Prime. I have the Amazon App installed on my Samsung SmartPhone and the integration to Home Assistant used to work well for several years. but no more. |
Are you getting
The result of a successful phoenix GET is the network details:
|
The page I posted is Amazon app, not Alexa app. |
IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
Describe the bug
I installed the Alexa Media Integration from HACS as explained in the Wiki. Everything seemed fine, including 2FA. Then I installed the Alexa media_player integration from HA Settings --> Devices & Services and again everything appeared fine. I even got a success notification in the end, along with a message to just ignore any error messages.
The only error message I got in the log was:
Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7fd0de6e77d0>,) inside the event loop by custom integration 'alexa_media' at custom_components/alexa_media/config_flow.py, line 374:
But there's no Alexa Media Player integration in the HA integration page!
And nothing seems to work.
To Reproduce
Expected behavior
Screenshots
System details
const.py
or HA startup log): v5.0.0pip show alexapy
in homeasssistant container or HA startup log): (not running HA OS)Debug Logs (alexa_media & alexapy)
Please provide logs.
Can't enable debug logging as long as the Integration isn't installed/found.
Additional context
The text was updated successfully, but these errors were encountered: