[amazonechocontrol] - Bugs in 4.3.9 version

jwiseman · November 29, 2025, 4:56pm

Here are all the bugs in the amazonechocontrol 4.3.9 version so far after a week of its release.

[amazonechocontrol] Amazon Air Quality Monitors (amazonechocontrol:humidity) #19708

github.com/openhab/openhab-addons

[amazonechocontrol] Amazon Air Quality Monitors (amazonechocontrol:humidity)

opened 01:56PM - 24 Nov 25 UTC

jaywiseman1971

bug

There is specific code around these Amazon devices in the binding below. https:…//www.amazon.com/dp/B08W8KS8D3 This may/may not reference the original fix that was working on the 4.3.8 version prior to the authentication changes on 4.3.9 --> https://github.com/openhab/openhab-addons/pull/19212 The 4.3.9 version of the binding re-introduced, I believe, this bug --> https://github.com/openhab/openhab-addons/issues/19624 In my opinion, **I think this could be a pathing issue** based on the path of the channel below for these specific Amazon Air Quality devices since other humidity items seem to work that are not these specific devices. 2025-11-23 12:49:22.084 [ERROR] [.amazonechocontrol.internal.handler.AccountHandler] - refresh data fails with unexpected error java.lang.IllegalArgumentException: **Channel type 'amazonechocontrol:humidity' is not known** at org.openhab.core.thing.internal.ThingHandlerCallbackImpl.createChannelBuilder(ThingHandlerCallbackImpl.java:222) ~[?:?] at org.openhab.binding.amazonechocontrol.internal.handler.SmartHomeDeviceHandler.addChannelToDevice(SmartHomeDeviceHandler.java:203) ~[?:?] at org.openhab.binding.amazonechocontrol.internal.handler.SmartHomeDeviceHandler.setDeviceAndUpdateThingState(SmartHomeDeviceHandler.java:136) ~[?:?] at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.lambda$26(AccountHandler.java:739) ~[?:?] at java.util.concurrent.CopyOnWriteArrayList.forEach(CopyOnWriteArrayList.java:807) ~[?:?] at java.util.concurrent.CopyOnWriteArraySet.forEach(CopyOnWriteArraySet.java:425) ~[?:?] at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.updateSmartHomeDeviceList(AccountHandler.java:739) ~[?:?] at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.refreshData(AccountHandler.java:445) ~[?:?] at org.openhab.binding.amazonechocontrol.internal.handler.AccountHandler.checkLoginAndData(AccountHandler.java:403) ~[?:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] at java.lang.Thread.run(Thread.java:840) [?:?]

[amazonechocontrol] /PROXY/api/notifications (failed with code 400) #19714

github.com/openhab/openhab-addons

[amazonechocontrol] /PROXY/api/notifications (failed with code 400)

opened 01:09PM - 25 Nov 25 UTC

jaywiseman1971

bug

Version 4.3.9 has a rouge path issue in it now after the change of the authentic…ation method ( https://github.com/openhab/openhab-addons/pull/19690 ) Version 4.3.8 references this path --> **/amazonechocontrol/account1/PROXY/api/notifications** In a browser this URL now returns this with 4.3.9 https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request [Try again](http://192.168.0.32:8080/amazonechocontrol/account1/) The 4.3.9 binding is logging this error consistently now. 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 2025-11-24 12:14:09.230 [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 13:14:10.045 [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 14:14:10.614 [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 15:14:07.455 [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 16:13:38.638 [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 17:13:38.725 [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 18:13:40.362 [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 18:14:07.459 [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 19:14:10.516 [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 20:14:09.245 [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 21:13:38.550 [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 22:02:20.803 [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 22:20:21.490 [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 23:01:28.038 [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 23:01:44.727 [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 23:02:31.549 [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-25 00:02:31.620 [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-25 01:02:31.989 [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-25 01:10:28.869 [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-25 01:10:45.828 [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-25 02:10:46.787 [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-25 03:10:48.616 [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-25 04:10:47.578 [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-25 05:10:47.855 [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-25 06:10:49.043 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request

[amazonechocontrol] /api/np/command? (failed with code 404) #19724

github.com/openhab/openhab-addons

[amazonechocontrol] na-api-alexa.amazon.com/api/np/command? (failed with code 404)

opened 12:35PM - 28 Nov 25 UTC

jaywiseman1971

bug

Version 4.3.9 has a rouge path issue in it now after the change of the authentic…ation method ( https://github.com/openhab/openhab-addons/pull/19690 ) I believe this rouge path needs to be sub/replaced with the correct one. **na-api-alexa.amazon.com/api/np/command?** This ticket is similar to this ticket except for parts of the path ( https://github.com/openhab/openhab-addons/issues/19714 ) 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) [?:?]

lastVoiceCommand channel doesn’t work at all on all versions of Echos v2 - 5.

Anything to do with reminder and alarm channels aren’t working, separate ticket opened on this by someone else.

I can confirm that TTS and volume setting is working very well.

Best, Jay

tommycw10 · November 29, 2025, 9:18pm

Don’t forget this one. While it was filed against the beta jar, it wasn’t fixed for 4.3.9:

github.com/openhab/openhab-addons

[amazonechocontrol] Binding does not control volume of devices

opened 10:12PM - 23 Nov 25 UTC

tommycw1

bug

After uninstalling the amazonechocontrol binding provided in OH 4.3.8, I downloa…ded the .zip file provided [here](https://onedrive.live.com/?id=70EA7AC46BC61C73%21s8a76a2ab18554feda6247fa2854e7440&cid=70EA7AC46BC61C73&redeem=aHR0cHM6Ly8xZHJ2Lm1zL3UvYy83MGVhN2FjNDZiYzYxYzczL0lRQ3JvbmFLVlJqdFQ2WWtmNktGVG5SQUFib2FJTmt6TjF5a0JnN2Y0T2Job1lBP2U9YWZ6RTZS&parId=70EA7AC46BC61C73%21119773&o=OneUp) for testing the fix to the binding issue discussed [here](https://github.com/openhab/openhab-addons/issues/19624#issuecomment-3568331910):, extracted the three .jar files into /usr/share/openhab/addons. The new binding started fine and I was able to re-login without issues. If I change the volume on my device it reflects the change in OH, however if I change the volume in OH, it does not change on the device and gets set back to the original volume. ``` 2025-11-23 16:10:04.694 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'Echo_CR_Volume' received command 100 2025-11-23 16:10:04.703 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Echo_CR_Volume' predicted to become 100 2025-11-23 16:10:04.706 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Echo_CR_Volume' changed from 30 to 100 2025-11-23 16:10:16.944 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Echo_CR_Volume' changed from 100 to 30 ``` All other functions that I tried seemed to function correctly I've tried this on all of my various devices including Echo, Echo Dot, Echo Show, Echo Pop. I'm running openhab 4.3.8 on Openhabian Raspbian GNU/Linux 11 (bullseye) on an RPI4. Please let me know if there is anything I can do to try to help debug.