Upgraded to 4.13.8: Missing public_url - DO NOT USE 4.13.8! Solution: Revert to 4.13.7 #2672
Comments
|
I have the same exact problem after upgrade the Addon. |
|
I deleted the Integration Entity and re-installed actually for a different reason. I noticed the public and internal address fields are reversed in order 4.13.8 from where they are on the setup configuration page in 4.13.7. The browser then complained the local address was insecure. I backed out and tried entering them in the old order ignoring the labels. It installed ok but after the reboot the Configure page has the local address in the field labeled public. Back to 4.13.7. |
|
I have the same exact problem after upgrade the Addon. |
|
same issue here after update Logger: homeassistant.setup Error during setup of component alexa_media |
|
I'm working on fixing it... |
Did you install via legacy yaml or via add integration config entry? |
via the add integration config entity |
|
Me too I'm going to roll back to the previous version of the addon until this is resolved. |
danielbrunt57
changed the title
|
I can't seem to get this rolled back. How are you doing it??? |
|
I just deleted the alexa folder inside custom_component folder. Restart ha. Nothing else. |
|
I figured it out. Got the previous version downloaded and all is good again. :-) |
|
I reinstalled the full backup form a week ago. Then, just in case I made a copy of the alexa_media folder from custom_components in case this happens again.In the future I plan making a copy like that before I upgrade alexa_media in the future. Then if the upgrade fails I can just copy back the folder I saved.
On Tuesday, November 12, 2024 at 05:08:11 PM CST, Michael Yeager ***@***.***> wrote:
I can't seem to get this rolled back. How are you doing it???
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Hi, I tried to delete the config and add it again by GUI. Then i opened HACS, searched the Integration "Alexa Media Player" and clicked on the three dot's. At least i restarted HomeAssistant and the Integration was up and running. So, downgrade and update again fixed the problem for me. |
|
reversed to anterior version did fix the issue |
|
I Downgraded to the previous version and it's now working. Have not tried to go up again. |
|
Same here: Error during setup of component alexa_media |
and same reply |
danielbrunt57
changed the title
danielbrunt57
added
bug
|
Any suggestions how to revert AND log in? After downgrading and logging into Amazon the integration sill isn't set up. I've tried downgrading (via HACS > three dots > "Redownload") to 4.13.7 and 4.13.6 and then restart HA. I then Add Integration and enter Email and Password and get sent to Amazon OAUTH login page, where I log in and enter the OTP sent to my phone. Sometimes, while at Amazon I see in the HA logs I see what others have posted about: But, not every time I try. After entering my OTP Amazon then redirects back to HA and I get: 
And after closing there's still no Alexa Media Player integration in HA. And there's no Aborted message in the logs, either. What's the trick? |
|
I've had experience of this problem across 2 installations.
After many trials, I think that this one works
remove the integration from the integrations page
remove the HACS download of the Alexa
(verify that the alexa media directory has been removed from "custom
components")
full restart of HA
start again and be sure to select version 4.13.7 when downloading the
repository into HACS
full restart of HA
install the integration
it should work.
PS - this whole thing has been frustrating as the behaviour is a bit
unpredictable.
good luck
…On Mon, 25 Nov 2024 at 08:33, billmoseley ***@***.***> wrote:
Any suggestions how to revert AND log in? After downgrading and logging
into Amazon the integration sill isn't set up.
I've tried downgrading (via HACS > three dots > "Redownload") to 4.13.7
and 4.13.6 and then restart HA. I then Add Integration and enter Email and
Password and get sent to Amazon OAUTH login page, where I log in and enter
the OTP sent to my phone. While at Amazon in the HA logs I see what others
have posted about:
2024-11-24 13:10:13.889 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0x7f3ffee050>,) inside the event loop by custom integration 'alexa_media' at custom_components/alexa_media/config_flow.py, line 374: self.proxy = AlexaProxy( (offender: /usr/local/lib/python3.12/site-packages/httpx/_config.py, line 149: context.load_verify_locations(cafile=cafile)), please create a bug report at https://github.com/alandtse/alexa_media_player/issues
But, not every time I try.
And then I enter my OTA and Amazon redirects back to HA and I get:
image.png (view on web)
<https://github.com/user-attachments/assets/1ae8122b-07d2-4238-a8e9-dfa9c2964848>
And after closing there's still no Alexa Media Player integration in HA.
And there's no Aborted message in the logs, either.
What's the trick?
—
Reply to this email directly, view it on GitHub
<#2672 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQEIO6RWV2NIWEOXJSTIJBT2CJA37AVCNFSM6AAAAABRTFDOFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJWGI2DMMZQHE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
*Michael Brooks*
|
I completely understand how very frustrated a lot of users are but as one of the contributors trying to fix everything, I think we have to be the most frustrated! |
I've also experienced that several times and I think I might have gotten past it either by simply trying to add the integration at that point. Either that or I restarted HA and then it showed up, or I added it and then it showed up. I'm not sure now as many things have been happening in my Dev environment day in and day out... |
|
Apologies, I can now see that my comment regarding frustration could be
interpreted as criticism of developers. This was absolutely not my intent
and I have complete and sincere respect for the people doing the developing
and trying to fix things. I just wish I had the skills to be able to
participate. keep up the good work .... please.
Michael
…On Mon, 25 Nov 2024, 9:42 am Daniel, ***@***.***> wrote:
PS - this whole thing has been frustrating as the behaviour is a bit
unpredictable.
I completely understand how very frustrated a lot of users are but as one
of the contributors trying to fix everything, I think we have to be the
most frustrated!
—
Reply to this email directly, view it on GitHub
<#2672 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQEIO6RGF5QLZP6OCTKF4PL2CJI5RAVCNFSM6AAAAABRTFDOFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJWGI4TCNBRGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Ha! Well, have to try again tomorrow. 
(I'm using my wife's Amazon account. Do I tell her now or just wait until she asks why she can't log in?) |
Thank you for the apology but I did not view your original comment as criticism of contributors but as just a statement of your frustration in general. I just want to clarify that and I thank you for your clarification and your appreciation of our efforts! |
You'll probably earn brownie points by telling her now. If you don't and she doesn't try to log in then no harm, no foul. But in my experience, what could ensue if she discovers she can't log in AND she finds out that you knew she wouldn't be able to AND didn't tell her, well, it could get ugly! |
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
Updating from 4.13.7 to 4.13.8 causes
Missing public_urlerror message. My installation has never had any issue with missing public url errors in the past. Looking in the configuration, I noticed the public url line is empty. Tried to add it back https:\exernal_url.com did nothing. It will not accept the submit.Reverting back to 4.13.7 and all is ok. Did not have to do any reconfiguration or reinstall.
To Reproduce
Upgrade to 4.13.8
Expected behavior
No error message. Upgrade with no issue
System details
const.pyor HA startup log): 4.13.7pip show alexapyin homeasssistant container or HA startup log):Debug Logs (alexa_media & alexapy)
Please provide logs.
Additional context
The text was updated successfully, but these errors were encountered: