-
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
Cannot install/reauthenticate Alexa Integration - DO NOT USE 4.13.8! Solution: Revert to 4.13.7 #2675
Comments
Exact Same Issue here after HA upgrade to 2024.11.1 |
Same error here, after upgrading alexa integration. Logger: homeassistant.setup Error during setup of component alexa_media |
Mesmo problema por aqui. Integração Amazon alexa 4.13.8 não carrega após atualização do HA para a nova versão 2024.11.1 . |
Exactly the same problem here: File "/config/custom_components/alexa_media/init.py", line 159, in async_setup |
Same error here : Logger: homeassistant.setup Error during setup of component alexa_media |
Do not install 4.13.8! |
Does anyone know how I go about downgrading this integration? It's not something I've ever done before! Thanks |
After download, restart HA to effect change. |
That was easy! Thanks, that's fixed it for now :) |
Same fix as above, moved back to 4.13.7 Ironically the 4.13.8 update says it fixes the "Missing Public URL" issue! Clearly it did not! |
No, it made things worse. It is being reverted to 4.13.7 while I examine the whole mess surrounding public_url which actually dates back to when it became a configurable option (Aug/Sept?). Legacy YAML was never considered then as it was planned to be deprecated. 4.13.8 tried to fix things for YAML for its last few days but UI config became messed up. The plan now is announce it will be deprecated as of 4.14.0 and with no fixes for it between now and then. |
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
After upgrading HA fram 2024.10.3 to 2024.11.1 I got a log error message saying that the Alexa Integration could not be loaded (see below). So I tried to re-install the integration which eventually required also deleting and re-creating the 2FA with a new key.
Now, when completing the installation, I get a success message which tells me to ignore the "Aborted message" from HA. But there is no "Aborted message" anywhere!
When I click "close" on the success message, there's no integration added, and no new messages at all in the log.
When I restart HA, I get the below error message in the log all over again.
To Reproduce
Expected behavior
Screenshots
System details
const.py
or HA startup log): 4.13.8pip show alexapy
in homeasssistant container or HA startup log):Debug Logs (alexa_media & alexapy)
Please provide logs.
Additional context
Logger: homeassistant.setup
Source: setup.py:416
First occurred: 8:20:11 PM (1 occurrences)
Last logged: 8:20:11 PM
Error during setup of component alexa_media
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 416, in _async_setup_component
result = await task
^^^^^^^^^^
File "/config/custom_components/alexa_media/init.py", line 159, in async_setup
CONF_PUBLIC_URL: account[CONF_PUBLIC_URL],
~~~~~~~^^^^^^^^^^^^^^^^^
KeyError: 'public_url'
The text was updated successfully, but these errors were encountered: