Open emufan opened 1 week ago
The lastest core version that works OK with polling enabled and devices connected to echo also enabled is 2024.7.4. At least for those that we are running AMP under European Amazon Servers. It looks something changed in the way our servers manage cookies … this and the latest python update for HA 2024.8, .9 and .10 … was the perfect storm. We need to wait until the next python update in HA.
The question is when it will be upgraded. Next month? Next year? Never?
The lastest core version that works OK with polling enabled and devices connected to echo also enabled is 2024.7.4. At least for those that we are running AMP under European Amazon Servers. It looks something changed in the way our servers manage cookies … this and the latest python update for HA 2024.8, .9 and .10 … was the perfect storm. We need to wait until the next python update in HA.
I have everything running with Amazon.de, Home Assistant 2024.10.2 and AMP 14.3.4.
@z-master42 , do you really have “polling” enabled? Are you using “alexa_media.update_last_called” service?
What does this have to do with the problem of the author of the issue?
As you said everything is running under 2024.10.2 and AMP 14.3.4 … it looks like the new core released a couple of days ago has solved these issues related to alexalogin authentication,
An error occurred accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',)
Issue: #2483
I have everything running with Amazon.de, Home Assistant 2024.10.2 and AMP 14.3.4.
@z-master42 Really? How did you get this working? Always standard updates? New installation? Always working or working since x and y now again?
I can try whatever I want, after 2024.6 nothing is working anymore (skipped try of .7, but .8, .9 and .10 is always showing error and not running installation after HA update and completely no possibility to re-install with the given errors above.
So I'm really wondering and looking forward how it is working in .de and I'm surprised that so many other users are running is <> .de, if this is really a cookie handling problem in HA .8 and bigger as I assume that the other regions are using cookies too and the login should not be that different to .de
It's been running for months, no idea how long. The only problem I had in the meantime was an updated blocklist in my Pi-hole that had the Amazon API on it. Even the .2 that caused so many people's memory to fill up and the CPU to max out ran without any problems for me.
The lastest core version that works OK with polling enabled and devices connected to echo also enabled is 2024.7.4. At least for those that we are running AMP under European Amazon Servers. It looks something changed in the way our servers manage cookies … this and the latest python update for HA 2024.8, .9 and .10 … was the perfect storm. We need to wait until the next python update in HA.
I have everything running with Amazon.de, Home Assistant 2024.10.2 and AMP 14.3.4.
How did you managed that? Once I did the update AMP stopped working and I was never able to login anymore.
@Sectorchan Which update are you talking about? Which versions? AMP stopped working after ‘the’ update? What does the log say? Are there any error messages?
Describe the bug
I'm running AMP without problems in HA 2024.6 and AMP 4.12.7.
But with HA versions > HA 2024.6 I can't get the integration to run. Tried is in every version .8, .9 and today again for hours in .10
So I'm wondering if I'm really the only one, who coudn't get it running if I read so many infos, that it is still running elsewhere.
Even an update to AMP 4.13.2 is working and AMP is running afterwards with HA 2024.06 but not with newer version, e.g. todays 2024.10.1.
To Reproduce
Update HA to 2024.8 or 2024.9 or 2024.10 with running AMP or try to install AMP in 2024.8 or 2024.9 or 2024.10.
Domain is de (if this is the problem).
What is not working / where it ends.
Adding of integration was not successfull
After restart of a before setup and running AMP ist just ends with "integration not loaded". And deleting, re-adding, ... nothing is working.
Of course, I read today most probably all open issues here in this section (again), but all the work arounds and tips there are not mine:
Tried
Expected behavior
Running AMP with HA e.g. 2024.10
System details
const.py
or HA startup log): 4.13.2pip show alexapy
in homeasssistant container or HA startup log):Debug Logs (alexa_media & alexapy)
Surprisingly it shows that it is finding devices and registers them, but then cancels everything at some point in time.
Is this the relevant problem
out of complete flow?