ducker2
(Ducker2)
December 25, 2025, 8:22am
1
Hi there, it’s already a long time ago that smartHomeDevices stopped working. All of these Things (Air Quality Monitor, smartHomeDevice channels on Echo devices, etc.) are still discoverred, including the relevant channels, but they remain in UNKNOWN state and the channel values are NULL. Removing and adding the thing again does not do the trick.
All non-smartHomeDevice things, like TTS, playback, speak, textCommand, etc. Echo devices, are working fine again after the last binding updates. Just non of smartHomeDevice functions works.
As mentioned, this is not a recent error, I face this issue already since a year or so. Since the non-smartHomeDevice parts are now working again, maybe it’s possible to get the full device support back. Any idea how to fix the smartHomeDevice support? Thanks!
sihui
(SiHui)
December 25, 2025, 8:26am
2
Update to a recent openHAB version. Since 5.0.3 most, it not all of the issues got fixed.
openHAB 5.1.0 Release version:
ducker2
(Ducker2)
December 25, 2025, 8:34am
3
Wow, what fast response!
Actually, the new updates have triggered me to start a new approach trying to get smartHomeDevice support back. I’m already on 5.1.0 but the issue remained with all recent updates and upgrades (since some 4.x version).
sihui
(SiHui)
December 25, 2025, 8:42am
4
ducker2:
since some 4.x version
Did you try to reset your Amazon account through Karaf ?
Please try amazonechocontrol listAccounts and then amazonechocontrol resetAccount <id> on the console. It seems that something is wrong with the account configuration.
yab
(Marino Schwedhelm)
December 25, 2025, 8:50am
5
If you are talking about things like “Alexa Guard on …”: Amazon does not provide the functions any more (did they ever work in DE?). They are said to be back some time, but you will have to pay for.
ducker2
(Ducker2)
December 25, 2025, 9:16am
6
Yes, they did work even in DE for some time, I used it for a couple of years. Too bad, but that confirms my worries, that more and more functionality is moved behind the pay wall. Therefore I did not invest in any further Amazon smare home sensors. When presence detection on Alexa Guard stopped working, e.g. the Air Quality Monitor device was still usable before all smartHomeDevice functions stopped.
ducker2
(Ducker2)
December 25, 2025, 9:35am
7
Yes, Amazon account has been reset multiple times. First time when the binding failed due to Amazon’s changes to the API. When the new binding versions became available, I issued another reset. Just to be sure, I now did did a reset and re-authentication one more time. In fact the smartHomeDevices thing states changed to ONLINE, but all channels (channel detection itself still works) values remain NULL.
sihui
(SiHui)
December 25, 2025, 9:39am
8
Then I am out of ideas. As you can see from my above screenshots, it is working for me …
lsiepel
(Leo)
December 25, 2025, 1:06pm
9
Anything in the logs? I would expect Atleast one issue to be logged.
ducker2
(Ducker2)
December 25, 2025, 7:14pm
10
Just one suspect entry this morning:
Request to URL ‘https://eu-api-alexa.amazon.com/api/phoenix/state’ failed: https://eu-api-alexa.amazon.com/api/phoenix/state failed with code 429: Too Many Requests
jwiseman
(Mr. Wiseman (OH 5.1.1 Stable on Pi5))
December 27, 2025, 4:02pm
11
These issues are still pending with the Amazon Control Binding.
opened 05:17PM - 11 Dec 25 UTC
bug
@digitaldan
@lsiepel
Version 5.1.0.m3 has a rouge path issue in it now after th… e change of the authentication method ( #19690 )
https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
Try again
```
2025-11-24 07:24:00.252 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 07:34:59.373 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 07:35:20.014 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 07:49:11.693 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 07:49:29.429 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 07:54:05.812 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 07:54:22.749 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 08:01:36.174 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 08:01:53.369 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 08:46:04.687 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 09:14:07.109 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 10:14:08.541 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-11-24 11:14:09.378 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
```
opened 05:16PM - 11 Dec 25 UTC
bug
@digitaldan
@lsiepel
Version 5.1.0.m3 has a rouge path issue in it now after th… e change of the authentication method ( #19690 )
I believe this rouge path needs to be sub/replaced with the correct one.
na-api-alexa.amazon.com/api/np/command?
```
2025-11-27 18:31:35.287 [WARN ] [ing.amazonechocontrol.internal.handler.EchoHandler] - Failed to handle command 'PAUSE' to 'amazonechocontrol:echo:account1:echobathroom:player': https://na-api-alexa.amazon.com/api/np/command?deviceSerialNumber=G090XG0692830EM1&deviceType=A1RABVCI4QCIKC failed with code 404: Not Found
org.openhab.binding.amazonechocontrol.internal.ConnectionException: https://na-api-alexa.amazon.com/api/np/command?deviceSerialNumber=G090XG069283xxx&deviceType=A1RABVCI4QCIKC 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) ~[?:?]
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:1723) ~[?:?]
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:840) [?:?]
```
I’m now running the 5.1.0 Stable version now, same results as 5.1.0.m3 version.
Best, Jay
pleky
(PleKy)
December 31, 2025, 3:43pm
12
Hello,
Got a similar issue, I’ve tried to logout & reconnect, and now I have an alexa login prompt loopîng:
We’re unable to verify your mobile number. Try signing in again.
Any idea to at least reconnect ?
Thanks
pleky
(PleKy)
February 7, 2026, 7:45am
14
From my side, one month later I was able to reconnect and resync.
So now it looks to be ok.
The unique thing I lost (but it is not really new) is the hue v1 detection. Echo are no longer able to add devices, and one support guy asked me to remove all the devices and try to redetect: KO