-
Notifications
You must be signed in to change notification settings - Fork 261
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
Alexa authentication bug, url is wrong, Cannot load Integration #1927
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Revert using home assistant restore or load older version of Alexa Media Player? live tried older versions of the Media Player back to 4.6.0 and all do the same thing, so this looks like a home assistant core issue... |
@jazzmonger older home assistant file..like 4.6 and older backups integrated it again |
This comment was marked as off-topic.
This comment was marked as off-topic.
facing the same error. downgrading HA core to 2023.4.1 seems to resolve the error as of now |
This comment was marked as off-topic.
This comment was marked as off-topic.
This is not a discussion forum. Please do not pollute it with off topic conversations. This makes it difficult for those who may want to read it to get to the information they may need. It also spams peoples emails with unnecessary info. The port number is pulled from HA. We don't populate it. Please check your Settings -> Network: We have heard reports disabling for setup IPv6 can workaround networking errors with the auth proxy. I can't do anything without enabling debug logs. You can obfuscate your HA url, but please leave the port intact. There's debug lines when it sets up the callback url. |
I changed my network to disable IPV6
|
And the URL in the windows to "Access Home Assistant" matched my URL that I have for online access. |
you CANNOT enable deg logs if the integration isn't loaded. Cloud access works just fine. And no matter what I change, there is always a This behavior was introduced in the latest core update. If we downgrade, it works. again, tell me specifically what else you need and I'm happy to provide gory details. I'm not a newbie. If it wasn't clear, I'm using a Debian Supervised install- a literally plain vanilla supported install on a purpose built, dedicated NUC. |
The above method has worked for me as well. |
The local IP and port worked for me. As an additional point of information, I was getting the error not only while using the NabuCasa url but also while using my Cloudflare redirected url. Neither of those use a port to get to my HA from outside my network. |
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
Unlike others, I'll provide as much info as I possibly can. If you need something else, pls be very specific on how to get it for you.
The problem lies in the automated url generation for authorization
...ui.nabu.casa:0/auth/alexamedia...
The
:0
shouldn't be there. If you remove it, you get a lot further, but it still won't authenticateTo Reproduce
just try and add the Alexa Media Player
Expected behavior
Add the integration
Authorize with a VALID url.
Screenshots
System details
Home-assistant (version): 2023.5.0
alexa_media (version from
const.py
or HA startup): From HACS 4.6.2alexapy (version from
pip show alexapy
or HA startup): There is no way to tell. Integration isn't available on startup.Amazon 2FA is enabled (y/n)yes
Logs no way to provide logs if you can't even load the integration.
Please provide logs.
Additional context
The text was updated successfully, but these errors were encountered: