The old thread for this error ends with everybody seeming to say that the error has gone away, and the thread is locked. From what I can tell, the updated binding included with OH 3.1 and up is supposed to have fixed the problem. Unfortunately, that hasn’t worked for me.
I’m on 3.2.0, and I’ve removed the binding, cleared the cache, re-installed the binding… I’ve tried snapshot JARs that were posted in the old thread… no matter what I do, I still get the Web socket 1005 error every minute.
Am I missing a step? Do I need to remove my amazon “account” thing and re-add it? Is there some other log-out-and-back-in step that I’ve somehow missed?
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.
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?
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.