-
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
Broken Home Assistant Configuration in HAss Core 2024.8.0 #2433
Comments
I have the same issue, tried reauthenticating with amazon.co.uk, but authentication keeps failing. After latest update. |
Same here |
Same here, I tried 3 times but no success! |
same here |
This worked, change the manifest.json. |
Thank you SO much for this temporary workaround. |
thank you, work fine ! |
works for me too great info thanks <3 |
Sorry, please can you tell me where to add this: "requirements": ["alexapy>=1.28.2", "packaging>=20.3", "wrapt>=1.14.0"], |
oops, |
@Shaunpottie you need to SSH inside the machine that has HA installed and locate the data directory like /etc/homeassistant/custom_components/alexa_media/ and then modify that file using a Text Editor like nano |
modify this : |
Eish, let me see if I come right, thank you. |
Thank you everyone for the help, I came right. Working 100% now. |
It works. Thanks s lot |
Or simply use Studio Code Server from within HA 😉 Thank you @sca075, that worked - I use Alexa Media Player for so many announcements, playing music, etc, I was (temporarily) lost before you gave us a fix 👍 |
With amazon.de it is not working. 😞 |
I´m using amazon.de and its working for me whats your failure? |
The 500 error |
Edited in Studio Code Sever "requirements": ["alexapy>=1.28.2", "packaging>=20.3", "wrapt>=1.14.0"], Worked! Ta! |
@herden-system I use amazon.de too and work fine, 500 = "Internal Server Error" means that there is some issue on the configuration of your instance, . Probably just reconfigure it and if you did change the mainifest.json as above all should work as usual. Note that it looks it is now required an external (https) url of your home assistant in the config. |
It was the pulic URL! Thanks a lot! |
@sca075 Hugest of props—that worked perfectly! 🙌🏻 |
Yep - thanks a lot! |
Can someone explain what public url it is that needed changed? I don't have any settings specific to me in the alexa manifest file so is this somewhere else? |
Guys, that's the first time I've opened an Issue in Github, I didn't think I would get so much effort! At this time, do you think I should close the Issue? I mean, is resolved no? |
@F5ancesco I’d hold off from closing this issue until this fix is baked in to an official update from Alexa Media Player. |
You need to have Nabu Casa! |
No, you don't. I do not use Nabu Casa as my external URL is either The Instead of NC, I chose the manual setup method to integrate the Alexa Home Assistant Skill and my alexa file is:
That I just re & re'd my integration yet again about 13 hours ago after successfully setting up AMP v4.10.3 in HA 2024.8.1 to double check detailed log files. After reinstalling AMP v4.12.7, everything is working fine. |
After some testing to solve problems related to AMP integration I found that the “alexa” and “alexa_auth” files contained in homeassistant/.storage/ (which perhaps not everyone has in their configuration) are related to the configuration of Amazon aws to expose HA devices on Alexa. In fact, by removing the “alexa_auth” file (which contains a token) the “alexa” file cannot be changed to true. So I came to the conclusion that they actually have nothing to do with the AMP integration that still doesn't work for me if I upgrade to HA 2024.8.1. |
That's not completely accurate as those two files are only created when Nabu Casa Cloud is configured to expose HA entities in Alexa. They do not exist with the AWS/Alexa manual skill method of exposing HA entities in Alexa. The only place authentication is configured when manually created is here:
that's correct
I'm wondering if my method of eliminating the partitioned cookie error might somehow be contributing to my 100% success rate since when not using it, AMP fails to load at restart due to partitioned cookie error but a reload loads it. I'm thinking that the pickled cookie file is in some way different because of that initial cookie error. Could you perhaps try replacing the |
How do you perform the procedure you describe? Could you explain it to me? | Could you perhaps try replacing the /usr/local/lib/python3.12/http/cookies.py with the 3.13 version. |
I usually use Portainer to sh to my homeassistant container but you can also get to it from your terminal ssh via
|
The primary change in the file is the addition of the
|
Thanks for the really detailed explanation. The auth process works fine so for the most the @petrotti77 issue looks to be a specific scenario. Do you need some specific data to analyze it? |
@sca075 Correct. AMP is only scanning amazon for alexa media capable devices (like Echo) in Alexa.
I'm confused as to what your issue is now... |
Good morning guys. I have reread the posts you have published these days. I sleep back once again to HA 2024.7.4 after a lot of frustrations to repair automations and zigbee devices that don't work after the downgrade and upgrade procedure. @danielbrunt57 I still haven't figured out if the pickled cookie file procedure you describe you used it in your configuration or it's just a suggestion to try it out, because I'm really terrified to update even though I'm aware that I can't stay forever at HA 2024.7.4. @danielbrunt57 You were telling me that you need specific data to analyze it. What would you need to understand what happened in my setup? |
I'm just totally confused as to what your current issue is with 2024.8.1...
It's not a pickled cookie file procedure. It addresses the partitioned cookie error which requires always reloading AMP after a restart to get it going by replacing the cookies.py file with a newer version from a pending PR for Python 3.13 beta and is safe if you replace the file with the complete and correct 3.13 cookies.py file. I once did not but was able to successfully recover from my error! I have documented how to use amitfin's Patch custom component to automate the procedure, which others have successfully implemented. If you are interested, I can repost it here... |
I too don't want to update again from 2024.7.4 and am watching this thread
in the hope of some good news - sadly, it all seems negative at the moment.
I can't imagine how so many people must be frustrated and don't know what
it happening.
Let's hope it is all resolved.
…On Thu, 15 Aug 2024 at 09:32, petrotti77 ***@***.***> wrote:
Good morning guys. I have reread the posts you have published these days.
I sleep back once again to HA 2024.7.4 after a lot of frustrations to
repair automations and zigbee devices that don't work after the downgrade
and upgrade procedure.
@danielbrunt57 <https://github.com/danielbrunt57> I still haven't figured
out if the pickled cookie file procedure you describe you used it in your
configuration or it's just a suggestion to try it out, because I'm really
terrified to update even though I'm aware that I can't stay forever at HA
2024.7.4.
@danielbrunt57 <https://github.com/danielbrunt57> You were telling me
that you need specific data to analyze it. What would you need to
understand what happened in my setup?
—
Reply to this email directly, view it on GitHub
<#2433 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABFWRDXMEQPM43L3YZAWF5DZRRRQ5AVCNFSM6AAAAABMGRLXDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJQHA4DQNBXGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@LindsayReid I understand your frustration but am doing my best to figure this whole mess out. My installation is working fine and am doing my utmost to assist others in achieving the same results that I have here. |
An info, who is left at HA 2024.7.4 which version of AMP are you using? @danielbrunt57 So to understand you are using HA 2024.8.1 with AMP 4.12.7? |
Yes. |
I have prepared a script that centralizes the access to alexa_media. sequence:
I found my entry_id inside the file: /config/.storage/core.config_entries bye |
But you performed the procedure to replace python3.12/http/cookies.py with version 3.13? |
No Daniel, this is the only procedure that run without errors. |
@messere63 But with what automation do you activate the script. Could you explain it? |
I do this with any automation. For example when the power absorbed in my house exceeds the maximum or when an alarm is triggered. |
@messere63 I didn't understand? |
It works fine !! Thanks a lot ! |
Guys did update AMP to the last version.. it works perfectly as it was with the v4.12.7.. I think it is clear that for those that still have problems authenticating the issue is clearly something different. The Team here did an amazing job. Thanks a lot guys. 🥇 |
Could you please answer the following questions?
Thank you. |
I hope this can help you. |
Good evening, for now I stayed on HA 2024.7.4 and I have only removed the 2FA validation in my Amazon account and updated AMP from 4.12.5 to 4.12.11 without making any changes to the cookies.py file. Everything seems to work but I'm a little afraid to update to HA 2024.8.3. |
What was this before you made the change? Trying to determine if my from/to would be the same now in October as it was back in August. |
There is no need to edit alexapy in manifest.json. The current version of alexapy is 1.29.2 and that's what the last several releases of AMP have in manifest.json. |
Describe the bug
Devices unresponsive under any circumstance, HA asking to reconfigure the extension but nothing happens.
To Reproduce
Expected behavior
The integration to properly work as it did before updating HAss Core to 2024.8.0.
To show all my echo devices as well as Alexa linked ones.
Screenshots
The UI Error is shown below:
![Screenshot 2024-08-08 alle 15 35 14](https://private-user-images.githubusercontent.com/37825831/356243914-02a323b2-02e9-4a46-a5e6-9eeea3edee68.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNjQzNDAsIm5iZiI6MTczOTI2NDA0MCwicGF0aCI6Ii8zNzgyNTgzMS8zNTYyNDM5MTQtMDJhMzIzYjItMDJlOS00YTQ2LWE1ZTYtOWVlZWEzZWRlZTY4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDA4NTQwMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWJlMWJkZmMyMzg5YTgwMWMwMzVlYzI5MDE1OGYxYzdkMjI1ZjFjN2U5NmJkNmNlZWYwN2MyYzljZGM0MGYyNjEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.NCqBaSNN8F_YaDTkuxA2Np79f88LHCeYFCeWvHaaVKI)
System details
const.py
or HA startup): 4.12.6pip show alexapy
or HA startup):Logs
Don't know where to find them! Tried to take a look to the log files but nothing seems to be relevant...
Additional context
The text was updated successfully, but these errors were encountered: