Amazon Echo Dot Thing not configuring

Add-ons Bindings
1

OpenHAB 5.1.3 release build

I’ve acquired an Amazon Echo Dot and am trying to incorporate it into OpenHAB for rules-based control. There are a few other threads describing issues with the bridge, but I seem to be having a different issue.
If I open http://xxx.xxx.xxx.xxx:8080/amazonechocontrol/account1 it shoes along the top header, Account “Amazon Account” that this is “ONLINE”, followed by a table of my account information.

Below this my devices are listed, and under the column Name, the Echo Dot shows as ONLINE. However in the next column Thing, it indicates NONE highlighted in grey. So it would seem the bridge is functioning (also my bridge thing within OpenHAB Things is green) but the Echo dot is not.

Under my bridge definition the Dot thing is defined as

Thing echo echo1 "Alexa" @ "Shed" [serialNumber="123456789"]

I used the serial number from the Alexa app, and not that which appears in the amazonechocontrol link, but neither SN works.

My logs from an initial configuration load:

2026-03-29 09:18:45.545 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading DSL model 'bridges.things'
2026-03-29 09:18:45.576 [DEBUG] [trol.internal.handler.AccountHandler] - cleanup amazonechocontrol:account:account1
2026-03-29 09:18:45.579 [INFO ] [openhab.event.ThingStatusInfoEvent ] - Thing 'amazonechocontrol:account:account1' updated: OFFLINE (CONFIGURATION_PENDING): Wait for login
2026-03-29 09:18:45.579 [DEBUG] [trol.internal.handler.AccountHandler] - check login amazonechocontrol:account:account1
2026-03-29 09:18:45.581 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:account:account1' changed from ONLINE to OFFLINE (CONFIGURATION_PENDING): Wait for login
2026-03-29 09:18:45.581 [INFO ] [openhab.event.ThingStatusInfoEvent ] - Thing 'amazonechocontrol:echo:account1:echo1' updated: OFFLINE (BRIDGE_OFFLINE)
2026-03-29 09:18:45.581 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:account1:echo1' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
2026-03-29 09:18:45.581 [INFO ] [openhab.event.ThingUpdatedEvent ] - Thing 'amazonechocontrol:account:account1' has been updated.
2026-03-29 09:18:45.584 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > POST: https://api.amazon.com/auth/token (available: 2)
2026-03-29 09:18:45.636 [DEBUG] [rol.internal.push.PushSessionHandler] - Session 610133341 closed, reason 0
2026-03-29 09:18:45.637 [DEBUG] [control.internal.push.PushConnection] - Received a session closed for session 610133341, but the current session is <not set>
2026-03-29 09:18:45.951 [DEBUG] [pRequestBuilder$HttpResponseListener] - < POST to https://api.amazon.com/auth/token: 200
2026-03-29 09:18:45.952 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > POST: https://www.amazon.com/ap/exchangetoken (available: 2)
2026-03-29 09:18:45.997 [DEBUG] [pRequestBuilder$HttpResponseListener] - < POST to https://www.amazon.com/ap/exchangetoken: 0
2026-03-29 09:18:45.997 [DEBUG] [pRequestBuilder$HttpResponseListener] - Retrying call to https://www.amazon.com/ap/exchangetoken
2026-03-29 09:18:48.397 [DEBUG] [pRequestBuilder$HttpResponseListener] - < POST to https://www.amazon.com/ap/exchangetoken: 200
2026-03-29 09:18:48.398 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/customer-status (available: 2)
2026-03-29 09:18:48.794 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/customer-status: 200
2026-03-29 09:18:48.795 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/users/me?platform=ios&version=2.2.556530.0 (available: 2)
2026-03-29 09:18:48.958 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/users/me?platform=ios&version=2.2.556530.0: 200
2026-03-29 09:18:48.960 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/customer-status (available: 2)
2026-03-29 09:18:49.202 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/customer-status: 200
2026-03-29 09:18:49.202 [DEBUG] [ntrol.internal.connection.Connection] - Customer profile exists My Name Account ID
2026-03-29 09:18:49.204 [INFO ] [openhab.event.ThingStatusInfoEvent ] - Thing 'amazonechocontrol:account:account1' updated: ONLINE
2026-03-29 09:18:49.204 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:account:account1' changed from OFFLINE (CONFIGURATION_PENDING): Wait for login to ONLINE
2026-03-29 09:18:49.204 [INFO ] [openhab.event.ThingStatusInfoEvent ] - Thing 'amazonechocontrol:echo:account1:echo1' updated: ONLINE
2026-03-29 09:18:49.204 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'amazonechocontrol:echo:account1:echo1' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2026-03-29 09:18:49.271 [DEBUG] [trol.internal.handler.AccountHandler] - refreshing data amazonechocontrol:account:account1
2026-03-29 09:18:49.271 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/devices-v2/device?cached=false (available: 2)
2026-03-29 09:18:49.452 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/devices-v2/device?cached=false: 200
2026-03-29 09:18:49.452 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/wake-word?cached=true (available: 2)
2026-03-29 09:18:49.603 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/wake-word?cached=true: 200
2026-03-29 09:18:49.605 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/content-skills/enabled-feeds (available: 2)
2026-03-29 09:18:49.614 [DEBUG] [control.internal.push.PushConnection] - Successfully initiated stream for session 1705684187.
2026-03-29 09:18:49.779 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/content-skills/enabled-feeds: 200
2026-03-29 09:18:49.779 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/device-notification-state (available: 2)
2026-03-29 09:18:49.892 [DEBUG] [trol.internal.push.PushStreamAdapter] - Sending ping
2026-03-29 09:18:49.979 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/device-notification-state: 200
2026-03-29 09:18:49.980 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/ascending-alarm (available: 2)
2026-03-29 09:18:50.159 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/ascending-alarm: 200
2026-03-29 09:18:50.161 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/dnd/device-status-list (available: 2)
2026-03-29 09:18:50.332 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/dnd/device-status-list: 200
2026-03-29 09:18:50.332 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/bluetooth?cached=true (available: 2)
2026-03-29 09:18:50.490 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/bluetooth?cached=true: 200
2026-03-29 09:18:50.491 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/behaviors/entities?skillId=amzn1.ask.1p.music (available: 2)
2026-03-29 09:18:50.789 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/behaviors/entities?skillId=amzn1.ask.1p.music: 200
2026-03-29 09:18:50.790 [DEBUG] [trol.internal.handler.AccountHandler] - refresh notifications amazonechocontrol:account:account1
2026-03-29 09:18:50.790 [DEBUG] [rol.internal.util.HttpRequestBuilder] - > GET: https://na-api-alexa.amazon.com/api/notifications (available: 2)
2026-03-29 09:18:50.897 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/notifications: 400
2026-03-29 09:18:50.897 [DEBUG] [pRequestBuilder$HttpResponseListener] - Retrying call to https://na-api-alexa.amazon.com/api/notifications
2026-03-29 09:18:52.992 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/notifications: 400
2026-03-29 09:18:52.993 [DEBUG] [pRequestBuilder$HttpResponseListener] - Retrying call to https://na-api-alexa.amazon.com/api/notifications
2026-03-29 09:18:55.084 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/notifications: 400
2026-03-29 09:18:55.085 [DEBUG] [pRequestBuilder$HttpResponseListener] - Retrying call to https://na-api-alexa.amazon.com/api/notifications
2026-03-29 09:18:55.732 [INFO ] [openhab.event.ItemStateEvent ] - Item 'Dryer_State' shall update to POWEROFF

2026-03-29 09:18:57.180 [DEBUG] [pRequestBuilder$HttpResponseListener] - < GET to https://na-api-alexa.amazon.com/api/notifications: 400
2026-03-29 09:18:57.181 [WARN ] [ntrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2026-03-29 09:18:57.181 [DEBUG] [trol.internal.handler.AccountHandler] - refresh data amazonechocontrol:account:account1 finished
2

Hey Dave,

I would move away from .thing based setup on Amazon Account/Echo devices. I did when I went to OH 5.x and it went a lot smoother via the GUI discovery process.

http://openhabianpi5:8080/amazonechocontrol/

Best, Jay

3

Thanks @jwiseman, that worked brilliantly. It all shows as connected. Now however, it doesn’t seem to happy about communicating with OpenHAB:

2026-03-29 13:51:18.580 [DEBUG] [pRequestBuilder$HttpResponseListener] - < POST to https://na-api-alexa.amazon.com/api/behaviors/preview: 401
2026-03-29 13:51:18.580 [WARN ] [ntrol.internal.connection.Connection] - execute sequence node fails with unexpected error
org.openhab.binding.amazonechocontrol.internal.ConnectionException: https://na-api-alexa.amazon.com/api/behaviors/preview failed with code 401: Unauthorized
	at org.openhab.binding.amazonechocontrol.internal.util.HttpRequestBuilder$HttpResponseListener.onComplete(HttpRequestBuilder.java:386) ~[?:?]
	at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:218) ~[?:?]
	at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:210) ~[?:?]
	at org.eclipse.jetty.client.AuthenticationProtocolHandler$AuthenticationListener.forwardFailureComplete(AuthenticationProtocolHandler.java:297) ~[?:?]
	at org.eclipse.jetty.client.AuthenticationProtocolHandler$AuthenticationListener.onComplete(AuthenticationProtocolHandler.java:164) ~[?:?]
	at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:218) ~[?:?]
	at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:210) ~[?:?]
	at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:481) ~[?:?]
	at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:461) ~[?:?]
	at org.eclipse.jetty.client.HttpReceiver.responseSuccess(HttpReceiver.java:424) ~[?:?]
	at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.messageComplete(HttpReceiverOverHTTP.java:374) ~[?:?]
	at org.eclipse.jetty.http.HttpParser.handleContentMessage(HttpParser.java:596) ~[?:?]
	at org.eclipse.jetty.http.HttpParser.parseContent(HttpParser.java:1669) ~[?:?]
	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1552) ~[?:?]
	at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.parse(HttpReceiverOverHTTP.java:208) ~[?:?]
	at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:148) ~[?:?]
	at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:80) ~[?:?]
	at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:131) ~[?:?]
	at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:172) ~[?:?]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) ~[?:?]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) ~[?:?]
	at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:555) ~[?:?]
	at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:410) ~[?:?]
	at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:164) ~[?:?]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) ~[?:?]
	at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104) ~[?:?]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338) ~[?:?]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315) ~[?:?]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) ~[?:?]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131) ~[?:?]
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409) ~[?:?]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) ~[?:?]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) ~[?:?]
	at java.lang.Thread.run(Thread.java:1583) [?:?]
2026-03-29 13:51:18.586 [DEBUG] [ntrol.internal.connection.Connection] - Removed 1634115252 device(s) [GRA22H01608205R4] from queue

There are a string of similar debug entries above the WARN

4

This is a known issue, its communicating either too fast OR to and end point that is EOL. I’ve opened tickets about this back in Oct/Nov 2025, still open.

Here’s my log right now.

2026-03-29 08:54:09.840 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2026-03-29 09:00:46.770 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2026-03-29 09:01:04.235 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2026-03-29 09:02:39.883 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2026-03-29 10:02:41.312 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2026-03-29 11:02:41.326 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2026-03-29 12:02:41.976 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2026-03-29 13:02:42.458 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2026-03-29 14:02:43.020 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request

There’s more issues than this that are still pending.

Best, Jay