Web Socket Error on AmazonEchoControl binding every 65 seconds

Good to know it’s not just me!

It’s something that happens on my system sporadically and fairly frequently, although rarely for long stretches like this. It’s become a prevailing reliability issue in my setup, which relies on the echocontrol binding’s lastCommand item to trigger a lot of my home automation. In the last 3-4 days it hasn’t worked at all! No commands or actions are appearing in the openHAB console, just this error report:

22:10:10.290 [INFO ] [ocontrol.internal.WebSocketConnection] - Web Socket error
java.nio.channels.AsynchronousCloseException: null
        at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.close(HttpConnectionOverHTTP.java:181) ~[?:?]
        at java.util.ArrayList.forEach(ArrayList.java:1257) [?:1.8.0_221]
        at org.eclipse.jetty.client.AbstractConnectionPool.close(AbstractConnectionPool.java:208) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.client.DuplexConnectionPool.close(DuplexConnectionPool.java:237) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.client.HttpDestination.close(HttpDestination.java:385) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.client.HttpClient.doStop(HttpClient.java:260) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:93) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:180) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:201) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.client.WebSocketClient.doStop(WebSocketClient.java:371) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:93) [bundleFile:9.4.20.v20190813]
        at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection.close(WebSocketConnection.java:159) [bundleFile:?]
        at org.openhab.binding.amazonechocontrol.internal.WebSocketConnection$2.run(WebSocketConnection.java:184) [bundleFile:?]
        at java.util.TimerThread.mainLoop(Timer.java:555) [?:1.8.0_221]
        at java.util.TimerThread.run(Timer.java:505) [?:1.8.0_221]

This appears randomly about every minute or so. It also appears a few seconds after a voice command is given to alexa.

As mentioned above, the ‘solution’ given on the aforementioned thread is to wait for it to be resolved server-side. I accept that, but in the meantime I wonder whether anyone has any further insight as to why it happens, and whether anything could be done to make the binding immune to this (likely) server-side problem?

2 Likes