I have had to restart today two of my three OH installations on my PI’s.
On exaclty thoose two installation under 4.3.5, I’m gett this errors, that the amazon account seens not to be working. The other is stell “online”
The logfile:
time,level,source,data
10:12:56.699,"INFO","openhab.event.ThingStatusInfoChangedEvent","Thing 'amazonechocontrol:echo:e2b7351909:954bd10e22' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)"
10:12:56.701,"INFO","openhab.event.ThingStatusInfoChangedEvent","Thing 'amazonechocontrol:account:e2b7351909' changed from OFFLINE (COMMUNICATION_ERROR): GET url 'https://alexa.amazon.de/api/phoenix' failed: null to UNINITIALIZED"
10:12:56.738,"INFO","openhab.event.ThingStatusInfoChangedEvent","Thing 'amazonechocontrol:echo:e2b7351909:954bd10e22' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)"
10:13:09.295,"INFO","openhab.event.ThingStatusInfoChangedEvent","Thing 'amazonechocontrol:account:e2b7351909' changed from OFFLINE (CONFIGURATION_PENDING): Wait for login to OFFLINE (COMMUNICATION_ERROR): GET url 'https://alexa.amazon.de/api/phoenix' failed: null"
Anyone else having issue here?
The Echo which is connected still works.
So it only the Account which is not “online” as an Item.
After that I deleted the “bridge THING” and tryed to created a new, with the effect, that the
Alex ECHO thing is now also has become a red error sign in the things overview
When try to create a new ID and login in at Amazon with my accountname and password,
I get a call, with a PIN, this I enter inb the OTP field.
After that I get the message with the error.
I’m having the same issue. I tried resetting the Amazon account, and now I get the errors below when logging into the binding through the web interface. I’m in the United States if that makes any difference.
HTTP ERROR 500 org.openhab.binding.amazonechocontrol.internal.HttpException: GET url 'https://alexa.amazon.com/api/phoenix' failed: null
URI: /amazonechocontrol/AmazonAccount/ap/signin
STATUS: 500
MESSAGE: org.openhab.binding.amazonechocontrol.internal.HttpException: GET url 'https://alexa.amazon.com/api/phoenix' failed: null
SERVLET: /amazonechocontrol/AmazonAccount
CAUSED BY: org.openhab.binding.amazonechocontrol.internal.HttpException: GET url 'https://alexa.amazon.com/api/phoenix' failed: null
Powered by Jetty:// 9.4.54.v20240208
Ah, good to hear, or bad, that more users now impacted.
As it looks like, that it happens over the weekend, an update was installed, without tested beforehand
only a suggestion from me
That works to bring the Amazon devices like Echo back online but I have several smarthome.devices and they remain offline, of course, if you deactivate that feature…
Anybody any other solutiin or reason why this is not working anymore?
Ok. It looks like the HomeAssistant “Binding” was changed from the developers, in that way, that it works again now.
Yes, some people on Git are reporting that they manually updated the aioamazondevices library to 3.2.8, and everything should be working again. According to the pull request, the change will be included in the 2025.7.2 core update. Let’s wait and see and hope it lasts longer this time and Amazon doesn’t change anything else in the API. Because apparently, no official API is used for Amazon devices either; otherwise, changes like the one with HTTPCode 299 would have to be officially announced by Amazon long in advance.
So how we are doing here in our Binding case, who could take a ownership here that the binding could be also changed, that it works again?
