Amazon Echo Control Error "Web socket close 1005" - Still happening on 3.2.0

Add-ons Bindings
2

also on latest ci build:

310 │ Active │  80 │ 3.3.0.202112200814    │ openHAB Add-ons :: Bundles :: Amazon Echo Control Binding

log says:

11:14:34.604 [INFO ] [ocontrol.internal.WebSocketConnection] - Web Socket close 1005. Reason: null

opened bug: [amazonechocontrol] openhab 3.2.0 Web Socket close 1005. Reason: null · Issue #11822 · openhab/openhab-addons (github.com)

3

Same problem here, with 3.2 stable

2021-12-22 09:07:11.489 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null

4

I’m on openHABian main branch, and received an update today. After the update, I am no longer getting the web socket error! Interestingly, the splash screen when I log into SSH still says “openHAB 3.2.0 - Release Build”.

EDIT: Never mind. It’s back. Not sure what happened, there, but it was gone for a little while. Then, I had to temporarily disable my “amazon account” thing, and when I re-enabled it, the web socket error returned.

5

Hi all,

Struggeling with the same error logs - openhabian OH3.2.0.
Are there any updates?

Regards

6

look here: [amazonechocontrol] Error: Web Socket close 1005. Reason: null · Issue #11810 · openhab/openhab-addons · GitHub

7

Here’s a version of the binding that works.

You have to uninstall the old one you have and drop these 2 items into your AddOn’s. A recycle of OH most likely will be needed also.

This version also works with the new Alexa air sensors just released.

Please don’t forget to remove the .txt from each of the files before doing this.

org.smarthomej.binding.amazonechocontrol-3.2.9-SNAPSHOT.jar.txt (475.7 KB)

org.smarthomej.commons-3.2.9-SNAPSHOT.jar.txt (66.4 KB)

Best, Jay

1 Like
8

with this version I get following error:

[ocontrol.internal.handler.EchoHandler] - Failed to get player queue

EDIT: seems to be resolved.

9

no … I get this Error again and again

10

At the karaf console, what is shown with this command?

list -s | grep amazon

Best, Jay

11 
322 │ Active │  80 │ 3.2.9                 │ org.smarthomej.binding.amazonechocontrol
12

My recommendation would be to clear the cache and tmp directories as the next steps.

I’m assuming you put the other commons jar in the addons also?

Best, Jay

13

Thank you! Solved the issue for me.

14

More discussion here

15

I rebuild the container and now it seems to work. fingers crossed

btw: great work and thanks

16

Thanks for posting the updated binding, Jay! And thanks, Mark, for the link to the other thread. I ended up installing the new binding by adding the json third-party addon file in the settings, and using the UI to install it like any other binding (after first removing the one that ships with 3.2, of course.)

Everything is working smoothly now. No more websocket errors.

Are the updates in this binding set to be added to the next official release?

17

Looks like this might solve two problems in one go (web socket 1005 and delayed response to commands). However, I can’t log in. I get: Login to 'amazon.com' failed: Request failed.

My account is registered with amazon.co.uk but I’m not convinced that is the problem because it recognises me enough to ask for my OTP, it just fails after that. If I disable 2FA, it fails right after the password screen.

18

Why is the smarthome/j version not merged into the main openhab? Why keeping a separate repo/version?

19

There are different views on technical and administrative/organizational aspects.

1 Like
20

Same thing here, however, I’m registered with amazon.ca

21

I’ve got mine working. Reinstall the version that can log in, get logged in and then install the latest - it remembers that you are logged on.