I am on OH5.0.2/docker and have had a stable Amazon Echo Control Bridge up an running. After an OH restart, I need to configure the things again. Login via the given link seems to work but at the end the message “Login to ‘amazon.com’ failed: Could not register as app.” is given.
I tried to reset the account via “amazonechocontrol resetAccount [accountname]” and disabled all possible add blockers.
There is also a bug listed (from another user):
Any ideas for workarounds or fixes?
Thanks
Same here since this morning, I guess its something with the Amazon servers again.
I will wait till tomorrow before taking further actions …
Same problem for me after an openHAB restart.
@lsiepel Hey, Again the similar issues cropping up. For me also, the Amazon account thing is offline. I tried logging in to the Amazonechocontrol but it keeps on giving me the error. Sometimes the url shown is Amazon.com instead of Amazon.in
Please help.
I can also confirm, that the service is not more working. I can’t login in to the service
same here
Obviously something changed to their api. It might be temporary (as before), maybe not.
If there is proper documentation I can look at it, but without details it won’t be fixed.
Please let us know how can we help in getting the documentation.
Here the debug-log with the 404
2025-11-07 07:02:50.430 [DEBUG] [trol.internal.handler.AccountHandler] - check login amazonechocontrol:account:AmazonEchoBridge
2025-11-07 07:02:50.431 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://eu-api-alexa.amazon.com/api/bootstrap (available: 2)
2025-11-07 07:02:50.538 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://eu-api-alexa.amazon.com/api/bootstrap: 404
2025-11-07 07:02:50.539 [DEBUG] [ntrol.internal.connection.Connection] - Bootstrapping failed
org.openhab.binding.amazonechocontrol.internal.ConnectionException: https://eu-api-alexa.amazon.com/api/bootstrap failed with code 404: Not Found
at org.openhab.binding.amazonechocontrol.internal.util.HttpRequestBuilder$HttpResponseListener.onComplete(HttpRequestBuilder.java:386) ~[?:?]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:218) ~[?:?]
and some trace logging via PM directly to @lsiepel as I don’t want to strip out the sensitive data.
Thx in advance 
Here comes my logfile, when I want to bring the Binding online:
time,level,source,data
09:39:58.003,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery(587)] : ServiceFactory.getService()"
09:39:58.003,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery(587)] : This thread collected dependencies"
09:39:58.003,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery(587)] : getService (ServiceFactory) dependencies collected."
09:39:58.004,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery(587)] : Querying state satisfied"
09:39:58.004,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery(587)] : For dependency osgi.ds.satisfying.condition, optional: false
09:39:58.004,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery(587)] : invoking activate: activate: parameters [org.apache.felix.scr.impl.helper.ReadOnlyDictionary]"
09:39:58.004,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery(587)] : invoked activate: activate"
09:39:58.005,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.AmazonEchoDiscovery(587)] : Changed state from satisfied to active"
09:39:58.007,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery(588)] : ServiceFactory.getService()"
09:39:58.007,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery(588)] : This thread collected dependencies"
09:39:58.007,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery(588)] : getService (ServiceFactory) dependencies collected."
09:39:58.007,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery(588)] : Querying state satisfied"
09:39:58.007,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery(588)] : For dependency osgi.ds.satisfying.condition, optional: false
09:39:58.008,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery(588)] : invoking activate: activate: parameters [org.apache.felix.scr.impl.helper.ReadOnlyDictionary]"
09:39:58.008,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery(588)] : invoked activate: activate"
09:39:58.008,"DEBUG","org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery","bundle org.openhab.binding.amazonechocontrol:5.0.2 (282)[org.openhab.binding.amazonechocontrol.internal.discovery.SmartHomeDevicesDiscovery(588)] : Changed state from satisfied to active"
09:39:58.010,"INFO","openhab.event.ThingStatusInfoChangedEvent","Thing 'amazonechocontrol:account:e2b7351909' changed from UNINITIALIZED (DISABLED) to INITIALIZING"
09:39:58.015,"INFO","openhab.event.ThingStatusInfoChangedEvent","Thing 'amazonechocontrol:account:e2b7351909' changed from INITIALIZING to OFFLINE (CONFIGURATION_PENDING): Wait for login"
09:39:58.016,"DEBUG","org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler","check login amazonechocontrol:account:e2b7351909"
09:39:58.017,"DEBUG","org.openhab.binding.amazonechocontrol.internal.util.HttpRequestBuilder","> POST: https://api.amazon.com/auth/token (available: 2)"
09:39:58.019,"INFO","openhab.event.ThingStatusInfoChangedEvent","Thing 'amazonechocontrol:echo:e2b7351909:954bd10e22' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING"
09:39:58.024,"INFO","openhab.event.ThingStatusInfoChangedEvent","Thing 'amazonechocontrol:echo:e2b7351909:954bd10e22' changed from INITIALIZING to UNKNOWN"
09:39:58.564,"DEBUG","org.openhab.binding.amazonechocontrol.internal.util.HttpRequestBuilder$HttpResponseListener","< POST to https://api.amazon.com/auth/token: 200"
09:39:58.565,"DEBUG","org.openhab.binding.amazonechocontrol.internal.util.HttpRequestBuilder","> POST: https://www.amazon.de/ap/exchangetoken (available: 2)"
09:39:58.901,"DEBUG","org.openhab.binding.amazonechocontrol.internal.util.HttpRequestBuilder$HttpResponseListener","< POST to https://www.amazon.de/ap/exchangetoken: 200"
09:39:58.902,"DEBUG","org.openhab.binding.amazonechocontrol.internal.util.HttpRequestBuilder","> GET: https://eu-api-alexa.amazon.com/api/bootstrap (available: 2)"
09:39:58.952,"DEBUG","org.openhab.binding.amazonechocontrol.internal.util.HttpRequestBuilder$HttpResponseListener","< GET to https://eu-api-alexa.amazon.com/api/bootstrap: 404"
09:39:58.956,"DEBUG","org.openhab.binding.amazonechocontrol.internal.connection.Connection","Bootstrapping failed"
09:39:58.957,"INFO","openhab.event.ThingStatusInfoChangedEvent","Thing 'amazonechocontrol:account:e2b7351909' changed from OFFLINE (CONFIGURATION_PENDING): Wait for login to OFFLINE (CONFIGURATION_PENDING): Please login in through servlet: http(s)://<YOUROPENHAB>:<YOURPORT>/amazonechocontrol/e2b7351909"
09:39:58.957,"INFO","openhab.event.ThingStatusInfoChangedEvent","Thing 'amazonechocontrol:echo:e2b7351909:954bd10e22' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)"
Other smart home systems have the same issue. They are fixing it or about to fix it based on the commit from here:
Great. Means the issue is identified. When is it getting fixed for our systems?
Just in case it helps:
There’s a PR running for home-assistant too. It claims that it solves the issue.
The PR is this
https://github.com/home-assistant/core/pull/155989
Nobody knows. No pressure to our beloved all volunteer devs please 
Oh ya. No pressure for sure. I am only requesting 
Hi all,
I have since two days a simiar issue. All my things went offline, and I cannot login anymore. The status of the bridge is config pending. When I open the config page amazonechocontrol/home, I put it username, password on the next page, and end up with a 404, as the following page is not found: https://www.amazon.de/ap/cvf/request
Setup is running in Germany. Could that be the same issue? Best, Lui
Yes.
From github about the problem with the binding:
Amazon is switching its servers to the new Alexa Skill Kit v3, which removes the possibility to access the echoes via api/bootstrap.
This leaves (currently) only the local option using an emulation of the Alexa web app, as used by Node-RED and, as far as I know, also by the media player in Home Assistant. However, this would be a major change compared to the current binding, since access to the properties works differently.
I hope I’ve summarized this correctly — please correct me if not.
I think I’ll give the node-red-way a try. It seems not so complicated. I wonder if there will be a solution to receive the lastCommand like we had in the binding.
I still use the rest-api in openhab2 on my raspberry pi to let my echoes speak. Today I noticed its not working anymore. For the amazonechocontrol page I get :
Problem accessing /amazonechocontrol/xxxxxxxx. Reason:
Server Error
org.openhab.binding.amazonechocontrol.internal.HttpException: GET url 'https://alexa.amazon.de/api/bootstrap' failed: Not Found
Followed by a lot of java messages.
Is this caused by same problem?
Keep us posted, please.