Error: Web Socket close 1005. Reason: null

[sl4m (Simon)]

I did the process. Login did not work. Will try to send you the logfile as DM.

[dika67 (Dieter Kaiser)]

Exactly the same for me. On OH v3.2.0 Stable and performed step 1 and 2. And the issue is solved.

Kudos to @J-N-K and thanks a lot!

[ariela (Andrea Riela)]

Hi folks,

I’ve the same log every 1m20s

2022-01-15 18:20:01.993 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2022-01-15 18:21:14.078 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2022-01-15 18:22:51.349 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2022-01-15 18:24:19.551 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2022-01-15 18:25:31.747 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2022-01-15 18:26:57.522 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2022-01-15 18:28:27.439 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2022-01-15 18:29:47.271 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null

How to understand if it’s an amazonechocontrol issue? and how to fix it? I’m on 3.3.0 #2690, so I was expecting the issue was already fixed. Am I wrong?

thanks for your support, much appreciated
Andrea

[ariela (Andrea Riela)]

@J-N-K sorry to bother you again on this thread, but after some search I see that my issue is like:

Web Socket Error on AmazonEchoControl binding every 65 seconds

Thanks for the quick fix! Maybe a side question: how will this fix be officially available? Is it automatically provided after merge when I do an update on openhabian? Or are there also maintenance releases for the addons once in a while? If I manually copy the addon now to my installation, will there be a conflict or so when later doing the OH updates?

I’m on 3.3.0 #2690, and if I well understood from 3.2 it should be already fixed in the add-on. Or am I wrong? do I need to put there a customised jar?

thanks again for your support here

Andrea

[Tallman]

Exactly the same for me, I’m on 3.3.0 #2694 .
The version for the binding is displayed in the console as 3.3.0.202201150331

[Wolfgang_S]

@Tallman

3.3.0 #2694

that sounds like you installed amazonechocontrol from the OH repository …
Reading about first 15 posts in this thread as far as I understand the content that is provided via third party download smarthomej content is the one that contains the fixes.

[ariela (Andrea Riela)]

not sure I understand why we need to download the add-on via third party smarthomej, and not the add-on in the OH repository. But I’m not an expert, so just to understand, not to blame someone (your support guys is always excellent :))

thanks for any clarification. I need to understand if I can wait for a fix in the OH repository, or better to move as situi suggested

thanks again
Andrea

[J-N-K (Jan N. Klug)]

To my knowledge a fix for the openHAB Version is not available in the near future.

[Wolfgang_S]

@ariela

not sure I understand why we need to download the add-on via third party smarthomej, and not the add-on in the OH repository.

same question was raised in this post Amazon Echo Control Error "Web socket close 1005" - Still happening on 3.2.0 - #18 by JimT
“answer” to it is in the post next to it.

[sihui]

@Wolfgang_S

“answer”

Good catch.

I think we shouldn’t question this in detail, their may be something going on behind the scenes we don’t know and don’t have to know.
I am happy that we have the great working smarthome/j version(s), thx Jan.